Reid Spencer
2004-Oct-13 01:10 UTC
[LLVMdev] RESOLVED: [LLVMbugs] [Bug 451] Libtool does not create libNAME.$(SHLIBEXT) files when building dynamic libs
I'm forwarding this bug resolution because it has a pretty wide impact on LLVM developers. This bug (451) has been resolved (well, works for me anyway). If you have reconfigured your build tree since October 4th, you need to reconfigure again. The bug produced shared objects that don't have a .so extension. Reconfiguring will fix this problem. The notes below show what was needed to be fixed. FOR THOSE RUNNING AutoRegen.sh: For this to work reliabily, you MUST have the following auto* tools in your path: autoconf: 2.59 aclocal: 1.9.2 autoheader: 2.59 automake: 1.9.2 libtool: 1.5.10 Other combinations *might* work, but its unlikely (I've tested nearly all of them). Note that automake isn't needed by AutoRegen.sh UNLESS you're trying out the --with-automake flag (on AutoRegen.sh). However, you still MUST install automake 1.9.2 even if you're not using --with-automake because that is how you get aclocal 1.9.2 which is needed by autoconf. Reid. -------- Original Message -------- Subject: [LLVMbugs] [Bug 451] Libtool does not create libNAME.$(SHLIBEXT) files when building dynamic libs Date: Tue, 12 Oct 2004 19:58:23 -0500 From: bugzilla-daemon at cs.uiuc.edu To: llvmbugs at cs.uiuc.edu http://llvm.cs.uiuc.edu/bugs/show_bug.cgi?id=451 rspencer at x10sys.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- Additional Comments From rspencer at x10sys.com 2004-10-12 19:58 ------- The difficulty I had turned out to be the name of "mklib" instead of "libtool". The Makefiles use "mklib" but I was constantly regenerating libtool under various circumstances. The real problem was our version of ltmain.sh which didn't match our version of libtool.m4. Both these files have been committed as well as changes to the AutoRegen.sh script. Commits are here: http://mail.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20041011/019191.html http://mail.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20041011/019192.html http://mail.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20041011/019193.html Bug resolved. NOTES FOR FUTURE: When upgrading the version of libtool, you must do the following: 1. configure/build/install libtool with --prefix=<PFX> 2. Copy <PFX>/share/aclocal/libtool.m4 to llvm/autoconf/m4/libtool.m4 3. Copy <PFX>/share/libtool/ltmain.sh to llvm/autoconf/ltmain.sh 4. Adjust the llvm/autoconf/m4/libtool.m4 file to ensure that the variable default_ofile is set to "mklib" instead of "libtool" 5. Possibly adjust llvm/autoconf/m4/libtool.m4 to get rid of autoconf warnings related to obsolete autconf features (e.g. AC_TRY_LINK) ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. _______________________________________________ LLVMbugs mailing list LLVMbugs at cs.uiuc.edu http://mail.cs.uiuc.edu/mailman/listinfo/llvmbugs
Apparently Analagous Threads
- [LLVMdev] Fwd: [LLVMbugs] [Bug 1971] New: EQUIVALENCE not supported in llvm-gfortran
- [LLVMdev] LLVMbugs list suggestion
- [LLVMdev] Re: IMPORTANT: autoconf changes
- [LLVMdev] ToolRunner.cpp:396: error: `SHLIBEXT' undeclared (first use this function)
- [LLVMdev] ToolRunner.cpp:396: error: `SHLIBEXT' undeclared (firstuse this function)