FreeLists / openbeosnetteam / [openbeosnetteam] Re: libnet fix

["Daniel Reinhold" <danielr@xxxxxxxxxxxxx>]

<emerging from lurk mode>

guys, at the risk of suggesting something useful, have you considered 
using a different name than 'libnet.so' for your target lib? I had this 
conversation with David Reid over a year ago and made the same 
suggestion, but he didn't feel like it was a big issue. But from my 
point of view, trying to actively develop a lib with the SAME NAME and 
the EXACT SAME SET OF EXPORTED SYMBOLS as a standard existing lib (and 
being loaded from the same set of standard search paths) is just asking 
for brain frying troubles.

Why not use 'libobosnet.so'? Or something distinctive. You can *always*
 change it to the standard name later, once the thing has matured, and 
test against that. In the mean time, sanity is preserved. Is this 
absolutely necessary? No. But isn't it worth keeping things straight 
and not spending hours (days) tracking down non-existent problems 
because of linking against the wrong lib?

Just a kooky suggestion.

<slinking back under his rock>


>Strange. 
>
>The symbol is in the R5 libnet.so. This is getting fishy. Ingo, is 
there
>perhaps something wrong with the link rule?
>
>Niels Sascha Reedijk
>
>
>
>