GNOME Bugzilla – Bug 130815
compile error with 0.9.4
Last modified: 2004-12-22 21:47:04 UTC
This is the same bug as bug 129629 but for some reason I don't have the option to re-open it. I disagree about it being a problem with libtool. It might be a problem with the version of libtool that gok includes, but every other desktop component (the 2.5.2 set) compiles fine without SED being defined. I tried to find a difference between gok and other components and all I can tell is that the version of libtool packaged with it must be broken in some way. Is it possible that an old version of libtool is being included with gok?
dtb@otter:~/code/gok> ./libtool --version ltmain.sh (GNU libtool) 1.5 (1.1220.2.1 2003/04/14 22:48:00) Copyright (C) 2003 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. dtb@otter:~/code/gok>
matt - I've seen this with other GNOME components as well. Perhaps the 0.9.4 tarball includes a b0rked libtool - libtool isn't in CVS so it's not part of GOK sources _per se_. there are other reports of build issues with 0.9.4, due to a packaging problem in make dist. Unfortunately I haven't been able to diagnose the problem, which seem to be on the dist build machine (my machine!), and it, err, "works for me".
I looked for other instances of this problem in gnome bugzilla. I found two different instances, bug 112348 and bug 104895. I'm not even close to a libtool/autoconf/automake expert but maybe it will help
Bill are you taking this? I've closed the related bug 130807 I don't feel qualified to follow up on this general libtool issue.
closing as dup of 112348 (though it's not strictly the same, being a different package). I think the libtool.m4 used in 0.9.4 was faulty. If this problem reappears with a GOK tarball post-0.9.10, please re-open this bug and I'll try (again) to fix. *** This bug has been marked as a duplicate of 112348 ***
This is not going to be fixed if I do something about #112348. The latter bug concerns building from CVS (i.e. running autogen.sh and hence installing the system libtool when libtoolize is run). This bug is about building from tarballs, which uses the libtool scripts that are shipped with the tarballs. There is a difference. The circumstances in this bug can only be fixed by using non-broken libtool scripts on the machine used the make the tarball. I'm not going to un-duplicate things (leaving that up to somebody involved with this bug), but just letting everybody know that somebody may have misunderstood something here.
Malcolm; I thought your fix for #112348 would fix this issue long-term, i.e. subsequent tarballs delivered from machines where 112348 was fixed wouldn't have broken libtools, and thus the tarballs would be OK.