.lai files
I'm trying to debug the libsasl make install error: libtool: install: /usr/bin/install -c .libs/libsasldb.lai /usr/local/lib/sasl2/libsasldb.la install: .libs/libsasldb.lai: stat: No such file or directory but I can't seem to find any documentation on where/when a .lai is created. (Just a reference in autobook) My guess is that it may have to do with plugins/Makefile.am: libsasldb_la_LIBADD = ../sasldb/libsasldb.la $(SASL_DB_LIB) $(COMPAT_OBJS) libsasldb.la being built in a neighbouring directory. Have you any hints on where to look? Cheers, Patrick ___ http://lists.gnu.org/mailman/listinfo/libtool
Re: .lai files
On Wed, 17 Sep 2008, Patrick Welche wrote: I'm trying to debug the libsasl make install error: libtool: install: /usr/bin/install -c .libs/libsasldb.lai /usr/local/lib/sasl2/libsasldb.la install: .libs/libsasldb.lai: stat: No such file or directory but I can't seem to find any documentation on where/when a .lai is created. (Just a reference in autobook) My guess is that it may have to do with plugins/Makefile.am: libsasldb_la_LIBADD = ../sasldb/libsasldb.la $(SASL_DB_LIB) $(COMPAT_OBJS) libsasldb.la being built in a neighbouring directory. Have you any hints on where to look? Libtool writes many files to a hidden '.libs' directory. Since the .lai file does not exist, perhaps there is an ordering error in your makefile? Automake is a powerful tool, but there are some things it just does not handle completely. One of those things is library build and install order. Bob == Bob Friesenhahn [EMAIL PROTECTED], http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer,http://www.GraphicsMagick.org/ ___ http://lists.gnu.org/mailman/listinfo/libtool
Libtool 2.2.6a
minor rant I notice that libtool-2.2.6a.tar.* unzips into the libtool-2.2.6/ directory (dropping the a from the directory name). This is unexpected. It actually throws off all my auto-install scripts because the version number is now not the same as the directory. Grumble. /minor rant -- Jeff Squyres Cisco Systems ___ http://lists.gnu.org/mailman/listinfo/libtool
Re: .lai files
Hi Patrick, Bob, * Bob Friesenhahn wrote on Wed, Sep 17, 2008 at 08:08:39PM CEST: On Wed, 17 Sep 2008, Patrick Welche wrote: I'm trying to debug the libsasl make install error: libtool: install: /usr/bin/install -c .libs/libsasldb.lai /usr/local/lib/sasl2/libsasldb.la install: .libs/libsasldb.lai: stat: No such file or directory but I can't seem to find any documentation on where/when a .lai is created. Should be created at the time the .la file is created. My guess is that it may have to do with plugins/Makefile.am: libsasldb_la_LIBADD = ../sasldb/libsasldb.la $(SASL_DB_LIB) $(COMPAT_OBJS) libsasldb.la being built in a neighbouring directory. Sounds rather unlikely to me, but what do I know? ;-) Libtool writes many files to a hidden '.libs' directory. Since the .lai file does not exist, perhaps there is an ordering error in your makefile? Automake is a powerful tool, but there are some things it just does not handle completely. One of those things is library build and install order. Certainly you have a point. (Maybe not for much longer, but that's another topic.) However, I don't think an ordering issue would complain about a missing .lai file, those rather have problems finding dependent installed libs. Patrick, it would be really good to have a reproducible example, including all autotools versions used, system this is on, shell. Bonus points for a small example, but a larger one is better than none, too. Thanks, Ralf ___ http://lists.gnu.org/mailman/listinfo/libtool
[sr #106497] Broken download link (2.2.6 instead of 2.2.6a)
URL: http://savannah.gnu.org/support/?106497 Summary: Broken download link (2.2.6 instead of 2.2.6a) Project: GNU Libtool Submitted by: hartwork Submitted on: Thu 18 Sep 2008 12:47:35 AM GMT Category: None Priority: 5 - Normal Severity: 3 - Normal Status: None Privacy: Public Assigned to: None Originator Email: Open/Closed: Open Discussion Lock: Any Operating System: None ___ Details: Broken link [1] on [2]. Please replace 2.2.6 with 2.2.6a. Sebastian [1] http://ftp.gnu.org/gnu/libtool/libtool-2.2.6.tar.gz [2] http://www.gnu.org/software/libtool/ ___ Reply to this item at: http://savannah.gnu.org/support/?106497 ___ Message sent via/by Savannah http://savannah.gnu.org/ ___ http://lists.gnu.org/mailman/listinfo/libtool
[sr #106497] Broken download link (2.2.6 instead of 2.2.6a)
Update of sr #106497 (project libtool): Status:None = Done Assigned to:None = pogma Open/Closed:Open = Closed ___ Follow-up Comment #1: Thank you. Fixed. ___ Reply to this item at: http://savannah.gnu.org/support/?106497 ___ Message sent via/by Savannah http://savannah.gnu.org/ ___ http://lists.gnu.org/mailman/listinfo/libtool
Re: problem when cross compiling with mingw32ce
I'm cross-compiling using the cegcc toolchain and the mingw32ce compiler. I have 2 problems: 1) I use Windows sockets, hence i have to link against libws2 and I pass -lws2. I have the following (usual...) message: *** Warning: linker path does not have real file for library -lws2. *** I have the capability to make that library automatically link in when *** you link to this library. But I can only do this if you have a *** shared version of the library, which you do not appear to have *** because I did check the linker path looking for a file starting *** with libws2 and none of the candidates passed a file format test *** using a file magic. Last file checked: /home/torri/local/opt/mingw32ce/lib/gcc/arm-mingw32ce/4.1.0/../../../../arm-mingw32ce/lib//libws2.a *** The inter-library dependencies that have been dropped here will be *** automatically added whenever a program is linked with this library *** or is declared to -dlopen it. *** Since this library must not contain undefined symbols, *** because either the platform does not support them or *** it was explicitly requested with -no-undefined, *** libtool will only create a static version of it. I pass -no-undefined. The command line is: /bin/sh ../../libtool --tag=CC --mode=link arm-mingw32ce-gcc -g -O2 -no-undefined -Wl,--enable-auto-import -version-info 0:1:0 -L/home/torri/local/wince/lib -L/home/torri/local/opt/cegcc/lib -o libevil.la -rpath /home/torri/local/wince/lib libevil_la-evil.lo libevil_la-evil_fcntl.lo libevil_la-evil_langinfo.lo libevil_la-evil_mman.lo libevil_la-evil_pwd.lo libevil_la-evil_stdlib.lo libevil_la-evil_unistd.lo libevil_la-evil_util.lo -lws2 Does someone know why ? 2) 2nd qestion: I have the following message from libtool (which i do not have with other compilers): libtool: link: Could not determine host path corresponding to libtool: link: '/home/torri/local/wince/lib' libtool: link: Continuing, but uninstalled executables may not work. libtool: link: Could not determine host path corresponding to libtool: link: '/home/torri/local/wince/bin' libtool: link: Continuing, but uninstalled executables may not work. libtool: link: Could not determine host path corresponding to libtool: link: '/home/torri/local/opt/cegcc/lib' libtool: link: Continuing, but uninstalled executables may not work. libtool: link: Could not determine host path corresponding to libtool: link: '/home/torri/local/opt/cegcc/bin' libtool: link: Continuing, but uninstalled executables may not work. I've never seen those message. Again, I would like to know what is happening. No idea where I should look to fix those messages ? thank you Vincent Torri ___ http://lists.gnu.org/mailman/listinfo/libtool
