From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: problems compiling glibc_2.9-r37.4 under Angstrom
Date: Fri, 21 Jan 2011 16:21:55 -0800 [thread overview]
Message-ID: <AANLkTinnrY2o___wOwe3vqrYfY8QsBQYE6AA7VFuAq7T@mail.gmail.com> (raw)
In-Reply-To: <ihbp5c$4ov$1@dough.gmane.org>
On Fri, Jan 21, 2011 at 3:03 AM, Koen Kooi <k.kooi@student.utwente.nl> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 20-01-11 19:12, Víctor M. Jáquez L. wrote:
>>
>> In order to build native-sdk-image recipe, I found my self compiling
>> glibc_2.9-r37.4, because it is the real provider of virtual-libc-dev (the
>> toolchain does not truly provide it -but that is another bug [1]-).
>>
>> But the glibc_2.9-r37.4 configuration fails using the canonical
>> arm-angstrom-linux-gnueabi- toolchain
>
> If you're using angstrom 2008, glibc 2.9 is built by default. Trying to
> rebuild it won't work because it will be missing headers due to all the
> - -initial and -intermedia shuffle.
> If you're using angstrom 2010, eglibc is built by default and should
> providing virtual-libc-dev
yes angstrom-2010.x is a better option keep in mind its new so expect
some churn every now and then.
>
> Switching to minimal will only get you anguish, since it's broken by design.
Heh interesting :) It would help if you elaborate on the flaws so we
can improve it and in turn improve OE in general
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (Darwin)
>
> iD8DBQFNOWfsMkyGM64RGpERAsqfAKC2L5KDSLLBSC0tES2r+Axm+rxGoQCfVssG
> IDR7J61eU9hEKOTT2+CRW9M=
> =R8yc
> -----END PGP SIGNATURE-----
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
next prev parent reply other threads:[~2011-01-22 0:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-20 18:12 problems compiling glibc_2.9-r37.4 under Angstrom Víctor M. Jáquez L.
2011-01-20 21:40 ` Khem Raj
2011-01-21 10:21 ` Víctor M. Jáquez L.
2011-01-22 11:29 ` Frans Meulenbroeks
2011-01-21 11:03 ` Koen Kooi
2011-01-21 11:29 ` Frans Meulenbroeks
2011-01-21 11:34 ` Dr. Michael Lauer
2011-01-21 14:30 ` Philip Balister
2011-01-21 15:12 ` Dr. Michael Lauer
2011-01-24 16:46 ` Dr. Michael Lauer
2011-01-24 16:49 ` Graeme Gregory
2011-01-24 19:59 ` Board meeting, was: " Philip Balister
2011-01-22 0:29 ` Khem Raj
2011-01-22 12:10 ` Frans Meulenbroeks
2011-01-22 0:21 ` Khem Raj [this message]
2011-01-22 11:10 ` Koen Kooi
2011-01-22 12:36 ` Frans Meulenbroeks
2011-01-22 12:39 ` Frans Meulenbroeks
2011-01-22 15:28 ` Graeme Gregory
2011-01-22 16:30 ` Frans Meulenbroeks
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=AANLkTinnrY2o___wOwe3vqrYfY8QsBQYE6AA7VFuAq7T@mail.gmail.com \
--to=raj.khem@gmail.com \
--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.