All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rolf Leggewie <no2spam@nospam.arcornews.de>
To: openembedded-devel@openembedded.org
Subject: Re: GCC 4.3 fails to build glibc(-intermediate)
Date: Thu, 22 May 2008 20:24:04 +0200	[thread overview]
Message-ID: <g14do2$eur$1@ger.gmane.org> (raw)
In-Reply-To: <70c9a9110805220711i33fd397k518855a05773edf0@mail.gmail.com>

Enric Balletbò i Serra wrote:
> I have the same problem, but at this moment I don't have idea about solution.

I am also experiencing similar problems for a spitz build.  The problem
started to appear about a week ago.
f2497299e919cb94e12fc8690a709479451e5510 still builds fine.  I think the
most likely candidates that triggered this problem are to be found among
the changes to gcc that were made after that revision.  I see changes
from koen and RP in the commit-ml.  It would be nice if the people who
understand this stuff took a look to spot a possible regression.  I will
try and narrow the revision down further.

http://oss.leggewie.org/wip/f2497299e919cb94e12fc8690a709479451e5510_vs_HEAD.txt




  parent reply	other threads:[~2008-05-22 18:27 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <70c9a9110805220710x6663f582lc5d6b75744960d08@mail.gmail.com>
2008-05-22 14:11 ` GCC 4.3 fails to build glibc(-intermediate) Enric Balletbò i Serra
2008-05-22 15:44   ` Khem Raj
2008-05-22 18:24   ` Rolf Leggewie [this message]
2008-05-23  0:02     ` Khem Raj
2008-05-23  6:17       ` Rolf Leggewie
2008-05-23  6:36   ` Rolf Leggewie
2008-05-28  7:01   ` Khem Raj
2008-05-28  7:36     ` Koen Kooi
2008-05-28  9:52     ` Matthijs van de Water
2008-05-28 11:22       ` Rolf Leggewie
2008-06-03  7:16         ` Matthijs van de Water
2008-06-04 11:14           ` Koen Kooi
2008-06-04 23:22             ` Khem Raj
2008-05-07 14:33 Matthijs van de Water
2008-05-07 16:21 ` Khem Raj
2008-05-07 17:02   ` Matthijs van de Water
2008-05-07 18:31     ` Leon Woestenberg

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='g14do2$eur$1@ger.gmane.org' \
    --to=no2spam@nospam.arcornews.de \
    --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 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.