From: Aaron Lehmann <aaronl@vitelus.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2003@gmx.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [2.5] [Cool stuff] "checking" mode for kernel builds
Date: Mon, 26 May 2003 21:47:44 -0700 [thread overview]
Message-ID: <20030527044744.GJ9947@vitelus.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0305262009400.1680-100000@home.transmeta.com>
On Mon, May 26, 2003 at 08:23:37PM -0700, Linus Torvalds wrote:
> Any takers? Some Makefile magic plus some hacky thing like
>
> gcc -print-file-name=include
>
> (Yeah, that's not righ either, it just happens to work. I don't know what
> the proper way of making gcc expose its local paths is).
gcc -v will tell you the final include path, but only when you
actually compile something. I'd probably make the makefile hackery parse
the ouput of echo | gcc -v -E -. Yeah, it's ugly.
The output between "#include <...> search starts here:" and "End of
search list." seems like the combination of what you want for
gcc_includepath and sys_includepath. I assume the output is ordered. I
might send a patch if I'm bored tonight.
next prev parent reply other threads:[~2003-05-27 4:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-27 0:17 [2.5] [Cool stuff] "checking" mode for kernel builds Carl-Daniel Hailfinger
2003-05-27 0:25 ` John Anthony Kazos Jr.
2003-05-27 0:36 ` Linus Torvalds
2003-05-27 1:24 ` Carl-Daniel Hailfinger
2003-05-26 13:17 ` dan carpenter
2003-05-27 1:58 ` Miles Bader
2003-05-27 3:02 ` Aaron Lehmann
2003-05-27 3:23 ` Linus Torvalds
2003-05-27 4:47 ` Aaron Lehmann [this message]
2003-05-27 5:07 ` Linus Torvalds
2003-05-27 9:16 ` Ryan Anderson
2003-05-27 14:44 ` Linus Torvalds
2003-05-27 11:03 ` dep
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=20030527044744.GJ9947@vitelus.com \
--to=aaronl@vitelus.com \
--cc=c-d.hailfinger.kernel.2003@gmx.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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.