- To: gcc-help@xxxxxxxxxxx
- Subject: Re: Toolchain compilation problems
- From: David Summers <gmane@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 30 May 2012 10:18:02 +0100
- Comment: DKIM? See http://www.dkim.org
- Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys
- In-reply-to: <jq0qvh$mub$1@dough.gmane.org>
- User-agent: Mozilla/5.0 (X11; Linux i686; rv:12.0) Gecko/20120430 Thunderbird/12.0.1
OK - solved the problem.
gcc (collect2 I think) doesn't look in /home/arm/usr/lib - despite that
it is listed in the ld search directories.
So what needs to be done is to copy (or set up a link) from the various
crt*.o files to the directory:
..../armv7-hardfloat-linux-gnueabi/lib
Or whatever the triplet name of your gcc is, in your top direcory (for
me /home/arm).
I'm not sure, but may also need these files in:
.../lib/gcc/armv7-hardfloat-linux-gnueabi/4.7.0
That seemed to help some times - but not when compiling gcc itself (e.g.
the various libs gcc compiles for itself, e.g. under threading and sharing).
So is this gcc doing something wrong, or is it uClibc installing crt*.o
in the wrong place?
David.
On 28/05/12 22:33, David Summers wrote:
I'm trying to compile a tool chain to run on an x86-64 machine, but ...
# ls /home/arm/usr/lib/crt*.o
/home/arm/usr/lib/crt1.o /home/arm/usr/lib/crti.o /home/arm/usr/lib/crtn.o
[Linux C Programming]
[Linux Kernel]
[eCos]
[Fedora Development]
[Fedora Announce]
[Autoconf]
[The DWARVES Debugging Tools]
[Yosemite Campsites]
[Yosemite News]
[Linux GCC]