Re: build system: gcc_cv_libc_provides_ssp and NATIVE_SYSTEM_HEADER_DIR

2008-10-12 Thread Kai Henningsen
On Fri, 10 Oct 2008 11:24:22 + (UTC) "Joseph S. Myers" <[EMAIL PROTECTED]> wrote: > On Fri, 10 Oct 2008, Thorsten Glaser wrote: > > > Thomas Schwinge dixit: > > > > >Ideally, IMO, this test (for stack-smashing-protection support in > > >glibc) should not be done by grepping through SYSROOT's

Re: build system: gcc_cv_libc_provides_ssp and NATIVE_SYSTEM_HEADER_DIR

2008-10-10 Thread Thomas Schwinge
Hello! On Fri, Oct 10, 2008 at 01:25:52PM +0200, Samuel Thibault wrote: > Thomas Schwinge, le Fri 10 Oct 2008 10:37:50 +0200, a écrit : > > Ideally, IMO, this test (for stack-smashing-protection support in glibc) > > should not be done by grepping through SYSROOT's features.h, but instead > > by u

Re: build system: gcc_cv_libc_provides_ssp and NATIVE_SYSTEM_HEADER_DIR

2008-10-10 Thread Thorsten Glaser
Joseph S. Myers dixit: >It's desirable to be able to configure GCC correctly in the presence of >installed headers and only a dummy libc.so, so as to get a GCC that can be >used to build the full glibc. Ah, right, the GNU case. Sorry, I totally did not have that one in mind, even though I know

Re: build system: gcc_cv_libc_provides_ssp and NATIVE_SYSTEM_HEADER_DIR

2008-10-10 Thread Samuel Thibault
Thomas Schwinge, le Fri 10 Oct 2008 10:37:50 +0200, a écrit : > Ideally, IMO, this test (for stack-smashing-protection support in glibc) > should not be done by grepping through SYSROOT's features.h, but instead > by using the CPP for doing that. The problem is that CPP has not yet > been bulit at

Re: build system: gcc_cv_libc_provides_ssp and NATIVE_SYSTEM_HEADER_DIR

2008-10-10 Thread Joseph S. Myers
On Fri, 10 Oct 2008, Thorsten Glaser wrote: > Thomas Schwinge dixit: > > >Ideally, IMO, this test (for stack-smashing-protection support in glibc) > >should not be done by grepping through SYSROOT's features.h, but instead > >by using the CPP for doing that. > > Why not just autoconf? > > Check

Re: build system: gcc_cv_libc_provides_ssp and NATIVE_SYSTEM_HEADER_DIR

2008-10-10 Thread Thomas Schwinge
Hello! On Fri, Oct 10, 2008 at 09:48:02AM +, Thorsten Glaser wrote: > Thomas Schwinge dixit: > >Ideally, IMO, this test (for stack-smashing-protection support in glibc) > >should not be done by grepping through SYSROOT's features.h, but instead > >by using the CPP for doing that. > > Why not

Re: build system: gcc_cv_libc_provides_ssp and NATIVE_SYSTEM_HEADER_DIR

2008-10-10 Thread Thorsten Glaser
Thomas Schwinge dixit: >Ideally, IMO, this test (for stack-smashing-protection support in glibc) >should not be done by grepping through SYSROOT's features.h, but instead >by using the CPP for doing that. Why not just autoconf? Check for the presence of __stack_smash_handler() in libc… or am I m

Re: build system: gcc_cv_libc_provides_ssp and NATIVE_SYSTEM_HEADER_DIR

2008-10-10 Thread Thomas Schwinge
Hello! On Thu, Oct 09, 2008 at 11:49:06AM +0200, Paolo Bonzini wrote: > > Unfortunately, NATIVE_SYSTEM_HEADER_DIR is a Makefile variable (see > > gcc/config/t-gnu). It is being used only in three places: > > gcc/config/t-gnu, gcc/config/t-gnu and gcc/config/i386/t-mingw32. What That list was bo

Re: build system: gcc_cv_libc_provides_ssp and NATIVE_SYSTEM_HEADER_DIR

2008-10-08 Thread Thorsten Glaser
Thomas Schwinge dixit: >First, the check for gcc_cv_libc_provides_ssp is not complete, as has >already pointed out (with patches!) before, but is still not fixed on >trunk. Let me revisit that: in configure.ac it is being checked for >``case "$target" in *-*-linux*)'' which should rather match ``

build system: gcc_cv_libc_provides_ssp and NATIVE_SYSTEM_HEADER_DIR

2008-10-08 Thread Thomas Schwinge
Hello! First, the check for gcc_cv_libc_provides_ssp is not complete, as has already pointed out (with patches!) before, but is still not fixed on trunk. Let me revisit that: in configure.ac it is being checked for ``case "$target" in *-*-linux*)'' which should rather match ``*-*-linux* | *-*-*-g