[openbeos] Re: joe - haiku ports

  • From: Nick <tonestone57@xxxxxxxxxxx>
  • To: <openbeos@xxxxxxxxxxxxx>
  • Date: Tue, 19 Aug 2008 14:37:10 -0600

>> Exactly! Haiku uses the name of the networking library to be able to 
>> provide R5 and BONE compatibility.
>> If you compile with Haiku headers, but link against libnet.so, things 
>> just won't work.
> In my opinion symlink libnetwork.so -> libnet.so
> in /boot/develop/lib/x86 will work correctly. Even if binary is linked
> using -lnet, it will be linked against libnetwork.so. You may check it
> with "readelf -d my_binary" command.
> -- 
> Grzegorz Dąbrowski

Thanks Grzegorz.  That is exactly what I wanted to say.

If you create the symlinks in /boot/develop/lib/x86

for libnet, libsocket, libbind to libnetwork ( libnetwork found in 
/boot/beos/system/lib )

then a program that uses one of those libs will get redirected to libnetwork & 
use that library instead.  I quickly tested with a program that uses libsocket 
and noticed that configure found libsocket ( which was really libnetwork ) when 
I did the symlink.  Without the symlink, configure could not find ( or use ) 

The method I mention above should work.  Just wanted to mention this alternate 

The advantage of doing it this way is that anyone can port stuff over really 
quick without doing any code changes to the source.

ie: configure, make, make check, make install & you are done.

I *believe* the bad might be that any programs done this way would be looking 
for libsocket, libnet, libbind at runtime so the symlinks in 
/boot/beos/system/lib would have to stay around too?


Other related posts: