[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

libtool 1.4.2: building modules on Tru64 V4.0F

From: Burkhard Schmidt
Subject: libtool 1.4.2: building modules on Tru64 V4.0F
Date: Fri, 9 Nov 2001 19:28:42 +0100


I'd like to report possibly erroneous behavior of libtool version 1.4.2 when building dynamically loadable modules on Compaq's Tru64 UNIX V4.0F: The generated *.so- and *.a-modules are prefixed with "lib", like shared libraries. This is the wrong behavior for Tru64, i.e., dlopen() can't find these modules except when passing the lib-prefix to it as part of the module name. Let me give a concrete example: The three commands

(1) libtool --mode=compile cc $(CFLAGS) -o object.lo object.c
(2) libtool --mode=link cc $(CFLAGS) -o object.la -rpath /some/path -module -avoid-version $(LDFLAGS) object.lo (3) libtool --mode=install $(INSTALL_COMMAND) object.la /some/path/object.la

install the files named libobject.so, libobject.a instead of object.so, object.a in the directory /some/path. (Additionally, object.la is installed in the same place.)

As far as I can see, the reason for the wrong module names is the setting of the variable need_lib_prefix in the file /usr/local/share/aclocal/libtool.m4. It has the default value "unknown", rather than "no", which would be the correct value for Tru64. I have attached a unified-diff of my modified libtool.m4 to illustrate the corresponding change.

Question: How can I prevent the creation of files with the lib-prefix in their names other than modifying libtool.m4?

Just for completeness: I created libtool with the single configure option "--prefix=/usr/local/libtool/1.4.2".

With kind regards,


Attachment: libtool.diff
Description: application/applefile

Attachment: libtool.diff
Description: application/macbinary

reply via email to

[Prev in Thread] Current Thread [Next in Thread]