From: Eial Czerwacki <eial@scalemp.com>
To: buildroot@busybox.net
Subject: [Buildroot] enabling libc.a generation
Date: Tue, 01 May 2012 11:45:19 +0300 [thread overview]
Message-ID: <4F9FA29F.90309@scalemp.com> (raw)
In-Reply-To: <4F9F9EBE.2070303@mind.be>
On 05/01/2012 11:28 AM, Arnout Vandecappelle wrote:
> On 05/01/12 08:24, Eial Czerwacki wrote:
>> I have a little issue, while trying to compile a small file within a
>> buildroot generated env, I get this:
>> /usr/lib/gcc/i686-unknown-linux-uclibc/4.2.4/../../../../i686-unknown-linux-uclibc/bin/ld:
>>
>> cannot find -lc
>> collect2: ld returned 1 exit status
>
> It would help if you at least specified the command you used to start
> the link. You can also add the -v option to gcc to see the exact
> parameters of the call to ld, including the search path.
>
> libc.a and libc.so should be present in output/staging/usr/lib. But I
> see you're calling a gcc in /usr... Is this a compiler running on the
> target? In that case, you should have libc.so and libc.a in /usr/lib.
>
> Regards,
> Arnout
Hello Arnout,
I have chroot which was created using buildroot, I'm chrooting into it
an run a simple compilation, e.g sh-4.1# gcc test.c -o test
here is the output gcc -v:
Using built-in specs.
Target: i686-unknown-linux-uclibc
Configured with:
/home/envdev/buildroot/output/toolchain/gcc-4.2.4/configure
--prefix=/usr --build=i686-pc-linux-gnu --host=i686-unknown-linux-uclibc
--target=i686-unknown-linux-uclibc --enable-languages=c
--with-gxx-include-dir=/usr/include/c++ --disable-__cxa_atexit
--enable-target-optspace --disable-libgomp --with-gnu-ld
--disable-libssp --disable-multilib --enable-tls --enable-shared
--disable-nls --enable-threads --with-arch=i686 --with-tune=i686
--disable-largefile
Thread model: posix
gcc version 4.2.4
as for libc.so, here is the relevant output:
sh-4.1# find . -name "libc*"
./lib/libcrypt.so.0
./lib/libc.so.0
./lib/libcrypt-0.9.32.so
./usr/include/bits/libc-lock.h
./usr/lib/libcurses.a
sh-4.1# ls -l ./lib/libc.so.0
lrwxrwxrwx 1 root root 19 Apr 30 23:57 ./lib/libc.so.0
-> libuClibc-0.9.32.so
Eial.
next prev parent reply other threads:[~2012-05-01 8:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-01 6:24 [Buildroot] enabling libc.a generation Eial Czerwacki
2012-05-01 8:28 ` Arnout Vandecappelle
2012-05-01 8:45 ` Eial Czerwacki [this message]
2012-05-04 19:55 ` Arnout Vandecappelle
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=4F9FA29F.90309@scalemp.com \
--to=eial@scalemp.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