Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Cc: openembedded-devel@openembedded.org
Subject: Re: RFC: SDK/external-toolchain fixes
Date: Mon, 15 Sep 2008 03:18:49 -0400	[thread overview]
Message-ID: <20080915071849.GA7168@denix.org> (raw)
In-Reply-To: <20080913190643.GA14530@gmail.com>

On Sat, Sep 13, 2008 at 12:06:43PM -0700, Khem Raj wrote:
> >>>>> gcc 4.3.x has some GCC-provided headers in include-fixed (namely limits.h),
> >>>>> which are missing in the gcc-cross-sdk version, rendering external toolchain
> >>>>> unusable.
> >>>> I do not like this fix. IMO Instead of copying them into include directory
> >>>> they should be let alone in include-fixed directory and packaged. You should
> >>>> add knowledge of this new directory to the failing package instead. What
> >>>> packages are broken because of this.
> >>> 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 ?
> 
> I only did cross build/testing no target gcc stuff so I did not see this problem thus far.
> I thought gcc driver should have added include-fixed to default search paths for includes unless you disable it to do so like glibc does in such a case the application should add it to include search paths manually. 
> 
> If you can give more details about this failure on native build. I could try to dig more.

The proper fix seems to work fine. Thanks for applying the patch.

-- 
Denys



  parent reply	other threads:[~2008-09-15  7:21 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 [this message]
2008-09-19 21:01             ` Denys Dmytriyenko
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=20080915071849.GA7168@denix.org \
    --to=denis@denix.org \
    --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