public inbox for gentoo-embedded@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ahmed Ammar <b33fc0d3@gentoo.org>
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] Auto Repair Cross Includes?
Date: Mon, 22 Sep 2008 10:45:48 +0200	[thread overview]
Message-ID: <1222073148.27532.17.camel@localhost.localdomain> (raw)
In-Reply-To: <1222017153.9939.82.camel@media>

On Sun, 2008-09-21 at 10:12 -0700, Ned Ludd wrote:
> I've been toying with an idea after seeing a patch which would abort()
> when it detected host includes for cross compiles. I did not like the
> idea of aborting as it prevented me from building pkgs that had the same
> headers in $ROOT as /. I did like the fact there was a little QA I could
> slip in there. After thinking about it a while. I said fsck the QA and
> just fixed the problem. Here is what I came up with for gcc-4.2.4.. 
> 
> While in my testing I'm finding this works beautifully. However I'd like
> some input from others on what they think of such an idea. 
> Good/Bad/Other?
> 
> Basic goal detect ^/usr/include and rewrite it to $ROOT/usr/include if
> using a cross compiler and ROOT is set.

I really like this idea, seems clean and simple to do it from gcc. I
haven't tested this out yet though but I can't see why it wouldn't work.


-- 
Ahmed Ammar (b33fc0d3 [at] gentoo.org)




  reply	other threads:[~2008-09-22  8:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-21 17:12 [gentoo-embedded] Auto Repair Cross Includes? Ned Ludd
2008-09-22  8:45 ` Ahmed Ammar [this message]
2008-10-26  8:14 ` Mike Frysinger
2008-10-26 16:39   ` Ned Ludd
2008-10-26 20:07     ` Mike Frysinger
2008-11-15  5:22 ` Enrico Weigelt
2009-02-05 15:32 ` Christopher Friedt
2009-02-05 22:26   ` Ned Ludd

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=1222073148.27532.17.camel@localhost.localdomain \
    --to=b33fc0d3@gentoo.org \
    --cc=gentoo-embedded@lists.gentoo.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