Re: Configuring GCC 10.3 on PPC Mac OS X 10.4.11/Tiger for build reveals flaws in configure scripts

[Jonathan Wakely <jwakely.gcc@gmail.com>]

On Fri, 25 Nov 2022 at 11:29, Jonathan Wakely wrote:
>
> On Fri, 25 Nov 2022 at 11:22, Jonathan Wakely wrote:
> >
> > On Fri, 25 Nov 2022 at 10:20, Peter Dyballa via Gcc-help
> > <gcc-help@gcc.gnu.org> wrote:
> > > Configuring stage 2 in ./gcc
> > >
> > > checking linker --sysroot support... no
> > > checking __stack_chk_fail in target C library... checking for __stack_chk_fail... no
> > > no __stack_chk_fail on this target
> > > no
> > > checking sys/sdt.h in the target C library... no
> >
> >
> > I'll see if I can find this one too. Also harmless though.
>
> gcc/configure.ac has:
>
> # Test for stack protector support in target C library.
> AC_CACHE_CHECK(__stack_chk_fail in target C library,
> ...
>        *-*-darwin* | *-*-freebsd* | *-*-netbsd*)
>      AC_CHECK_FUNC(__stack_chk_fail,[gcc_cv_libc_provides_ssp=yes],
>            [echo "no __stack_chk_fail on this target"])
>         ;;
>
> That AC_CHECK_FUNC comes after the earlier message which hasn't
> printed its result yet, so the output of the two gets muddled. Then
> the echo makes it even worse, by adding a third message inside the
> other two.


I've opened https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107869 for this.