From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] sanity.bbclass: Check for the presennce of libc.a
Date: Sun, 12 Sep 2010 11:36:57 +0100 [thread overview]
Message-ID: <1284287817.18010.7488.camel@rex> (raw)
In-Reply-To: <1284288866.4698.81.camel@lenovo.internal.reciva.com>
On Sun, 2010-09-12 at 11:54 +0100, Phil Blundell wrote:
> On Sun, 2010-09-12 at 17:24 +0800, Holger Freyther wrote:
> > The insmod.static binary links statically and requires the libc.a
> > to be present. On Fedora glibc-static is not installed by default
> > when installing development headers. Warn the user that he needs
> > to have that installed.
>
> Why are we building insmod.static for native anyway? That seems a bit
> silly.
It is. FWIW, Poky now patches the modutils-cross recipe so it only
builds the dynamically linked version to resolve exactly this issue.
Cheers,
Richard
next prev parent reply other threads:[~2010-09-12 10:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-12 9:24 [PATCH] sanity.bbclass: Check for the presennce of libc.a Holger Freyther
2010-09-12 10:54 ` Phil Blundell
2010-09-12 10:36 ` Richard Purdie [this message]
2010-09-12 12:52 ` Philip Balister
2010-09-12 13:01 ` Frans Meulenbroeks
2010-09-12 15:01 ` Holger Freyther
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=1284287817.18010.7488.camel@rex \
--to=rpurdie@rpsys.net \
--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.