egcs 1.1a on DEC alpha OSF/3.2, problem with include files
Alexandre Oliva
oliva@dcc.unicamp.br
Fri Sep 11 22:38:00 GMT 1998
kuball <kuball@zedo.fuedo.de> writes:
> On 10 Sep , Alexandre Oliva wrote:
>> kuball <kuball@zedo.fuedo.de> writes:
>>> 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???
>> 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.
`make install' won't clean up the g++-include directory, because it
might contain something useful.
> Well, I specified
> --enable-version-specific-runtime-libs
> when buildng egcs.
But include-files are not libraries, right? :-)
> How come that the above directory is added to the default search
> path?
I guess it is searched by default. Run `g++ -E -v - < /dev/null' to
check what the search path is.
> And how can I remove it from the default search path?
You may want to configure
--with-gxx-include-dir=/usr/local/include/eg++-1.1 or
--with-local-prefix=/usr/local/egcs or even with
--prefix=/usr/local/egcs-1.1
I'm not sure which one will fix your problem, but one of them should
do it, but each one will have different side-effects. I myself prefer
to install each package in a separate directory, so I'd use the last
option. However, this may not eliminate the possibility of having
/usr/local/lib/g++-include installed in the search path :-(
--
Alexandre Oliva
mailto:oliva@dcc.unicamp.br mailto:aoliva@acm.org
http://www.dcc.unicamp.br/~oliva
Universidade Estadual de Campinas, SP, Brasil
More information about the Gcc-bugs
mailing list