This is the mail archive of the mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: libstdc++/3465: Using option -I/usr/include breaks bits/std_c*.h

From: neil at gcc dot gnu dot org
Date: 28 Jun 2001 19:51:00 -0000
> Synopsis: Using option -I/usr/include breaks bits/std_c*.h
> State-Changed-From-To: open->closed
> State-Changed-By: neil
> State-Changed-When: Thu Jun 28 12:51:00 2001
> State-Changed-Why:
>     Don't use -I/usr/include; it's wrong for this reason (KDE, right?).

It is not so easy to avoid giving -I/usr/include to gcc.

I am trying to compile gnomemm-1.2.0:

Its configure script tries to compile a gtk-- test program, but
that fails under g++ 3.0.  The -I/usr/include switch comes from
scripts like gtkmm-config or gnome-config, or from the gnome--.m4
Autoconf macro of the gnomemm project.  Actually, those scripts
use an expression like -I$prefix/include, which only becomes a
problem if $prefix is /usr.

I have tried to patch the gnomemm configure script so that it would
take out all occurences of -I/usr/include with a `sed' command,
but I failed and gave up.  It would be much easier if gcc 3.0
behaved correctly, like 2.95.2 did.

Can someone point me to the place in the gcc 3.0 sources where
I could cancel the code that is responsible for this problem?


Pierre Sarrazin <sarrazip at sympatico dot ca>

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]