🚀 go-pugleaf

Craig Dewick wrote:
> 
> Hi,
> 
> I'm trying to build gtk+-1.2.3 so I can eventually build, install and use
> GIMP. However, there's one problem that I can't fathom at the moment.
> 
> I have already compiled and installed glib-1.2.3, and at one stage I had a
> problem earlier with the gtk build where it would find the glib-config
> program, but tried to tell me the wrong version of glib was installed (there
> is only one version - 1.2.3 - installed on the system). Running glib-config
> manually showed it was working, so the problem must have been in gtk's
> configure script.
> 
> Anyway, I resolved that one by using the following config options for gtk's
> configure script:
> 
> sh ./configure --prefix=/X --with-glib=/azwan/glib-1.2.3 --with-x
> 
> '/X' is my symlink to /usr/openwin. The '--with-glib' option got around the
> glib-searching problem with the script, and the build then progressed to the
> point it's at now, which is this:
> 
> /bin/sh ../libtool --mode=link gcc  -g -O2 -Wall  -o testgtk  testgtk.o
> libgtk.la                                               ../gdk/libgdk.la
> -L/usr/openwin/lib -R/usr/openwin/lib -lXext -lX11 -lsocket  -lnsl
> /azwan/glib-1.2.3/libglib.la /azwan/glib-1.2.3/gmodule.la -lm
> libtool: link: `/azwan/glib-1.2.3/gmodule.la' is not a valid libtool archive
> *** Error code 1
> make: Fatal error: Command failed for target `testgtk'
> Current working directory /azwan/X/gtk+-1.2.3/gtk
> *** Error code 1
> make: Fatal error: Command failed for target `all-recursive'
> Current working directory /azwan/X/gtk+-1.2.3
> *** Error code 1
> make: Fatal error: Command failed for target `all-recursive-am'
> 
> What does the error code about 'gmodule.la' mean? I had a look back through
> the glib directory and could not find any file named 'gmodule.la', so is the
> real meaning of the message simply that it can't find the file in question?
> 
> Running 'find' over the glib source directory shows these files have been
> created with a '.la' extension:
> 
> 77 root@lios #----> find /azwan/glib-1.2.3 -name "*.la" -print
> /azwan/glib-1.2.3/gmodule/.libs/libgmodule.la
> /azwan/glib-1.2.3/gmodule/.libs/libgplugin_a.la
> /azwan/glib-1.2.3/gmodule/.libs/libgplugin_b.la
> /azwan/glib-1.2.3/gmodule/libgmodule.la
> /azwan/glib-1.2.3/gmodule/libgplugin_a.la
> /azwan/glib-1.2.3/gmodule/libgplugin_b.la
> /azwan/glib-1.2.3/gthread/.libs/libgthread.la
> /azwan/glib-1.2.3/gthread/libgthread.la
> /azwan/glib-1.2.3/.libs/libglib.la
> /azwan/glib-1.2.3/libglib.la
> 
> but there's no 'gmodule.la'.
> 
> So at this point I'm a little confused... I'm probably mis-interpreting the
> use of the '--with-glib' and other glib-related config script options, or am
> I doing something else wrong?
> 
> Regards,
> 
> Craig.
> 

I had this problem. Symlink gmodule.la to libgmodule.la in the right
directory. There will be more errors. Keep symlinking. It will work
eventually. It looks like glib changed and didn't tell gtk.

-- 
So, quality-assured materials soon work effectively.