Re: Problem with ltdl m4 for OS/2

[Ralf Wildenhues]

Hello Paul,

* Paul Smedley wrote on Mon, Apr 06, 2009 at 11:38:36PM CEST:
> Ralf Wildenhues wrote:
>>> 2009/4/5 Paul Smedley <address@hidden>:
>>>> ltdl has problems running on OS/2 - as its detected as using some cygwin
>>>> code:
>>
>>>> cygwin* | mingw* | os2* | pw32*)
>>>>  AC_CHECK_DECLS([cygwin_conv_path], [], [], [[#include <sys/cygwin.h>]])
>>>>  LT_DLLOADERS="$LT_DLLOADERS 
>>>> ${lt_dlopen_dir+$lt_dlopen_dir/}loadlibrary.la"
>>>>  ;;
>>>> esac
>>
>>>> os2* shouldn't be included for the section on cygwin_conv_path
>>>>
>>>> It would be really great if this could be corrected - this seems to have
>>>> been added recently, and causes a lot of build bustage.
>>
>> I don't see how this particular code causes the breakage; if OS/2 has no
>> cygwin_conv_path function, then the respective code should be disabled.
>> Can you post (copy and paste) errors that you are getting?

> What ends up happening is that windows.h gets included when the ltdl  
> code get's built.

Well, what I really meant was: can you post (copy and paste) errors that
you are getting?

It's fine if you describe errors in your own words, but the essential
part is that you show the error exactly.  That makes it easier to
analyze them.

Unfortunately, I know close to nothing about OS/2.  Does it provide a
GetModuleFileName/LoadLibrary API, like Windows does?  Does it have
SetErrorMode, FreeLibrary, GetProcAddress?  If yes, which public header
file declares these functions?

If you would like to try to get things working, you should probably try
to edit the libltdl/loaders/loadlibrary.c file, wrap the
  #include <windows.h>

in `#if defined __WINDOWS__'/`#endif' lines, and add required headers
conditionally under some OS/2 #define.  Then see how far you get, and
post findings.  When you get stuck, pretty please post whatever command
fails, completely, including all of its output.

>> Can you please try out the git master tree of Libtool (or a nightly
>> snapshot) and report all test failures; see the README file for more
>> information on running the test suite.

> OK will do

This is interesting if you manage to get Libtool built completely.

Thanks!
Ralf