Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: Toolchain Issues
Date: Tue, 16 Jul 2013 08:30:54 -0500	[thread overview]
Message-ID: <51E54B0E.2070701@windriver.com> (raw)
In-Reply-To: <51E5027D.6050003@communistcode.co.uk>

On 7/16/13 3:21 AM, 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:
>

How are you compiling/linking uboot, what options are you using?

When you load the SDK, you need to source the environment file, and then you 
should be using $CC/$LD from the environment as the compiler.  Calling the 
arm-... directly may lead to failures as the --sysroot parameter is not passed 
to the compiler.

--Mark

>       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
>
> So I took a look at the gcc -v and it gives me:
>
> [09:14:40 jack u-boot-socfpga.git]$ arm-oecore-linux-gnueabi-gcc -v |
> grep custom
> Using built-in specs.
> COLLECT_GCC=arm-oecore-linux-gnueabi-gcc
> COLLECT_LTO_WRAPPER=/mnt/SSD/socfpga/custom-sdk/1.0-20130715/sysroots/x86_64-oecore-linux/usr/bin/cortexa9hf-vfp-neon-oecore-linux-gnueabi/../../libexec/cortexa9hf-vfp-neon-oecore-linux-gnueabi/gcc/arm-oecore-linux-gnueabi/4.8.1/lto-wrapper
> Target: arm-oecore-linux-gnueabi
> Configured with:
> /mnt/SSD/oe-r0005/altera-r0005/tmp/work-shared/gcc-4.8.1-r0/gcc-4.8.1/configure
> --build=x86_64-linux --host=x86_64-oecore-linux
> --target=arm-oecore-linux-gnueabi
> --prefix=/mnt/SSD/r0005sdk/1.0-20130715/sysroots/x86_64-oecore-linux/usr
> --exec_prefix=/mnt/SSD/r0005sdk/1.0-20130715/sysroots/x86_64-oecore-linux/usr
> --bindir=/mnt/SSD/r0005sdk/1.0-20130715/sysroots/x86_64-oecore-linux/usr/bin/cortexa9hf-vfp-neon-oecore-linux-gnueabi
> --sbindir=/mnt/SSD/r0005sdk/1.0-20130715/sysroots/x86_64-oecore-linux/usr/bin/cortexa9hf-vfp-neon-oecore-linux-gnueabi
> --libexecdir=/mnt/SSD/r0005sdk/1.0-20130715/sysroots/x86_64-oecore-linux/usr/libexec/cortexa9hf-vfp-neon-oecore-linux-gnueabi
> --datadir=/mnt/SSD/r0005sdk/1.0-20130715/sysroots/x86_64-oecore-linux/usr/share
> --sysconfdir=/mnt/SSD/r0005sdk/1.0-20130715/sysroots/x86_64-oecore-linux/etc
> --sharedstatedir=/mnt/SSD/r0005sdk/1.0-20130715/sysroots/x86_64-oecore-linux/com
> --localstatedir=/mnt/SSD/r0005sdk/1.0-20130715/sysroots/x86_64-oecore-linux/var
> --libdir=/mnt/SSD/r0005sdk/1.0-20130715/sysroots/x86_64-oecore-linux/usr/lib/cortexa9hf-vfp-neon-oecore-linux-gnueabi
> --includedir=/mnt/SSD/r0005sdk/1.0-20130715/sysroots/x86_64-oecore-linux/usr/include
> --oldincludedir=/mnt/SSD/r0005sdk/1.0-20130715/sysroots/x86_64-oecore-linux/usr/include
> --infodir=/mnt/SSD/r0005sdk/1.0-20130715/sysroots/x86_64-oecore-linux/usr/share/info
> --mandir=/mnt/SSD/r0005sdk/1.0-20130715/sysroots/x86_64-oecore-linux/usr/share/man
> --disable-silent-rules --disable-dependency-tracking
> --with-libtool-sysroot=/mnt/SSD/oe-r0005/altera-r0005/tmp/sysroots/x86_64-nativesdk-oecore-linux
> --with-gnu-ld --enable-shared --enable-languages=c,c++
> --enable-threads=posix --enable-multilib --enable-c99 --enable-long-long
> --enable-symvers=gnu --enable-libstdcxx-pch
> --program-prefix=arm-oecore-linux-gnueabi- --without-local-prefix
> --enable-target-optspace --enable-lto --enable-libssp
> --disable-bootstrap --disable-libmudflap --with-system-zlib
> --with-linker-hash-style=gnu --enable-linker-build-id --with-ppl=no
> --with-cloog=no --enable-checking=release --enable-cheaders=c_global
> --with-float=hard
> --with-gxx-include-dir=/mnt/SSD/r0005sdk/1.0-20130715/sysroots/cortexa9hf-vfp-neon-oecore-linux-gnueabi/usr/include/c++
> --with-build-time-tools=/mnt/SSD/oe-r0005/altera-r0005/tmp/sysroots/x86_64-linux/usr/arm-oecore-linux-gnueabi/bin
> --with-sysroot=/mnt/SSD/r0005sdk/1.0-20130715/sysroots/cortexa9hf-vfp-neon-oecore-linux-gnueabi
> --with-build-sysroot=/mnt/SSD/oe-r0005/altera-r0005/tmp/sysroots/socfpga_cyclone5
> --disable-libunwind-exceptions --disable-libssp --disable-libgomp
> --disable-libmudflap
> --with-mpfr=/mnt/SSD/oe-r0005/altera-r0005/tmp/sysroots/x86_64-nativesdk-oecore-linux
> --with-mpc=/mnt/SSD/oe-r0005/altera-r0005/tmp/sysroots/x86_64-nativesdk-oecore-linux
> --enable-nls
> Thread model: posix
> gcc version 4.8.1 (GCC)
>
> Now, my toolchain is located in the directory:
>
> /mnt/SSD/socfpga/custom-sdk/1.0-20130715
>
> So, why does most of the GCC version info mention the default directory of:
>
> /mnt/SSD/r0005sdk/1.0-20130715
>
> Is this a bug, or just a quirk? If it's a quirk then why can't u-boot
> find -lgcc on compile?
>
> Cheers,
>



  parent reply	other threads:[~2013-07-16 13:30 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
2013-07-16 13:30 ` Mark Hatle [this message]
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=51E54B0E.2070701@windriver.com \
    --to=mark.hatle@windriver.com \
    --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