From: Steve Rae <srae@broadcom.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] buildman: using wrong libgcc.a (magic -3)
Date: Wed, 5 Nov 2014 11:36:52 -0800 [thread overview]
Message-ID: <545A7C54.30204@broadcom.com> (raw)
In-Reply-To: <20141105190902.847643833C7@gemini.denx.de>
On 14-11-05 11:09 AM, Wolfgang Denk wrote:
> Dear Steve,
>
> In message <545A74E6.5010208@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:
>>
>> CROSS_COMPILE=/opt/eldk-5.4/armv7a/sysroots/i686-eldk-linux/usr/bin/armv7a-vfp-neon-linux-gnueabi/arm-linux-gnueabi-
>
> Actually we should have only
>
> CROSS_COMPILE=arm-linux-gnueabi-
>
> and make the PATH take care of where to pick the tools from.
>
> Best regards,
>
> Wolfgang Denk
>
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)
installed on my machine....
If $PATH" was to "take care of it", then somehow $PATH would need to be
constantly "rearranged" so that the desired compiler is selected correctly.
IMO it would be best to specify the "absolute path to the prefix"
completely, and not rely on PATH at all!
Thanks, Steve
next prev parent reply other threads:[~2014-11-05 19:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-30 16:57 [U-Boot] buildman: using wrong libgcc.a Steve Rae
2014-10-30 20:42 ` Steve Rae
2014-10-30 20:57 ` Jeroen Hofstee
2014-11-03 21:14 ` Simon Glass
2014-11-05 17:22 ` Steve Rae
2014-11-05 18:46 ` Jeroen Hofstee
2014-11-05 19:05 ` [U-Boot] buildman: using wrong libgcc.a (magic -3) Steve Rae
2014-11-05 19:09 ` Wolfgang Denk
2014-11-05 19:36 ` Steve Rae [this message]
2014-11-05 22:59 ` Wolfgang Denk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=545A7C54.30204@broadcom.com \
--to=srae@broadcom.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox