Jim Gifford wrote:
> Here's what it should be saying instead of
>
> checking whether make sets $(MAKE)... yes
> checking whether to enable maintainer-specific portions of
> Makefiles... no
> checking for gcc... cc
>
> This is from a powerpc build I just completed
>
> checking for gawk... gawk
> checking whether make sets $(MAKE)... yes
> checking whether to enable maintainer-specific portions of
> Makefiles... no
>
> --This Line
> checking for powerpc-unknown-linux-gnu-gcc...
> powerpc-unknown-linux-gnu-gcc --You notice mine picked up the value of
> ${CC} - yours only shows cc
>
> checking for C compiler default output file name... a.out
> checking whether the C compiler works... yes
> checking whether we are cross compiling... yes
>
>
>
>
>
> _______________________________________________
> Clfs-support mailing list
> [email protected]
> http://lists.cross-lfs.org/cgi-bin/mailman/listinfo/clfs-support
>
Yes, I noticed this thing...
Right now I tried another build, now when configuring for native tools,
it looks for i686-{target}-gcc and indeed it finds i686-{target}-gcc but
then again at the
'checking for C compiler default output file name...' it prints out
'configure: error: C compiler cannot create executables'._______________________________________________ Clfs-support mailing list [email protected] http://lists.cross-lfs.org/cgi-bin/mailman/listinfo/clfs-support
