Hi John,
On Wed, 2004-09-29 at 04:07, John J. Boyer wrote:
> On Redhat 8.0 and now on Debian Sarge, when I run ./configure I get the
> message that glib cannot be found.
I can report on the Debian/unstable distribution: the configure script
_finds_ glib-2.0, and glib-2.0 is also the name returned by
pkg-config --list-all
Have you installed the glib library in a location other than the default
one? That being the case, it should be sufficient to update the
PKG_CONFIG_PATH environment variable so that the relevant .pc files can
be found.
> I managed to fix the problem on
> Redhat, but on Debian glib-2.0 is present, but seems to have a different
> name. Changing the library path doesn't help. I think the configure script
> needs to be revised so it can find glib. A friend managed to get the
> configure to work, but I think this problem shouldn't be occuring.
I'm attaching the log messages I get when my copy of ./configure runs.
It would be helpful if you could provide your own log messages and also
to know if the command
pkg-config glib-2.0 --cflags
does work for you. Also, it would be interesting to see how your friend
patched the configuration script. Although I'm not an auto*guru, I might
get a better clue as to what is going on.
Cheers,
--luca
gdome2_configure.output
Description: Text document
signature.asc
Description: This is a digitally signed message part
_______________________________________________
gdome mailing list
gdome@xxxxxxxxx
http://mail.gnome.org/mailman/listinfo/gdome
|
