Re: what's the deal with libgmodule?



Ok, here's my final fix:

--- glib/glib-config.in.orig Wed Aug 26 19:48:53 1998
+++ glib/glib-config.in      Wed Aug 26 19:49:07 1998
@@ -26,6 +26,7 @@
 fi
 
 lib_glib=yes
+lib_gmodule=yes
 
 while test $# -gt 0; do
   case "$1" in

(end)

This is off of a fresh glib CVS checkout.

If you don't make this change, then how is glib-config supposed to
report that you need to link against libgmodule and libdl?  That failure
propogates up the entire source chain.  I think that this is as low as it
goes, and I think that the fix is appropriate, given that the variable
lib_glib is already hard-coded to "yes".  (I.e., I don't think that the
"gmodule" flag is significant.)

--
Todd Graham Lewis            32°49'N,83°36'W          (800) 719-4664, x2804
******Linux******         MindSpring Enterprises      tlewis@mindspring.net



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]