From: Christoph Hellwig <hch@lst.de>
To: marcelo@conectiva.com.br
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] use -iwithprefix to find gcc headers
Date: Sun, 25 Aug 2002 20:33:36 +0200 [thread overview]
Message-ID: <20020825203336.A2787@lst.de> (raw)
Use -iwithprefix instead of my crude gcc -print-search-dirs hack to find
the directory where gcc puts stdarg.h. Backport from 2.5.
diff -uNr -Xdontdiff -p linux-2.4.20-pre4/Makefile linux/Makefile
--- linux-2.4.20-pre4/Makefile Tue Aug 20 11:36:59 2002
+++ linux/Makefile Tue Aug 20 11:39:48 2002
@@ -260,7 +260,7 @@ include arch/$(ARCH)/Makefile
# 'kbuild_2_4_nostdinc :=' or -I/usr/include for kernel code and you are not UML
# then your code is broken! KAO.
-kbuild_2_4_nostdinc := -nostdinc $(shell $(CC) -print-search-dirs | sed -ne 's/install: \(.*\)/-I \1include/gp')
+kbuild_2_4_nostdinc := -nostdinc -iwithprefix include
export kbuild_2_4_nostdinc
export CPPFLAGS CFLAGS CFLAGS_KERNEL AFLAGS AFLAGS_KERNEL
reply other threads:[~2002-08-25 18:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20020825203336.A2787@lst.de \
--to=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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