🚀 go-pugleaf

cdewick@lios.apana.org.au (Craig Dewick) writes:

> 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?
> 

I think it's actually due to the fact that the libtool supplied with most gnu
software really _hates_ solaris. I'd recommend that you firstly download and
install the absolute latest version of libtool (since this is more
solaris-friendly), and then go through your configure scripts and change 


# Always use our own libtool.
LIBTOOL='$(SHELL) $(top_builddir)/libtool'


to the following:

# Always use our own libtool.
#LIBTOOL='$(SHELL) $(top_builddir)/libtool'
LIBTOOL=/usr/local/bin/libtool   


instead, where /usr/local/bin/libtool is your own locally built version.

Everything should work just fine then.


James
--
Unix Systems Administrator            Phone: +61.2.9850.9418
Office of Computing Services            Fax: +61.2.9850.7433
Macquarie University   NSW    2109     
AUSTRALIA			     

In <kiyso5koane.fsf@orrery.ocs.mq.edu.au> James.McPherson@mq.edu.au (James C. McPherson) writes:

>> /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?
>> 

>I think it's actually due to the fact that the libtool supplied with most gnu
>software really _hates_ solaris. I'd recommend that you firstly download and
>install the absolute latest version of libtool (since this is more
>solaris-friendly), and then go through your configure scripts and change 


># Always use our own libtool.
>LIBTOOL='$(SHELL) $(top_builddir)/libtool'


>to the following:

># Always use our own libtool.
>#LIBTOOL='$(SHELL) $(top_builddir)/libtool'
>LIBTOOL=/usr/local/bin/libtool   


>instead, where /usr/local/bin/libtool is your own locally built version.

>Everything should work just fine then.

Except that it doesn't. I installed libtool-1.3.3 locally, and changed the
definitions in the configure scripts so they invoke the locally installed
copy of libtool in /usr/local/bin, however the result is exactly the same:

libtool: link: `/azwan/glib-1.2.3/gmodule.la' is not a valid libtool archive
*** Error code 1

The problem of why gmodule.la is needed for this step of building gtk, and
also why it's not created when glib is built, both remain unanswered at this
stage... So I'm still stuck with no GIMP. 8-)

Regards,

Craig.
-- 
            Craig Dewick. Send email to "cdewick@lios.apana.org.au"
  Point a web browser at 'http://lios.apana.org.au/~cdewick/sun_shack.html' to
    access my archive of Sun information and links to other places. For info 
          about Sun Ripened Kernels, go to "http://www.sunrk.com.au"

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.

On 17 Aug 1999 17:13:20 +1000, Craig Dewick <cdewick@lios.apana.org.au> wrote:
>In <kiyso5koane.fsf@orrery.ocs.mq.edu.au> James.McPherson@mq.edu.au (James C.
>McPherson) writes:
>>I think it's actually due to the fact that the libtool supplied with most gnu
>>software really _hates_ solaris. I'd recommend that you firstly download and
>>install the absolute latest version of libtool (since this is more
>>solaris-friendly), and then go through your configure scripts and change 
>
>># Always use our own libtool.
>>LIBTOOL='$(SHELL) $(top_builddir)/libtool'
>
>>to the following:
>
>># Always use our own libtool.
>>#LIBTOOL='$(SHELL) $(top_builddir)/libtool'
>>LIBTOOL=/usr/local/bin/libtool   
>
>>instead, where /usr/local/bin/libtool is your own locally built version.
>
>>Everything should work just fine then.
>
>Except that it doesn't. I installed libtool-1.3.3 locally, and changed the
>definitions in the configure scripts so they invoke the locally installed
>copy of libtool in /usr/local/bin, however the result is exactly the same:
>
>libtool: link: `/azwan/glib-1.2.3/gmodule.la' is not a valid libtool archive
>*** Error code 1
>
>The problem of why gmodule.la is needed for this step of building gtk, and
>also why it's not created when glib is built, both remain unanswered at this
>stage... So I'm still stuck with no GIMP. 8-)
>
I will through in my two cents worth on this and you can take it for
what it's worth.

I have compiled the above (glib-1.2.3) on both a Solaris 2.4 and
Solaris 2.6 system.  Solaris 2.4 is running on a Sparc 5 and Solaris
2.6 is running on a Sparc 20.  I don't seem to remember having
any such problem.

On both systems, I have gcc version 2.8.1.  I have also not installed
libtool to the best of my knowledge.

If you would like me to try and compile glib-1.2.3 for you, I would
be glad to try.

-- 
Frank Hahn

What good is having someone who can walk on water if you don't follow
in his footsteps?

At 16 Aug, James C. McPherson wrote:

> I think it's actually due to the fact that the libtool supplied with
> most gnu software really _hates_ solaris. I'd recommend that you
> firstly download and install the absolute latest version of libtool
> (since this is more solaris-friendly), and then go through your
> configure scripts and change 

Type libtoolize --force --copy instead...

/Tomas - had no problems with gtk on solaris 2.4, 2.5.1 or 2.6
-- 
Tomas �gren, stric@ing.umu.se, http://www.ing.umu.se/~stric/
|- Student at Computing Science, University of Ume�
`- Sysadmin at {cs,ing,acc}.umu.se