From: Jack Mitchell <ml@communistcode.co.uk>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: ld problems with relocated toolchain
Date: Fri, 21 Sep 2012 16:17:23 +0100 [thread overview]
Message-ID: <505C8503.2040907@communistcode.co.uk> (raw)
In-Reply-To: <505C7F3A.7020400@intel.com>
On 21/09/12 15:52, Laurentiu Palcu wrote:
>
> On 09/21/2012 05:04 PM, Jack Mitchell wrote:
>> I am currently having issues building my application with the latest
>> toolchain.
>>
>> I have used the new capabilities of it being relocatable to place it
>> somewhere sensible and I think this may be what is breaking it. My old
>> toolchain in /opt still works perfectly.
>>
>> The error I receive is:
>>
>> /home/jack/Projects/R0005-SDK-210912/sysroots/x86_64-pokysdk-linux/usr/bin/armv7a-vfp-neon-poky-linux-gnueabi/../../libexec/armv7a-vfp-neon-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/4.7.2/ld:
>> cannot find crtbegin.o: No such file or directory
>> collect2: error: ld returned 1 exit status
>> make: *** [R0005] Error 1
> Did this error appear after the latest SDK fixes that were merged today?
> Can you activate compiler verbose mode so we can see the arguments
> passed to the linker? Does it work if you install in the default
> location? Or better, can you tell the exact steps you followed to get
> this issue?
Exact steps:
bitbake meta-toolchain
run toolchain setup script
tell application to use new toolchain and sysroot
compile
This was appearing before the patches that were merged today.
Works fine when installed in default location.
Some more verbose output:
/home/jack/Projects/R0005-SDK-210912/sysroots/x86_64-pokysdk-linux/usr/bin/armv7a-vfp-neon-poky-linux-gnueabi/../../libexec/armv7a-vfp-neon-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/4.7.2/as
-v -I
/home/jack/Projects/R0005-SDK-210912/sysroots/armv7a-vfp-neon-poky-linux-gnueabi/usr/include
-mcpu=cortex-a8 -mfloat-abi=softfp -mfpu=neon -meabi=5 -o
src/systemConfig.o /tmp/ccr24jiu.s
GNU assembler version 2.22 (arm-poky-linux-gnueabi) using BFD version
(GNU Binutils) 2.22
COMPILER_PATH=/home/jack/Projects/R0005-SDK-210912/sysroots/x86_64-pokysdk-linux/usr/bin/armv7a-vfp-neon-poky-linux-gnueabi/../../libexec/armv7a-vfp-neon-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/4.7.2/:/home/jack/Projects/R0005-SDK-210912/sysroots/x86_64-pokysdk-linux/usr/bin/armv7a-vfp-neon-poky-linux-gnueabi/../../libexec/armv7a-vfp-neon-poky-linux-gnueabi/gcc/
LIBRARY_PATH=/home/jack/Projects/R0005-SDK-210912/sysroots/x86_64-pokysdk-linux/usr/bin/armv7a-vfp-neon-poky-linux-gnueabi/../../lib/armv7a-vfp-neon-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/4.7.2/:/home/jack/Projects/R0005-SDK-210912/sysroots/x86_64-pokysdk-linux/usr/bin/armv7a-vfp-neon-poky-linux-gnueabi/../../lib/armv7a-vfp-neon-poky-linux-gnueabi/gcc/
COLLECT_GCC_OPTIONS='-I'
'/home/jack/Projects/R0005-SDK-210912/sysroots/armv7a-vfp-neon-poky-linux-gnueabi/usr/include'
'-O0' '-mfpu=neon' '-mfloat-abi=softfp' '-mcpu=cortex-a8' '-g3' '-Wall'
'-Wextra' '-c' '-fmessage-length=0' '-v' '-MMD' '-MP' '-MF'
'src/systemConfig.d' '-MT' 'src/systemConfig.d' '-o'
'src/systemConfig.o' '-mtls-dialect=gnu'
/home/jack/Projects/R0005-SDK-210912/sysroots/x86_64-pokysdk-linux/usr/bin/armv7a-vfp-neon-poky-linux-gnueabi/../../libexec/armv7a-vfp-neon-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/4.7.2/ld:
cannot find crt1.o: No such file or directory
/home/jack/Projects/R0005-SDK-210912/sysroots/x86_64-pokysdk-linux/usr/bin/armv7a-vfp-neon-poky-linux-gnueabi/../../libexec/armv7a-vfp-neon-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/4.7.2/ld:
cannot find crti.o: No such file or directory
/home/jack/Projects/R0005-SDK-210912/sysroots/x86_64-pokysdk-linux/usr/bin/armv7a-vfp-neon-poky-linux-gnueabi/../../libexec/armv7a-vfp-neon-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/4.7.2/ld:
cannot find crtbegin.o: No such file or directory
/lib/libpthread.so.0: file not recognized: File format not recognized
collect2: error: ld returned 1 exit status
make: *** [R0005] Error 1
>
> Thanks,
> Laurentiu
>> However, crtbeign.o is at the path:
>>
>> [jack@archHP armv7a-vfp-neon-poky-linux-gnueabi]$ pwd
>> /home/jack/Projects/R0005-SDK-210912/sysroots/armv7a-vfp-neon-poky-linux-gnueabi
>> [jack@archHP armv7a-vfp-neon-poky-linux-gnueabi]$ find . -name
>> crtbegin.o
>> ./usr/lib/arm-poky-linux-gnueabi/4.7.2/crtbegin.o
>> [jack@archHP armv7a-vfp-neon-poky-linux-gnueabi]$ ls usr/lib
>> lib/ libexec/
>> [jack@archHP armv7a-vfp-neon-poky-linux-gnueabi]$ ls usr/libexec/
>> pt_chown
>> [jack@archHP armv7a-vfp-neon-poky-linux-gnueabi]$
>>
>>
>> Does anyone have an idea what is the issue here? Why can't it find the
>> object file?
>>
--
Jack Mitchell (jack@embed.me.uk)
Embedded Systems Engineer
http://www.embed.me.uk
--
next prev parent reply other threads:[~2012-09-21 15:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-21 14:04 ld problems with relocated toolchain Jack Mitchell
2012-09-21 14:08 ` Richard Purdie
2012-09-21 14:23 ` Jack Mitchell
2012-09-21 14:27 ` Zhang, Jessica
2012-09-21 14:35 ` Jack Mitchell
2012-09-21 14:52 ` Laurentiu Palcu
2012-09-21 15:17 ` Jack Mitchell [this message]
2012-09-24 2:17 ` Khem Raj
2012-09-24 8:37 ` Jack Mitchell
2012-09-24 8:44 ` Laurentiu Palcu
2012-09-24 8:54 ` Jack Mitchell
2012-09-24 15:28 ` Khem Raj
2012-09-25 8:29 ` Jack Mitchell
2012-09-25 13:41 ` Khem Raj
2012-09-25 13:58 ` 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=505C8503.2040907@communistcode.co.uk \
--to=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