All of lore.kernel.org
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH][v3 3/4] uClibc: redo configuration
Date: Thu, 8 Jul 2010 13:41:25 -0700	[thread overview]
Message-ID: <AANLkTik9zItYpxBnFbOi2DlS--2dXbZntdwZ40AnEp19@mail.gmail.com> (raw)
In-Reply-To: <20100708202835.GC23169@mx.loc>

On Thu, Jul 8, 2010 at 1:28 PM, Bernhard Reutner-Fischer
<rep.dot.nop@gmail.com> wrote:
>
> you said you saw an ICE with current uclibc master. Which arch and which
> versions of the toolchain did you use?

The ICE is because of -Os -mthumb -fno-omit-frame-pointer because now we pass
CFLAGS into UCLIBC_EXTRA_CFLAGS which is right thing but it unveils this
issue. I have opened a gcc bug for the same
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44860

and deviced a local work around
to not pass -fno-omit-frame-pointer on arm. I wanted to use thumb override
to localize the workaround even more but thumb is added to OVERRIDES in machine
confs and bitbake does not pick it up when I apply it on
var_thumb := <....>
var_thumb = <....> seems to work ok.

Probably you did not use thumb instruction set when compiling for qemuarm
thats where the ICE happens.

I have to cobble up few recipes but now with your patches I can build bootable
x11-image and native-sdk-images on minimal. I am quite happy with what we have
thus far.

> FYI, i tested qemuarm, qemumips, qemuppc, qemux86 and (my local)
> qemux86_64 with
> PREFERRED_BINUTILS = "2.20.1" ¹)
> PREFERRED_GCC_VERSION = "4.5" ²) ³)

thats similar to what I have.

>
> and all of built fine for me.
>
> ¹) micro.conf incorrectly picks 2.19.51 per default, should be bumped
> ²) micro.conf should also default to 4.5
> ³) It would be great if we could settle on one scheme for
>   binutils/gcc/libc version shorthands:
>   PREFERRED_BINUTILS_VERSION _or_ PREFERRED_GCC, i'd go for
>   PREFERRED_foo_VERSION, uniformly.



  parent reply	other threads:[~2010-07-09 10:30 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-06 19:32 [PATCH][v3 0/4] honour {MACHINE, DISTRO}_FEATURES for configuration Bernhard Reutner-Fischer
2010-07-06 19:32 ` [PATCH][v3 1/4] busybox: configure according to {MACHINE, DISTRO}_FEATURES Bernhard Reutner-Fischer
2010-07-06 19:32 ` [PATCH][v3 2/4] busybox: picking IPv6 per default is not up to the package Bernhard Reutner-Fischer
2010-07-06 19:32 ` [PATCH][v3 3/4] uClibc: redo configuration Bernhard Reutner-Fischer
2010-07-08 19:02   ` Khem Raj
2010-07-08 20:28     ` Bernhard Reutner-Fischer
2010-07-08 20:31       ` Khem Raj
2010-07-08 20:44         ` Bernhard Reutner-Fischer
2010-07-08 20:41       ` Khem Raj [this message]
2010-07-08 20:47     ` Phil Blundell
2010-07-08 21:03       ` Khem Raj
2010-07-08 21:29         ` Phil Blundell
2010-07-08 21:31           ` Khem Raj
2010-07-08 21:34             ` Phil Blundell
2010-07-08 22:03               ` Khem Raj
2010-07-08 22:16                 ` Bernhard Reutner-Fischer
2010-07-08 22:55                   ` Khem Raj
2010-07-08 21:12       ` Khem Raj
2010-07-08 21:32         ` Phil Blundell
2010-07-08 22:01           ` Khem Raj
2010-07-06 19:32 ` [PATCH][v3 4/4] uclibc: add 0.9.31 Bernhard Reutner-Fischer

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=AANLkTik9zItYpxBnFbOi2DlS--2dXbZntdwZ40AnEp19@mail.gmail.com \
    --to=raj.khem@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=rep.dot.nop@gmail.com \
    /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.