public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@ocs.com.au>
To: Chris Friesen <cfriesen@nortelnetworks.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: correct to set -nostdinc and then include <stdarg.h> ?
Date: Mon, 07 Apr 2003 15:15:12 +1000	[thread overview]
Message-ID: <23076.1049692512@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Mon, 07 Apr 2003 00:41:22 -0400." <3E910172.8030406@nortelnetworks.com>

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".

Try this:

Index: 66.1/Makefile
--- 66.1/Makefile Tue, 25 Mar 2003 11:23:27 +1100 kaos (linux-2.5/I/d/12_Makefile 1.45.1.4.1.59 444)
+++ 66.1(w)/Makefile Mon, 07 Apr 2003 15:13:54 +1000 kaos (linux-2.5/I/d/12_Makefile 1.45.1.4.1.59 444)
@@ -177,7 +177,7 @@ LDFLAGS_MODULE  = -r
 CFLAGS_KERNEL	=
 AFLAGS_KERNEL	=
 
-NOSTDINC_FLAGS  = -nostdinc -iwithprefix include
+NOSTDINC_FLAGS  = -nostdinc $(shell LANG=C $(CC) -print-search-dirs | sed -ne 's/install: \(.*\)/-I \1include/gp')
 
 CPPFLAGS	:= -D__KERNEL__ -Iinclude
 CFLAGS 		:= $(CPPFLAGS) -Wall -Wstrict-prototypes -Wno-trigraphs -O2 \


  reply	other threads:[~2003-04-07  5:04 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 [this message]
2003-04-07  6:47   ` Russell King
2003-04-07 14:08     ` Chris Friesen
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=23076.1049692512@kao2.melbourne.sgi.com \
    --to=kaos@ocs.com.au \
    --cc=cfriesen@nortelnetworks.com \
    --cc=linux-kernel@vger.kernel.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