Re: Hard-coded gcc header path

[Bernd Petrovitsch <bernd@firmix.at>]

On Die, 2008-11-11 at 23:32 +0100, Jörn Engel wrote:
[...]
> Either sparse gets smart enough to find the headers [1] or it ships its
> own set.  Anything else will continue to fail on one machine or another.

I don't think that shipping a copy of .h files from one gcc version will
seriously help people using `pcc` (or any other compiler).
But I'm probably missing something here.

> [1] Bernd Petrovitsch sent me this neat one-liner in a private mail:
> gcc -v -E - </dev/null 2>&1 >/dev/null | sed -n -e '/^#include <\.\.\.> search starts here:/,/^End of search list\./s/^ \(.*\)/\1/p
> 
> We could add that to cgcc to set additional include paths.

And there probably are similar ones for `pcc` or others.

	Bernd
-- 
Firmix Software GmbH                   http://www.firmix.at/
mobil: +43 664 4416156                 fax: +43 1 7890849-55
          Embedded Linux Development and Services

--
To unsubscribe from this list: send the line "unsubscribe linux-sparse" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html