Hi, yeah true, having been burned by Be when working on their OS I wish the OS would go away, but not really.  I'm glad to hear it might have been purchased by 3Com (is that true?) 

 

If the OS doesn't have good TCP/IP stack support such as a lack of getsockopt() it sounds like the OS needs fixed.  I think from what I remember of the little I ever knew of this, to call getsockopt() from some stacks you have to be root (a scary concept to me), so perhaps if that's the case in BeOS your app isn't running as root or doesn't have security privilege?  If you feel up to it you might write (ugly proposal sorry) your own glue to fix the hole in the BeOS networking stack.  I never dealt with this side of BeOS so can't comment on how hard that might be, my interest was mostly in video drivers.  This was back when Be had it's own box, and the code ports related to PowerPC.  (Yeah, some time ago sorry.)

 

Best of luck.

Chet

 

-----Original Message-----
From: Zero One [mailto:[EMAIL PROTECTED]]
Sent:
Tuesday, April 30, 2002 4:59 PM
To: [EMAIL PROTECTED]
Subject: Re: OpenSSL on BeOS^H^H^H^Hnon-Windows & non-Linux OSes

 



Ok, let me amend and repeat this request since there wasn't even so much as a "No! BeOS is stupid! Go away!" response to my original message. (Yes, sometimes a flame is better than utter silence ;) )

The biggest problem that I seem to be running into in getting OpenSSL to compile and generate shared libraries is that the net_server version of BeOS does not apparently have getsockopt() in it's networking libraries. At least not in the standard ones that I have.

So, my question is now how would one get around this lack of functionality on any operating system? The reason this is important is because one of the required files (crypto/bio/b_sock.c) in OpenSSL uses this function, precisely once (line 224). I've tried working around it by supplying the value of errno if there is an error, and I've tried following a 1998 era suggestion on it, though neither method worked.

So, does anyone have suggestions based on lack of a particular function as opposed to OS wonkiness?

Thanks. --- Zero One <[EMAIL PROTECTED]>wrote: > Has anyone out there had any luck getting OpenSSL compiled and > running properly under BeOS R5.0.x, in particular with the > "net_server" rather than "BONE"?If so, please drop me an email > telling me precisely how you managed this feat, and whether you > compiled the shared libraries or not.Thank you. > > > --------------------------------- > Do You Yahoo!? > Yahoo! Games - play chess, backgammon, pool and more

 


Do You Yahoo!?
Yahoo! Health - your guide to health and wellness

Reply via email to