From: Phil Blundell <philb@gnu.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: finding libgcc.a with meta-toolchain-sdk toolchain
Date: Wed, 10 Aug 2011 13:50:33 +0100 [thread overview]
Message-ID: <1312980634.6733.62.camel@phil-desktop> (raw)
In-Reply-To: <1A4B195B-C80C-4E0B-9FC2-DBB3E1FC3E2E@kernel.crashing.org>
On Wed, 2011-08-10 at 07:43 -0500, Kumar Gala wrote:
> While these are good suggestions, I still think the toolchain is broken as u-boot has been this way for sometime and numerous other cross toolchains work perfectly fine.
I just tried "ld -lgcc" on my Ubuntu desktop and it didn't work there
either. Indeed, there's no way in general for ld to know which libgcc
to use since you might have multiple versions of gcc installed on the
system.
So, while u-boot might have worked for you before, if it is linking with
the command you mentioned (and no extra -L options) then I think it was
only working by chance.
p.
next prev parent reply other threads:[~2011-08-10 12:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-10 4:20 finding libgcc.a with meta-toolchain-sdk toolchain Kumar Gala
2011-08-10 6:54 ` Khem Raj
2011-08-10 9:19 ` Phil Blundell
2011-08-10 12:43 ` Kumar Gala
2011-08-10 12:50 ` Phil Blundell [this message]
2011-10-27 3:07 ` [RFC] Fix libgcc nativesdk to install libgcc.a in good location for tools Matthew McClintock
2011-10-27 3:40 ` James Limbouris
2011-10-27 4:20 ` McClintock Matthew-B29882
2011-10-28 9:03 ` Richard Purdie
2011-10-28 19:35 ` McClintock Matthew-B29882
2011-10-28 19:36 ` McClintock Matthew-B29882
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=1312980634.6733.62.camel@phil-desktop \
--to=philb@gnu.org \
--cc=openembedded-core@lists.openembedded.org \
/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