Re: [U-Boot] buildman: using wrong libgcc.a

2014-11-05 Thread Steve Rae
On 14-11-03 01:14 PM, Simon Glass wrote: Hi, On 30 October 2014 14:57, Jeroen Hofstee jer...@myspectrum.nl wrote: Hello Steve, On 30-10-14 21:42, Steve Rae wrote: H -- maybe it would be better to specify the entire path for the CROSS_COMPILE, and not rely on the PATH to find the cross

Re: [U-Boot] buildman: using wrong libgcc.a

2014-11-05 Thread Jeroen Hofstee
Hello Simon, On 03-11-14 22:14, Simon Glass wrote: Hi, On 30 October 2014 14:57, Jeroen Hofstee jer...@myspectrum.nl wrote: Hello Steve, On 30-10-14 21:42, Steve Rae wrote: H -- maybe it would be better to specify the entire path for the CROSS_COMPILE, and not rely on the PATH to find

Re: [U-Boot] buildman: using wrong libgcc.a (magic -3)

2014-11-05 Thread Steve Rae
On 14-11-05 10:46 AM, Jeroen Hofstee wrote: Hello Simon, On 03-11-14 22:14, Simon Glass wrote: Hi, On 30 October 2014 14:57, Jeroen Hofstee jer...@myspectrum.nl wrote: Hello Steve, On 30-10-14 21:42, Steve Rae wrote: H -- maybe it would be better to specify the entire path for the

Re: [U-Boot] buildman: using wrong libgcc.a (magic -3)

2014-11-05 Thread Wolfgang Denk
Dear Steve, In message 545a74e6.5010...@broadcom.com you wrote: In my experience, we would normally set the CROSS_COMPILE variable to the prefix of the cross compiler toolchain, for example:

Re: [U-Boot] buildman: using wrong libgcc.a (magic -3)

2014-11-05 Thread Steve Rae
On 14-11-05 11:09 AM, Wolfgang Denk wrote: Dear Steve, In message 545a74e6.5010...@broadcom.com you wrote: In my experience, we would normally set the CROSS_COMPILE variable to the prefix of the cross compiler toolchain, for example:

Re: [U-Boot] buildman: using wrong libgcc.a (magic -3)

2014-11-05 Thread Wolfgang Denk
Dear Steve, In message 545a7c54.30...@broadcom.com you wrote: Actually, that would be unfortunate, because I currently have: - /usr/bin/arm-linux-gnueabi-gcc - /opt/eldk-5.4/armv7a/sysroots/i686-eldk-linux/usr/bin/armv7a-vfp-neon-linux-gnueabi/arm-linux-gnueabi-gcc - (and others)

Re: [U-Boot] buildman: using wrong libgcc.a

2014-11-03 Thread Simon Glass
Hi, On 30 October 2014 14:57, Jeroen Hofstee jer...@myspectrum.nl wrote: Hello Steve, On 30-10-14 21:42, Steve Rae wrote: H -- maybe it would be better to specify the entire path for the CROSS_COMPILE, and not rely on the PATH to find the cross compile tools: diff --git

[U-Boot] buildman: using wrong libgcc.a

2014-10-30 Thread Steve Rae
Hi Simon, In my environment, buildman and MAKEALL are not producing the same results. It seems that buildman is accidentally picking up the wrong libgcc.a ... *** buildman *** $ cat ~/.buildman [toolchain] eldk:

Re: [U-Boot] buildman: using wrong libgcc.a

2014-10-30 Thread Steve Rae
H -- maybe it would be better to specify the entire path for the CROSS_COMPILE, and not rely on the PATH to find the cross compile tools: diff --git a/tools/buildman/toolchain.py b/tools/buildman/toolchain.py index 27dc318..58c7b1f 100644 --- a/tools/buildman/toolchain.py +++

Re: [U-Boot] buildman: using wrong libgcc.a

2014-10-30 Thread Jeroen Hofstee
Hello Steve, On 30-10-14 21:42, Steve Rae wrote: H -- maybe it would be better to specify the entire path for the CROSS_COMPILE, and not rely on the PATH to find the cross compile tools: diff --git a/tools/buildman/toolchain.py b/tools/buildman/toolchain.py index 27dc318..58c7b1f 100644