Ken Moffat wrote:
> I just started another attempt to build for ppc64, using the
> 20071030 book. And didn't get very far at all - binutils tried to
> use x86_64-pc-linux-gnu-ar and tried to find it (yeah, I'm building
> from x86_64 multilib).
>
> This is the first part of the cross-compile, so far all I've built
> are the headers and 'file'). At this stage, the only variant of
> 'ar' is just plain 'ar'. The really strange thing is that
> 'configure' tested for x86_64-pc-linux-gnu-ar and didn't find it,
> then later decided it was indeed there. Looking at the _main_
> config.log, I can see
>
> configure:6295: checking for x86_64-pc-linux-gnu-ar
> configure:6324: result: no
>
> but then at the end
> AR='x86_64-pc-linux-gnu-ar'
> AR_FOR_TARGET='powerpc64-unknown-linux-gnu-ar'
>
> which means that when configure runs in a subdirectory it finds
> x86_64-pc-linux-gnu-ar.
>
> I don't understand how this can work, unless for some strange
> reason only x86_64 hosts are affected. Maybe I'm missing something
> obvious.
>
When binutils was updated to 2.18 the configure command changed too,
AR=ar AS=as was put in the env to fix that annoying change.
_______________________________________________
Clfs-support mailing list
[email protected]
http://lists.cross-lfs.org/cgi-bin/mailman/listinfo/clfs-support
