Re: rules on generating dlname

[Edscott Wilson]

Well, figured it out.

I had this in configure.ac:

m4_define([release], [1])

This breaks the definition of dlname in the .la file libtool produces.

2013/11/3 Edscott Wilson <address@hidden>

I've read through the libtool manual and google'd around, but the following has me dumfounded.

When I compile the librfm library (basic functions for Rodent Filemanager, http://xffm.org), I get the

following stuff in .libs:

-- lrwxrwxrwx 1 edscott users     16 nov  3 00:18 librfm1.so.1 -> librfm1.so.1.0.1
-rwxr-xr-x 1 edscott users 261997 nov  3 00:18 librfm1.so.1.0.1
lrwxrwxrwx 1 edscott users     12 nov  3 00:18 librfm.la -> ../librfm.la
-rw-r--r-- 1 edscott users    952 nov  3 00:18 librfm.lai
lrwxrwxrwx 1 edscott users     16 nov  3 00:18 librfm.so -> librfm1.so.1.0.1

But the librfm.la file specifies a weird name:

# The name that we can dlopen(3).
dlname='librfmlibrfm1.so.1.so.1'

This symlink gets generated when I do a make install.  Why does libtool use this weird name?

I guess it means something, but I can't figure it out. Other libraries I create with libtool have regular
a "dlname" (one of the "library_names").

Could anyone please tell me what libtool means when this kind of weird dlname is generated in the .la file?

Any pointer would be greatly appreciated.

------------------------------------------------------------------------------------

Dr. Edscott Wilson Garcia

Applied Mathematics and Computing

Mexican Petroleum Institute

--

------------------------------------------------------------------------------------

Dr. Edscott Wilson Garcia

Applied Mathematics and Computing

Mexican Petroleum Institute