From: Tomas Szepe <szepe@pinerecords.com>
To: Russell King <rmk@arm.linux.org.uk>
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 12:59:11 +0200 [thread overview]
Message-ID: <20020928105911.GU27082@louise.pinerecords.com> (raw)
In-Reply-To: <20020928091530.B32639@flint.arm.linux.org.uk>
> > > > -I/usr/src/linux-2.5.36/include
> > > > -iprefix /usr/sbin/../../lib/gcc-lib/i686-pc-linux-gnu/3.0.3/
> > >
> > > That's the problem. Where's the -iprefix coming from? Your configure
> > > doesn't specify /usr/sbin anywhere.
> > >
> > > Verdict: bad GCC install or a 3.0.3 bug. Might have to do with your
> > > libdir-outside-of-prefix.
> >
> > I've got the same problem with -nostdinc with my Debian gcc-3.0 that
> > I've been patching around. I assumed it was a problem with the
> > kernel's Makefile, now you're saying it's the Debian package?
>
> 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?
T.
next prev parent reply other threads:[~2002-09-28 10:54 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 [this message]
2002-09-28 17:26 ` Russell King
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=20020928105911.GU27082@louise.pinerecords.com \
--to=szepe@pinerecords.com \
--cc=dan@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oxymoron@waste.org \
--cc=rmk@arm.linux.org.uk \
--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 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.