From: Enrico Weigelt <weigelt@metux.de>
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] Auto Repair Cross Includes?
Date: Sat, 15 Nov 2008 06:22:09 +0100 [thread overview]
Message-ID: <20081115052209.GA21400@nibiru.local> (raw)
In-Reply-To: <1222017153.9939.82.camel@media>
* Ned Ludd <solar@gentoo.org> schrieb:
Hi,
> I've been toying with an idea after seeing a patch which would abort()
> when it detected host includes for cross compiles.
Funny idea, sorts out the dozens of crap makefiles easily (eg. written
by those mindless jerks who refuse to learn not to use absolute pathes
or explicitly add standard includes).
> I did not like the idea of aborting as it prevented me from building
> pkgs that had the same headers in $ROOT as /.
sucessfully shot yourself ? ;-o
> Basic goal detect ^/usr/include and rewrite it to $ROOT/usr/include if
> using a cross compiler and ROOT is set.
#1: why not using the more standard and well-known $SYSROOT variable ?
#2: why not just using the already existing '=' prefix ?
#3: WTH do you explicitly add an standard include path like
/usr/include ?! It's automatically done by gcc nothings an
individual application has to cope with.
cu
--
---------------------------------------------------------------------
Enrico Weigelt == metux IT service - http://www.metux.de/
---------------------------------------------------------------------
Please visit the OpenSource QM Taskforce:
http://wiki.metux.de/public/OpenSource_QM_Taskforce
Patches / Fixes for a lot dozens of packages in dozens of versions:
http://patches.metux.de/
---------------------------------------------------------------------
next prev parent reply other threads:[~2008-11-15 5:25 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
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 [this message]
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=20081115052209.GA21400@nibiru.local \
--to=weigelt@metux.de \
--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