After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 132836 - bootstrap: libtool complaints with 1.5; 1.5.2 won't install
bootstrap: libtool complaints with 1.5; 1.5.2 won't install
Status: RESOLVED FIXED
Product: jhbuild
Classification: Infrastructure
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: James Henstridge
Jhbuild QA
: 133228 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2004-01-29 08:36 UTC by Telsa Gwynne
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.3/2.4


Attachments
Patch updating mktemp patch to allow it be applied against libtool-1.5.2 (1.77 KB, patch)
2004-01-29 16:27 UTC, Fernando Herrera
none Details | Review

Description Telsa Gwynne 2004-01-29 08:36:07 UTC
System is Fedora Core 1 with Gnome 2.4. jhbuild is that from 
CVS as of 2004-01-29.

Changes to .jhbuildrc: added my cvs account and altered to 
cflags = '-g -Os'

Ran jhbuild bootstrap. Compared what it found with the
list in the README of what it wants and added stuff until
they corresponded. 

Told it to build. It died on libxml and 
aclocal: configure.in: 60: macro `AM_PROG_LIBTOOL' not found in library

I have libtool-1.5-8 from rpms. README only mentions
"1.5", but re-ran bootstrap and agreed to updating to 
libtool-1.5.2.tar.gz. This fails to build because a patch
(libtool-1.3.5-mktemp.patch) fails.

So I'm at a loss. Do I need to get 1.5.2, or will this 1.5 I
have from rpm suffice? If that will suffice, what am I 
missing wrt the aclocal complaint? I think I have done
everything in the README correctly. Is there something
missing from it? 

If I need 1.5.2, then the bug is "update README to say so"
and I suppose I need to find a libtool maintainer to tell me
why 1.5.2 won't build.
Comment 1 Fernando Herrera 2004-01-29 16:27:13 UTC
Created attachment 23878 [details] [review]
Patch updating mktemp patch to allow it be applied against libtool-1.5.2
Comment 2 Telsa Gwynne 2004-01-29 16:57:26 UTC
This successfully applies. I re-ran "make install" then, then 
"jhbuild bootstrap" and libtool built properly.

And then libxml built fine. Thanks!
Comment 3 Fernando Herrera 2004-01-29 17:02:07 UTC
Due to high priority of having a jhbuild working, I commited the fix,
so closing.
Comment 4 James Henstridge 2004-01-30 05:39:18 UTC
Thanks for checking this in Fernando.

In answer to Telsa's question, the documentation on bootstrapping does
need some additional work.  At the moment, my suggestion is that
people do one of:
  1) get all the bootstrap items (autotools, etc) from their
     distro.  In this case, it isn't necessary to call "jhbuild
     bootstrap"
  2) Install all boostrap items into the build root, ignoring what
     the distro installed.

Currently "jhbuild bootstrap" will often leave you somewhere in
between (1) and (2), occasionally with a broken setup (the common case
is where one of the automakes gets installed under /prefix, and
consequently doesn't see macros installed in /usr/share/aclocal).

The bootstrap process should probably be modified so that it does one
of two things:
   1) verifies that the required tools have been installed with the
      distro.  Error out if they haven't.
or
   2) check if the tools are installed in the buildroot (ignoring
      other versions) and if not, download and install them.
Comment 5 Telsa Gwynne 2004-01-30 08:35:17 UTC
Oh no. I fear I am in your state 1-and-a-half, then. I
have been seeing complaints and whinges about aclocal
and what I should add to the contents of what, but
everything has just kept on building. 

Except that I am stuck now, but I don't think it's
jhbuild's fault. :) 
Comment 6 James Henstridge 2004-02-04 11:58:07 UTC
*** Bug 133228 has been marked as a duplicate of this bug. ***