All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Schuster <theBohemian@gmx.net>
To: openembedded-devel@lists.openembedded.org
Cc: Koen Kooi <k.kooi@student.utwente.nl>
Subject: Re: [oe-commits] org.oe.dev glibc 2.6.1: change optimizations flags for	armv7a
Date: Thu, 10 Jul 2008 15:19:46 +0200	[thread overview]
Message-ID: <48760C72.8090608@gmx.net> (raw)
In-Reply-To: <20080706092603.9E5F3189303@amethyst.openembedded.net>

[-- Attachment #1: Type: text/plain, Size: 727 bytes --]

koen commit schrieb:
> glibc 2.6.1: change optimizations flags for armv7a
> * If the rebuild fails in do_configure, build glibc-initial to get limits.h in a place where glibc can find it. Builds from scratch works great, though

Just for the records

If you see this error:

checking how to run the C preprocessor... arm-angstrom-linux-gnueabi-gcc -E
configure: error: C preprocessor "arm-angstrom-linux-gnueabi-gcc -E"
fails sanity check
See `config.log' for more details.
FATAL: oe_runconf failed

you need to run:

bitbake -f -c fetch gcc-cross-initial && bitbake gcc-cross-initial

and then glibc intermediate to fix this.

In short rebuild gcc-cross-initial not glibc-initial. :)

Regards
Robert


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

       reply	other threads:[~2008-07-10 13:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20080706092603.9E5F3189303@amethyst.openembedded.net>
2008-07-10 13:19 ` Robert Schuster [this message]
2008-07-10 13:21   ` [oe-commits] org.oe.dev glibc 2.6.1: change optimizations flags for armv7a Koen Kooi

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=48760C72.8090608@gmx.net \
    --to=thebohemian@gmx.net \
    --cc=k.kooi@student.utwente.nl \
    --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.