Linking OSLib Support

[John Tytgat]

In message <9EzGpBAJvGR6EweS at mk-net.demon.co.uk>
          Tony van der Hoff <OSLib at mk-net.demon.co.uk> wrote:

> On Fri, 22 Dec 2000, at 12:57:57, Dr. Simon J. Melhuish
> <simon at melhuish.net> wrote on the subject "Linking OSLib Support":
> 
> >Hello.
> >
> >I'm just trying out OSLib Support, and I can't get my program to link.
> >Maybe you can guess what I'm doing wrong:
> >
> >Drlink AOF Linker  Version 0.33  10/01/98
> >Error: The following symbols could not be found:
> >    '__SIG_ERR' referenced in '<Make$Dir>.X.obj.X'
> >Drlink: Link failed with 1 error
> >
> >It seems it's something in OSLibSupport that's looking for that. 
> >
> >I'm using gcc (perhaps that's not a good idea) and unixlib.
> >
> 
> I've just come across that problem myself in the last week. It turns out
> that __SIG_ERR (and others) is not defined in UnixLib. The OSLibSupport
> library was built using the CLib definitions.
> 
> A second problem is the X module (which requires these signals) is
> called from the Event module in OSLibsupport, so you can't get round the
> first problem by avoiding X. It also breaks GNU C++
> 
> If you use CLib instead of Unixlib, the problem goes away. However, 
> I have here an experimental OSLibSupport, which conditionally #defines
> the signals, and removes the dependence of Event on X. I'm still testing
> it, and it is still subject to change, but it is available for download
> from HTTP://www.mk-net.demon.co.uk/oslib/620/beta/oslibsupport.zip

The OSLibSupport binary can only be used by either CLib or either by
UnixLib depending how it was compiled.  UnixLib and CLib and not
binary compatible.  If you want to use UnixLib with OSLibSupport, you
have to recompile OSLibSupport library with the UnixLib headers.

John.
-- 
John Tytgat, in his comfy chair at home                                 BASS
John.Tytgat at aaug.net                             ARM powered, RISC OS driven