Re: egcs 1.1a on DEC alpha OSF/3.2, problem with include files

[kuball at zedo dot fuedo dot de]

On 10 Sep , Alexandre Oliva wrote:
> kuball  <kuball@zedo.fuedo.de> writes:
> 
>> Where can I find an explanation of the structure of the temp files?
> 
> It is just the output of the preprocessor.  All macros and #includes
> are expanded, and #ifs are resolved.  Lines starting with `#' indicate 
> the line number and file their following lines come from.
> 
>> Looking at test.ii gives no answers, but new questions: there is no
>> prototype for strcmp in the temp file, either. So why does the compiler
>> warn about strncmp but not about strcmp???
> 
> Are you sure?  I haven't got access to an OSF/3.2 host, only to 4.0,
> but strcmp shows up in the preprocessed output for me.  Does string.h
> appear in the preprocessed output?  Is it read from the directory
> where you expect it to live?

No :(. It's read from /usr/local/lib/g++-include. But this are old
include files belonging to gcc 2.7. Well, I specified
	--enable-version-specific-runtime-libs
when buildng egcs. How come that the above directory is added to the
default search path? And how can I remove it from the default search
path?


Martin Kuball