From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: RFC: SDK/external-toolchain fixes
Date: Fri, 19 Sep 2008 17:01:18 -0400 [thread overview]
Message-ID: <20080919210118.GA4101@denix.org> (raw)
In-Reply-To: <20080915071849.GA7168@denix.org>
Khem,
On Mon, Sep 15, 2008 at 03:18:49AM -0400, Denys Dmytriyenko wrote:
> On Sat, Sep 13, 2008 at 12:06:43PM -0700, Khem Raj wrote:
> > >>> I agree that this is not a proper fix, but rather a hack. glibc has its own
> > >>> limits.h, which wants to include gcc's limits.h like this:
> > >>>
> > >>> This issue was brought up before, but as far as I can tell, it wasn't fixed
> > >>> properly.
> > >>> This is initial Koen's post about the issue:
> > >>> http://projects.linuxtogo.org/pipermail/openembedded-devel/2008-April/005108.html
> > >>> And here is your own reply with one of the possible solutions:
> > >>> http://projects.linuxtogo.org/pipermail/openembedded-devel/2008-April/005111.html
> > >>
> > >> right. So can you try this patch and see if this fixes the problem ?
>
> The proper fix seems to work fine. Thanks for applying the patch.
I see most of gcc-cross* recipes been cleaned removing the hack mentioned
above, but there are few more, mostly CodeSourcery ones. The patch for those
is in the ticket #4560:
http://bugs.openembedded.net/show_bug.cgi?id=4560
--
Denys
next prev parent reply other threads:[~2008-09-19 21:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-11 19:52 RFC: SDK/external-toolchain fixes Denys Dmytriyenko
2008-09-12 0:02 ` Khem Raj
2008-09-12 1:53 ` Denys Dmytriyenko
2008-09-12 2:11 ` Khem Raj
2008-09-12 7:40 ` Denys Dmytriyenko
2008-09-13 13:49 ` Koen Kooi
2008-09-13 19:06 ` Khem Raj
2008-09-13 19:34 ` Koen Kooi
2008-09-15 7:18 ` Denys Dmytriyenko
2008-09-19 21:01 ` Denys Dmytriyenko [this message]
2008-09-23 17:16 ` Denys Dmytriyenko
2008-09-23 18:44 ` Khem Raj
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=20080919210118.GA4101@denix.org \
--to=denis@denix.org \
--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.