Re: [gtkmm] Problem compiling libglademm 1.3.0

["Marcelo E. Magallon" <marcelo magallon bigfoot com>]

>> Murray Cumming <murrayc usa net> writes:

 > > > g++ -DHAVE_CONFIG_H -I. -I. -I../../libglade 
 > > > -I/usr/local/include/gtkmm-2.0 -I/usr/local/lib/gtkmm-2.0/include 
 > > > -I/usr/local/include/gtk-2.0 -I/usr/local/lib/sigc++-1.2/include 
 > > > -I/usr/local/include/sigc++-1.2 -I/usr/local/include/glib-2.0 
 > > > -I/usr/local/lib/glib-2.0/include -I/usr/local/lib/gtk-2.0/include 
 > > > -I/usr/local/include/pango-1.0 -I/usr/X11R6/include 
 > > > -I/usr/local/include -I/usr/local/include/freetype2 
       ^^^^^^^^^^^^^^^^^^^^
 > > > -I/usr/local/include/atk-1.0 -I/usr/local/include/libglade-2.0 
 > > > -I/usr/local/include/libxml2    -O3 -march=i686  -O3 -march=i686 -c 
 > > > generate_defs_libglade.cc
 > > > cc1plus: warning: changing search order for system directory 
 > > > "/usr/local/include"
 > > > cc1plus: warning:   as it has already been specified as a non-system 
 > > > directory

 Pierre, it'd be useful if you specify your compiler version (and Linux
 distribution if this is Linux).
 
 > This is quite unusual. I would not expect us to have this problem
 > with pkg-config. Could you tell us about your system? If this is a
 > home-grown non-standard distribution then I don't care about it.

 IIRC there's a gcc release out there which has this problem.  Basically
 cpp doesn't like the idea of having /usr/local/include specified twice,
 because the first time it's been specified as a compiler include
 directory.  But anyway, this is a warning, it shouldn't matter.  You
 just should keep in mind that /usr/local/include is being searched
 before other -I's in the command line.

 I'd examine the contents of /usr/local/include more closely.  Perhaps
 there's a /usr/local/include/gtk or something like that which is
 getting in the way.

-- 
Marcelo