From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: openembedded-devel@openembedded.org
Subject: Re: GCC 4.3 fails to build glibc(-intermediate)
Date: Thu, 22 May 2008 17:02:50 -0700 [thread overview]
Message-ID: <1211500970.10806.14.camel@isis> (raw)
In-Reply-To: <g14do2$eur$1@ger.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1425 bytes --]
On Thu, 2008-05-22 at 20:24 +0200, Rolf Leggewie wrote:
> 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
Looking at this file. I dont see any obvious problem unless you are
using armv7a and angstrom-2008.1
in this changeset the preferred gcc version has been changed from
4.2.3+csl-arm-2008q1-126 to 4.2.1+csl-arm-2007q3-53
Otherwise these changes look only like new gcc recipe has been added and
no common code is modified which could affect gcc 4.3
glibc changes also seems specific to armv7a
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 196 bytes --]
next prev parent reply other threads:[~2008-05-23 0:05 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
2008-05-23 0:02 ` Khem Raj [this message]
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=1211500970.10806.14.camel@isis \
--to=raj.khem@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox