From: Steve Rodgers <hwstar@rodgers.sdcoxmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot: Problem locating crt1.o on target system [more info]
Date: Thu, 8 Feb 2007 15:59:40 -0800 [thread overview]
Message-ID: <200702081559.40799.hwstar@rodgers.sdcoxmail.com> (raw)
In-Reply-To: <200702081138.38218.hwstar@rodgers.sdcoxmail.com>
I discovered that if I move crt1.o, crti.o and crtn.o to my build directory on
the target system where the C source lives, the test.c file compiles
correctly.
Looking at the gcc-v output, gcc is expecting these files to be in the build
directory, not in /usr/lib!
What changes would be required to gcc- gcc-uclibc-3.x.mk to resolve this so
that /usr/lib/crtX.0 files can be brought in from /usr/lib?
Here's the output of gcc -v test.c:
GNU assembler version 2.16.1 (i586-linux-uclibc) using BFD version 2.16.1
/usr/libexec/gcc/i586-linux-uclibc/3.4.2/collect2 --eh-frame-hdr -m elf_i386
-dynamic-linker /lib/ld-uClibc.so.0 crt1.o
crti.o /usr/lib/gcc/i586-linux-uclibc/3.4.2/crtbegin.o
-L/usr/lib/gcc/i586-linux-uclibc/3.4.2
-L/usr/lib/gcc/i586-linux-uclibc/3.4.2 /tmp/ccAcPbA4.o -lgcc --as-needed
-lgcc_s --no-as-needed -lc -lgcc --as-needed -lgcc_s
--no-as-needed /usr/lib/gcc/i586-linux-uclibc/3.4.2/crtend.o crtn.o
/usr/bin/ld: crt1.o: No such file: No such file or directory
collect2: ld returned 1 exit status
Steve.
On Thursday 08 February 2007 11:38, Steve Rodgers wrote:
> I've been using buildroot for quite some time and recently decided to
> upgrade it as some of the packages in the older version I'm using are no
> longer available for download.
>
> I've run into a problem using the C compiler and linker on the target
> system. I can't compile a simple "hello world" program written in C on the
> target system.
>
> The compiler/linker complains it can't find crt1.o, even though it is
> located in /user/lib. The exact error message is:
>
> ?/usr/bin/ld: crt1.o: No such file: No such file or directory
>
> I configured buildroot for gcc 3.4.2 and binutils 2.16. I selected the the
> 2.4.31 kernel headers.
>
> The system in question ?was built using the 2/6/07 snapshot tarball of
> buildroot.
>
> The config file for buildroot is attached.
>
> Is there some configuration option I missed?
>
> TIA Steve.
next prev parent reply other threads:[~2007-02-08 23:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-08 19:38 [Buildroot] Buildroot: Problem locating crt1.o on target system Steve Rodgers
2007-02-08 23:59 ` Steve Rodgers [this message]
2007-02-09 6:32 ` Alexander Rigbo
2007-02-09 16:51 ` Steve Rodgers
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=200702081559.40799.hwstar@rodgers.sdcoxmail.com \
--to=hwstar@rodgers.sdcoxmail.com \
--cc=buildroot@busybox.net \
/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