From: Russell King <rmk@arm.linux.org.uk>
To: Tomas Szepe <szepe@pinerecords.com>
Cc: Oliver Xymoron <oxymoron@waste.org>,
Daniel Jacobowitz <dan@debian.org>,
Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>,
linux-kernel@vger.kernel.org
Subject: Re: Does kernel use system stdarg.h?
Date: Sat, 28 Sep 2002 18:26:43 +0100 [thread overview]
Message-ID: <20020928182643.A13064@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20020928105911.GU27082@louise.pinerecords.com>; from szepe@pinerecords.com on Sat, Sep 28, 2002 at 12:59:11PM +0200
On Sat, Sep 28, 2002 at 12:59:11PM +0200, Tomas Szepe wrote:
> > It certainly looks like it. gcc 3.0.3 appears to ignore
> > "-iwithprefix include", where as gcc 2.95.x, 2.96, 3.1 and 3.2 all
> > work as expected.
>
> No. Try building/installing gcc-3.2 with '--prefix=/usr/gcc-3.2'
> and '--prefix=/usr'. The former won't work with '-iwithprefix include',
> the latter will. GCC build bug?
Maybe.
I've just checked the GCC 3.2 info files, and it appears that the
definition of -iwithprefix has changed.
gcc 2.9[156] comes with this description:
`-iwithprefix DIR'
Add a directory to the second include path. The directory's name
is made by concatenating PREFIX and DIR, where PREFIX was
specified previously with `-iprefix'. If you have not specified a
prefix yet, the directory containing the installed passes of the
compiler is used as the default.
whereas gcc 3.2 comes with:
`-iwithprefix DIR'
`-iwithprefixbefore DIR'
Append DIR to the prefix specified previously with `-iprefix', and
add the resulting directory to the include search path.
`-iwithprefixbefore' puts it in the same place `-I' would;
`-iwithprefix' puts it where `-idirafter' would.
Use of these options is discouraged.
This seems to leave us with no official guaranteed way to get at the
compiler specific includes, which is Bad News(tm). We obviously can't
use "-I/usr/lib/gcc-lib/`gcc -dumpmachine`/`gcc -dumpversion`/" and
we've already had problems with the 2.4 "gcc -print-search-dirs"
version.
This leaves us with one option:
gcc -print-file-name=include
This works, but its also not official:
`-print-file-name=LIBRARY'
Print the full absolute name of the library file LIBRARY that
would be used when linking--and don't do anything else. With this
option, GCC does not compile or link anything; it just prints the
file name.
Maybe we need to go back to the gcc folk and get -iwithprefix
reinstated...
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
"I know toolchain people. They _love_ to change things."
next prev parent reply other threads:[~2002-09-28 17:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-27 12:58 Does kernel use system stdarg.h? Denis Vlasenko
2002-09-27 8:26 ` Russell King
2002-09-27 13:20 ` Denis Vlasenko
2002-09-27 9:31 ` Mikael Pettersson
2002-09-27 17:18 ` Denis Vlasenko
2002-09-27 14:05 ` Daniel Jacobowitz
2002-09-27 21:47 ` Oliver Xymoron
2002-09-28 8:15 ` Russell King
2002-09-28 9:34 ` Alan Cox
2002-09-28 10:59 ` Tomas Szepe
2002-09-28 17:26 ` Russell King [this message]
2002-09-29 1:16 ` Keith Owens
2002-09-28 15:13 ` Oliver Xymoron
[not found] ` <20020927140302.B13401@flint.arm.linux.org.uk>
2002-09-30 12:58 ` Denis Vlasenko
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=20020928182643.A13064@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=dan@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oxymoron@waste.org \
--cc=szepe@pinerecords.com \
--cc=vda@port.imtp.ilyichevsk.odessa.ua \
/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