All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mitch Davis <mjd+buildroot@afork.com>
To: buildroot@busybox.net
Subject: [Buildroot] Build error "cannot find -lc"
Date: Tue, 14 Sep 2010 14:09:49 +1000	[thread overview]
Message-ID: <AANLkTimH+esZGQRhRHTPuNb5aVLToQx8aNrdWLYgGWE0@mail.gmail.com> (raw)
In-Reply-To: <87d3sh7359.fsf@macbook.be.48ers.dk>

On Tue, Sep 14, 2010 at 7:19 AM, Peter Korsgaard <jacmet@uclibc.org> wrote:
>>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
>
>  Thomas> Hello,
>  Thomas> On Tue, 14 Sep 2010 02:37:22 +0900
>  Thomas> S W <sw18@hotmail.co.jp> wrote:
>
>  >> I checked the /lib and /usr/lib, but I couldn't find
>  >> glibc.a file.
>  >> So I did "yum install glibc-static" to install the libc.a file.
>  >> Now it is OK with this problem.
>
>  Thomas> Ok, thanks.
>
>  Thomas> Peter, what can we do about this ? Should we enforce the fact that
>  Thomas> glibc-static is installed globally ? Or just if host-module-init-tools
>  Thomas> is going to be compiled ?
>
> Globally I would say. host-module-init-tools probably isn't the only
> package that might want to link something statically.

I'm still confused as to why a host-side app should need to be static linked...

I would rather not install glibc.a on my host...

Mitch.

  reply	other threads:[~2010-09-14  4:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-10 22:16 [Buildroot] Build error "cannot find -lc" S W
2010-09-11  8:52 ` Thomas Petazzoni
2010-09-11 18:09   ` S W
2010-09-13 17:37     ` S W
2010-09-13 17:47       ` Thomas Petazzoni
2010-09-13 21:19         ` Peter Korsgaard
2010-09-14  4:09           ` Mitch Davis [this message]
2010-09-13 17:51     ` [Buildroot] Build error: No rule to make target `ubootboard_config' S W
2010-09-13 18:30       ` Thomas Petazzoni
2010-09-13 20:16         ` S W
2010-09-14 17:29           ` Marcus Osdoba

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=AANLkTimH+esZGQRhRHTPuNb5aVLToQx8aNrdWLYgGWE0@mail.gmail.com \
    --to=mjd+buildroot@afork.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 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.