[Top][All Lists]

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

Re: and configure

From: Ellen Bowsher
Subject: Re: and configure
Date: Tue, 9 Sep 2003 13:33:16 +0100

address@hidden wrote:
> Hi,
> I'm swimming in a libiconv protage on QNX and I have a problem with shared
> library namming.
> First, the original configure script in libiconv-1.9.1 doesn't know the
> platform.
> After some discussions with a QNX people, I got the informations to
> all the corresponding files.
> It seems that I have to invoke the followng commands, based on
> #>libtoolize -a -c

You probably wanted -f in addition to the other options.

> #>aclocal-1.7
> #>automake-1.7 -f -c
> #>autoconf
> then
> #>configure
> #>make
> Everything runs fine except that I get libiconv.2.0 instead of
> same for the soname.
> The command in configure is:
>   library_names_spec='${libname}${release}${shared_ext}$versuffix
> ${libname}${release}${shared_ext}$major $libname${shared_ext}'
> After some investigation and discussion with qnx peoples and the libiconv
> developper, I found that libtool.m4 contains the following line:
>>   1085 4:shrext=".so"
> the original (from libiconv-1.9.1, don't which libtool version)
> contains the following line
>    2756         eval shared_ext=\"$shrext\"
> Unfortunately, from libtool-1.4.3 doesn't contain the same eval.
> I define shrext and use shared_ext.
> That means I have a dependancy problem but I don't know what to update. I
> wanted to try libtool-1.5 but it that's a simple ghost!!

I don't understand this last sentence.

> Any idea about my problem??

You have a version mismatch between and libtool.m4.

I suspect that because you did not use the --force option to libtoolize, you
are still using the that shipped with libiconv, but because you
have run aclocal, the contents of a later version of libtool.m4 have been
installed in aclocal.m4, and then copied into configure by autoconf.


reply via email to

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