From: Chris Friesen <cfriesen@nortelnetworks.com>
To: Russell King <rmk@arm.linux.org.uk>
Cc: Keith Owens <kaos@ocs.com.au>, linux-kernel@vger.kernel.org
Subject: Re: correct to set -nostdinc and then include <stdarg.h> ?
Date: Mon, 07 Apr 2003 10:08:44 -0400 [thread overview]
Message-ID: <3E91866C.2000902@nortelnetworks.com> (raw)
In-Reply-To: 20030407074722.A9367@flint.arm.linux.org.uk
Russell King wrote:
> On Mon, Apr 07, 2003 at 03:15:12PM +1000, Keith Owens wrote:
>>On Mon, 07 Apr 2003 00:41:22 -0400,
>>Chris Friesen <cfriesen@nortelnetworks.com> wrote:
>>
>>>I was trying to compile 2.5.66 with gcc 3.2.2. It dies as soon as it tries to
>>>compile init/main.c because it is unable to find "stdarg.h" which is included by
>>>"include/linux/kernel.h".
>>>
>
> stdarg.h is part of the compiler specific includes. We want to pick
> up on these, so we use "-iwithprefix include" to add the compiler specific
> includes back.
It doesn't seem to work with gcc 3.2.2 then.
> Unfortunately, there seems to be something wrong with GCC's ability to
> determine where these includes really reside when GCC is installed in
> a different location to the one it was configured with. In other words,
> don't do that. Install GCC to the location where you told it to be
> installed.
gcc was configured with a prefix of "/usr/local/gcc322" and installed using
"make install". It still gave the error. Is this a gcc bug? I'm at work now,
but I can run the command you gave this evening to check the results.
Chris
--
Chris Friesen | MailStop: 043/33/F10
Nortel Networks | work: (613) 765-0557
3500 Carling Avenue | fax: (613) 765-2986
Nepean, ON K2H 8E9 Canada | email: cfriesen@nortelnetworks.com
next prev parent reply other threads:[~2003-04-07 13:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-07 4:41 correct to set -nostdinc and then include <stdarg.h> ? Chris Friesen
2003-04-07 5:15 ` Keith Owens
2003-04-07 6:47 ` Russell King
2003-04-07 14:08 ` Chris Friesen [this message]
2003-04-07 14:16 ` Martin Schlemmer
2003-04-07 14:44 ` Chris Friesen
2003-04-07 23:00 ` Daniel Jacobowitz
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=3E91866C.2000902@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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