From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Build failure module-init-tools-cross_3.2.2.bb on Fedora 12 x86_64
Date: Sun, 24 Jan 2010 10:45:47 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.00.1001241044240.14413@localhost> (raw)
In-Reply-To: <20100124154357.GG15943@jama>
On Sun, 24 Jan 2010, Martin Jansa wrote:
> On Sun, Jan 24, 2010 at 07:37:36PM +0400, Elvis Dowson wrote:
> > Hi,
>
> Hi
>
> > | /usr/bin/ld: cannot find -lc
> > | collect2: ld returned 1 exit status
> > | make: *** [insmod.static] Error 1
>
> Thomas White had the same problem and reported that:
>
> in F12 there's a separate package for glibc static linking ok, after
> installing the static package, it works
>
> Not sure if it's correct fix (I would expect that static libc should
> be in staging already for module-init-tools-cross), but you can give
> it a try.
i'm guessing that's it:
# yum install glibc-static
given that i run f12, i ran across that issue some time back.
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Kernel Pedantry.
Web page: http://crashcourse.ca
Twitter: http://twitter.com/rpjday
========================================================================
next prev parent reply other threads:[~2010-01-24 15:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-24 15:29 Build failure module-init-tools-cross_3.2.2.bb on Fedora 12 x86_64 Elvis Dowson
2010-01-24 15:37 ` Elvis Dowson
2010-01-24 15:43 ` Martin Jansa
2010-01-24 15:45 ` Robert P. J. Day [this message]
2010-01-24 15:47 ` Elvis Dowson
2010-01-24 17:36 ` Robert P. J. Day
2010-01-24 18:54 ` Technote Overo-031: How to setup a development environment for the Overo platform using a Fedora-12 x86 64-bit VMware image Elvis Dowson
2010-01-24 16:46 ` Build failure module-init-tools-cross_3.2.2.bb on Fedora 12 x86_64 Robert P. J. Day
2010-01-24 18:46 ` Elvis Dowson
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=alpine.LFD.2.00.1001241044240.14413@localhost \
--to=rpjday@crashcourse.ca \
--cc=openembedded-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.