From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: klibc problems
Date: Tue, 21 Apr 2009 11:18:10 +0200 [thread overview]
Message-ID: <gsk30i$7bc$1@ger.gmane.org> (raw)
In-Reply-To: <49D3582F.4070304@xora.org.uk>
On 01-04-09 14:03, Graeme Gregory wrote:
> Ok, its no mystery to some people that klibc has problems with modern
> kernels.
>
> But I think we also have a problem with the package in OE. Seeing as
> klibc is machine dependent in that it includes mach-XXX/include/mach/*.h
> files it really should not be staged as part of the base arch. I think
> we need to stage it into ${MACHINE_ARCH} the same was as the kernel is.
>
> We can then work on fixing the application compiles. I think I have a
> suitable hack.
It will also fail in a multimachine environment and when you change
kernels. To address the second point I propose one of the following:
* make klibc nostamp
* make klibc use MACHINE_KERNEL_PR (and all kernels and machines using
klibc)
To address the first point I think we need to get Graeme's stuff in.
regards,
Koen
prev parent reply other threads:[~2009-04-21 9:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-01 12:03 klibc problems Graeme Gregory
2009-04-02 6:42 ` Khem Raj
2009-04-02 9:44 ` Graeme Gregory
2009-04-02 12:10 ` Jeremy Lainé
2009-04-21 9:18 ` Koen Kooi [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='gsk30i$7bc$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--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