Obviously, I can't invest the time to bugshoot all these applications that won't compile, about which I have been emailed by many people in this list during the past 2 hours.
I can add this information, however. I achieved this success with the newer automake and autoconf, $ rpm -q automake automake-1.5-1pj [pauljohn@valinux fs]$ rpm -q autoconf autoconf-2.52-1pj which are also in my software directory. I did not try to rebuild an SRPM file with this libtool, instead I started from a source tree and did the automake/autoconf ritual to create the tarball, and built the RPM from there. It easily could be true that tarballs or SRPMS that were built with old versions of libtool and automake/autoconf do not rebuild with the current libtool. Maybe some libtool maintainers will enter this thread and tell us their expectations. Other than to say "this worked in the case I tested" I am not making any claims about the setup. It seems to me that if you want to rebuild an RPM from an SRPM that was compiled with the old libtool, your easiest path is to stick to the old libtool. pj Martin Norbäck wrote: > tis 2001-11-27 klockan 17.38 skrev Paul E Johnson: > >>This libtool issue is a known and fixed problem in libtool cvs. I built >>rpms of that snapshot of libtool and I've tested it and it does work. >>If you want to try the RPMS, I stashed them in here >>http://lark.cc.ukans.edu/~pauljohn/software >> > > I tried rebuilding the ogle RPM with your new version of libtool > (libtool-20011121-1pj), and got the errors shown in the attached file. > > There are still things like > > libtool: install: warning: `../ogle/libmsgevents.la' has not been > installed in `/usr/lib/ogle' > > Regards, > > Martin > -- Paul E. Johnson email: [EMAIL PROTECTED] Dept. of Political Science http://lark.cc.ukans.edu/~pauljohn University of Kansas Office: (785) 864-9086 Lawrence, Kansas 66045 FAX: (785) 864-5700 _______________________________________________ Libtool mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/libtool
