[openbeos] Apache 2.0 update
- From: Nik Derewianka <nick@xxxxxxxxxxxxxx>
- To: openbeos@xxxxxxxxxxxxx
- Date: Fri, 28 Jun 2002 18:14:02 +1000
First - thanks to Peter moore.
The DBEOS flag helped it compile, just FYI, you still have to explicitly
state a prefix as the default will not work with just the DBEOS flags.
Secondly - its still broken ;) Browsers can connect, they dont timeout,
and as soon as the server is stopped, the page is rendered into the
browser windows - looks like something isnt being sent at the end to let
them know that the page download is complete. This was with R5
netserver, installing BONE just completely hosed my BeOS setup. None of
this is surprising or worrying.
Quick question: Should we still ask project developers if they can make
their code work with BeOS R5 or should we hold off till there is
something more OBOS specific. I know that binary and source
compatibility is aimed for, but this article
http://open-beos.sourceforge.net/nsl.php?15 shows that a different
network stack is in place from BeOS R5. If i do bug-hunt and try and
get devs to fix things like apache for R5, will they then have to turn
around and reimplement parts of it once OBOS appears ?? (ie am i
wasting their time ?)
Regards,
Nik
- Follow-Ups:
- [openbeos] Re: Apache 2.0 update
- From: François Revol
- [openbeos] Re: Apache 2.0 update
- From: David Reid
- References:
- [openbeos] Re: Name suggestion
- From: Elver Loho
Other related posts:
- » [openbeos] Apache 2.0 update
- » [openbeos] Re: Apache 2.0 update
- » [openbeos] Re: Apache 2.0 update
- [openbeos] Re: Apache 2.0 update
- From: François Revol
- [openbeos] Re: Apache 2.0 update
- From: David Reid
- [openbeos] Re: Name suggestion
- From: Elver Loho