Openembedded Core Discussions
 help / color / mirror / Atom feed
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 10:19:39 +0100	[thread overview]
Message-ID: <1312967980.6733.35.camel@phil-desktop> (raw)
In-Reply-To: <24988974-E702-4404-BEB2-EB8B946BFC5E@kernel.crashing.org>

On Tue, 2011-08-09 at 23:20 -0500, Kumar Gala wrote:
> Trying to build something like u-boot w/the toolchain produced by meta-toolchain-sdk and get the following:
> 
> $ powerpc-poky-linux-gnuspe-ld -g -Ttext 0x40000 -o hello_world -e hello_world hello_world.o libstubs.o -L. -lgcc
> powerpc-poky-linux-gnuspe-ld: cannot find -lgcc
> 
>[...]
>
> What do we need to tweak so we can find libgcc.a?

The best/easiest fix is to link with gcc rather than calling ld
directly.  You can use -nostartfiles to suppress crt1.o and the like.
If you must invoke ld manually for whatever reason then you will have to
use something like `$(CC) --print-libgcc-file-name` to obtain the path
to libgcc.

p.





  parent reply	other threads:[~2011-08-10  9:24 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 [this message]
2011-08-10 12:43   ` Kumar Gala
2011-08-10 12:50     ` Phil Blundell
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=1312967980.6733.35.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