Re: [PATCH][SPARSE] Runtime detection of gcc include paths
H. Peter Anvin (hpa@zytor.com)
8 Jun 2003 20:51:18 -0700
Followup to: <Pine.LNX.4.44.0306081807500.1849-100000@home.transmeta.com>
By author: Linus Torvalds <torvalds@transmeta.com>
In newsgroup: linux.dev.kernel
>
> On Sun, 8 Jun 2003, Ryan Anderson wrote:
> >
> > This uses the same method as previously was used, it just performs the
> > lookup at runtime.
>
> I much prefer a compile-time thing.
>
> Performance is, to me, paramount for "checker". I don't want to slow it
> down, I'm hoping that some day we can just enable C=1 by default in the
> kernel build (this is a _long_ time off, though, don't you all start
> worrying now).
>
> I don't see anything wrong with a compile/install time thing, that is,
> after all, how gcc too works.
>
Both of these seem a little unnecessary. Why not pass this stuff on
the command line, and have the top-level Makefile extract the paths
into a command-line argument?
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
Architectures needed: ia64 m68k mips64 ppc ppc64 s390 s390x sh v850 x86-64
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/