Re: New release of GTK+ libraries (1.3.15). Please test!

[Arnaud Charlet <charlet ACT-Europe FR>]

> Well, thats pretty broken if you used gcc to build the library but not the
> program. If you have to know what compiler the shared library was built
> with (and potentially build/link the program with the same one) you are in
> the same situation that was supposed tobe bad about using c++...

In the case of Gtk+, it is *required* to use the same compiler for building
Gtk+ itself, and for compiling Gtk applications, since Gtk+ defines
some non portable/low level macros that are very compiler specific, so
this is not an argument.

concerning libgcc and shared libs, the situation is a little bit more
complicated than what has been described in other posts, but removing the
-no-undefined flags sounds like an acceptable and reasonable solution to me.

Arno