From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Fedora 16: Cannot find -lc
Date: Tue, 01 May 2012 10:21:21 +0200 [thread overview]
Message-ID: <4F9F9D01.2090407@mind.be> (raw)
In-Reply-To: <CA+T-u8d3owC=YNJ5O9V6MUaahdSOPo21H+5aLxxnf8xan5GyHQ@mail.gmail.com>
On 05/01/12 08:35, Alexander Broekhuis wrote:
> Hi all,
>
> I am trying to use buildroot on a Fedora 16 installation and run into
> the following error:
>
> /usr/bin/ld: cannot find -lc
> collect2: ld returned 1 exit status
>
> The last make command before the error:
> make[2]: Entering directory
> `/home/alexander/Development/buildroot/output/build/host-module-init-tools-3.15/build'
> /usr/lib/ccache/gcc -O2
> -I/home/alexander/Development/buildroot/output/host/include
> -I/home/alexander/Development/buildroot/output/host/usr/include -Wunused
> -Wall -static -L/home/alexander/Development/buildroot/output/host/lib
> -L/home/alexander/Development/buildroot/output/host/usr/lib
> -Wl,-rpath,/home/alexander/Development/buildroot/output/host/usr/lib -o
> insmod.static insmod.o libmodtools.a
I guess you need /usr/lib/libc.a installed on your build system. I
think it's in the glibc-static package on Fedora.
If that makes the difference, it definitely should be in the
documentation. (On Debian derivatives, libc.a is a dependency of the
compiler so it will be there.)
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2012-05-01 8:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-01 6:35 [Buildroot] Fedora 16: Cannot find -lc Alexander Broekhuis
2012-05-01 8:21 ` Arnout Vandecappelle [this message]
2012-05-01 19:45 ` Thomas Petazzoni
2012-05-01 19:58 ` Alexander Broekhuis
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=4F9F9D01.2090407@mind.be \
--to=arnout@mind.be \
--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