From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: ml@communistcode.co.uk
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: Toolchain Issues
Date: Tue, 16 Jul 2013 11:25:09 +0100 [thread overview]
Message-ID: <1373970309.29233.72.camel@ted> (raw)
In-Reply-To: <51E5027D.6050003@communistcode.co.uk>
On Tue, 2013-07-16 at 09:21 +0100, Jack Mitchell wrote:
> Morning everyone,
>
> I'm trying to create a custom toolchain and sdk for a development board
> and I'm having some issues.
>
> I create my toolchain with the following method:
>
> bitbake image -c populate_sdk
>
> When I try to compile u-boot with the sdk, I recieve the following error:
>
> Configuring for socfpga_cyclone5 board...
> make[1]: *** [/mnt/SSD/socfpga/u-boot-socfpga.git/spl/u-boot-spl]
> Error 1
> make: *** [spl/u-boot-spl.bin] Error 2
> make: *** [u-boot] Error 1
> arm-oecore-linux-gnueabi-size: './u-boot': No such file
> arm-oecore-linux-gnueabi-ld.bfd: cannot find -lgcc
> make[1]: *** [/mnt/SSD/socfpga/u-boot-socfpga.git/spl/u-boot-spl]
> Error 1
> make: *** [spl/u-boot-spl.bin] Error 2
> make: *** Waiting for unfinished jobs....
> arm-oecore-linux-gnueabi-ld.bfd: cannot find -lgcc
> make: *** [u-boot] Error 1
The toolchain environment script requires some --sysroot options to be
passed to the compiler/linker. I'm guessing uboot isn't getting these.
See the uboot recipes for how to pass in those options.
Cheers,
Richard
next prev parent reply other threads:[~2013-07-16 10:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-16 8:21 Toolchain Issues Jack Mitchell
2013-07-16 10:25 ` Richard Purdie [this message]
2013-07-16 13:30 ` Mark Hatle
2013-07-16 13:51 ` Jack Mitchell
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=1373970309.29233.72.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=ml@communistcode.co.uk \
--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