All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Víctor M. Jáquez L." <vjaquez@igalia.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: problems compiling glibc_2.9-r37.4 under Angstrom
Date: Fri, 21 Jan 2011 11:21:02 +0100	[thread overview]
Message-ID: <20110121102102.GA7400@lit.local.igalia.com> (raw)
In-Reply-To: <AANLkTin6XfEpo_ic0Edp8+58EbzGutuhohM-V4EzzwhJ@mail.gmail.com>

On Thu, Jan 20, 2011 at 01:40:19PM -0800, Khem Raj wrote:
> 2011/1/20 Víctor M. Jáquez L. <vjaquez@igalia.com>:
> >
> > 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 (using the csl external toolchain fails
> > too, but for other reasons):
> >
> > Log data follows:
> > [snip]
> 
> 
> you might try to use eglibc. It may fix this issue for you.
> 

Thanks. I'm giving a try to minimal distribution according to Yuri's
observation [1].

1. http://lists.linuxtogo.org/pipermail/openembedded-devel/2011-January/028950.html



  reply	other threads:[~2011-01-21 10:21 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. [this message]
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
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=20110121102102.GA7400@lit.local.igalia.com \
    --to=vjaquez@igalia.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.