libtool-patches
[Top][All Lists]
Advanced

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

Re: [PATCH] ltdl: set libltdl_cv_need_uscore to yes on OS/2


From: Gary V. Vaughan
Subject: Re: [PATCH] ltdl: set libltdl_cv_need_uscore to yes on OS/2
Date: Thu, 27 Nov 2014 17:23:34 +0000

Hi,

> On Nov 27, 2014, at 4:53 AM, KO Myung-Hun <address@hidden> wrote:
> Gary V. Vaughan wrote:
>> 
>>> On 27 Nov 2014, at 02:47, KO Myung-Hun <address@hidden> wrote:
>>> I agree.
>>> 
>>> Gary V. Vaughan wrote:
>>>> I pushed the core of a new macro that does exactly that to M4 master just
>>>> now.
>>>> 
>>>> Would you let me know whether this works correctly on OS2 for you please?
>>> 
>>> Of course. Unfortunately, however, it does not work. dlopen() in
>>> configure fails due to 'file not found'.
>> 
>> Thanks for checking.  Can you tell me why it fails (module is not compiled 
>> correctly;
>> path argument to dlopen() is wrong), and maybe suggest what would fix it, 
>> please?
>> 
> 
> I've look into this problem. Module is not built. To build it, some
> additional variables are required. They are soname, libname,
> output_objdir. And archive_cmds on OS/2 consists of multi lines
> separated by ~. So when using it, quotation is needed. And to eval it
> the function such as func_execute_cmds is needed. In addition, make sure
> .libs exist before building a module.
> 
> Finally, please remember that OS/2 does not support DLLs whose base name
> is longer than 8 characters.

Thanks for the swift and helpful feedback.  I pushed some new changes that 
should
address all of those issues.  Please let me know if anything is still wrong, and
in what way it is broken for you if so -- otherwise, I'll port this code into a
new libtool macro and make the next libtool release for m4 master to depend on.

I know I have some other issues you reported to work out in M4, but I'd like to
clear this one up first so I can make the promised libtool release asap.

Many thanks for your help!

Cheers,
-- 
Gary V. Vaughan (gary AT gnu DOT org)


reply via email to

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