From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: openembedded-devel@openembedded.org
Subject: Re: building module-init-tools-cross fails
Date: Tue, 20 Oct 2009 14:50:48 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.00.0910201450110.29057@localhost> (raw)
In-Reply-To: <19c1b8a90910201108u1ad326c3w251d73e793d1b848@mail.gmail.com>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 2497 bytes --]
On Tue, 20 Oct 2009, Khem Raj wrote:
> On Fri, Oct 2, 2009 at 6:32 PM, Sashan Govender <sashang@gmail.com> wrote:
> > I'm trying out openembedded but get this error:
> >
> > ERROR: function do_compile failed
> > ERROR: log data follows
> > (/home/sashan/code/openembedded/build/tmp/work/i486-oe-linux-gnu/module-init-tools-cross-3.2.2-r5/temp/log.do_compile.12217)
> > | NOTE: make
> > | gcc -isystem/home/sashan/code/openembedded/build/tmp/staging/x86_64-linux/usr/include
> > -O2 -g -Wunused -Wall -static
> > -L/home/sashan/code/openembedded/build/tmp/staging/x86_64-linux/usr/lib
> > -Wl,-rpath-link,/home/sashan/code/openembedded/build/tmp/staging/x86_64-linux/usr/lib
> > -Wl,-rpath,/home/sashan/code/openembedded/build/tmp/staging/x86_64-linux/usr/lib
> > -Wl,-O1 -o insmod.static insmod.o
> > | /usr/bin/ld: cannot find -lc
> > | collect2: ld returned 1 exit status
> > | make: *** [insmod.static] Error 1
> > | FATAL: oe_runmake failed
> >
> > This is my local.conf file:
> >
> > DL_DIR = "${HOME}/archives"
> > BBFILES = ${OEBASE}/openembedded/recipes/*/*.bb
> > BBMASK = ""
> > PREFERRED_PROVIDERS = "virtual/qte:qte virtual/libqpe:libqpe-opie"
> > PREFERRED_PROVIDERS += " virtual/libsdl:libsdl-x11"
> > PREFERRED_PROVIDERS += " virtual/${TARGET_PREFIX}gcc-initial:gcc-cross-initial"
> > PREFERRED_PROVIDERS += "
> > virtual/${TARGET_PREFIX}gcc-intermediate:gcc-cross-intermediate"
> > PREFERRED_PROVIDERS += " virtual/${TARGET_PREFIX}gcc:gcc-cross"
> > PREFERRED_PROVIDERS += " virtual/${TARGET_PREFIX}g++:gcc-cross"
> > MACHINE = "x86"
> > TARGET_OS = "linux"
> > DISTRO = "minimal"
> > IMAGE_FSTYPES = "jffs2 tar"
> > BINCLUDELOGS = "yes"
> >
> > What am I missing?
>
> its looking for libc.a on your build machine because you are linking
> static version. Depending upon what distro you run on
> your host you can install appropriate package. e.g on debian/ubuntu
> libc6-dev provides it.
if you're running fedora, you need to separately install the
"glibc-static" package.
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Annoying Kernel Pedantry.
Web page: http://crashcourse.ca
Twitter: http://twitter.com/rpjday
========================================================================
prev parent reply other threads:[~2009-10-20 18:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-03 1:32 building module-init-tools-cross fails Sashan Govender
2009-10-20 18:08 ` Khem Raj
2009-10-20 18:23 ` Philip Balister
2009-10-20 18:50 ` Robert P. J. Day [this message]
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.0910201450110.29057@localhost \
--to=rpjday@crashcourse.ca \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox