Re: Support for BeOS in APR-trunk
Ivan Zhakov <[email protected]> Mon, 11 May 2026 15:46:30 +0200
| Newsgroups | gmane.comp.apache.apr.devel |
|---|---|
| Message-ID | <CAPZho0--m5BvKF0XR8692hpGdQx_Mc+Jr7=bss7ChTU4JSMhMg@mail.gmail.com> |
--00000000000004118506518afa28 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Mon, 11 May 2026 at 09:25, Daniel Sahlberg <[email protected]> wrote: > Den m=C3=A5n 11 maj 2026 kl 04:33 skrev Nathan Hartman < > [email protected]>: > > > > On Sun, May 10, 2026 at 10:15=E2=80=AFAM Nathan Hartman < > [email protected]> wrote: > >> > >> On Sun, May 10, 2026 at 8:41=E2=80=AFAM Branko =C4=8Cibej <brane@apach= e.org> wrote: > >>> > >>> On 10. 5. 26 14:11, Ivan Zhakov wrote: > >>> > >>> Hi, > >>> > >>> 1. According to Wikipedia [1] BeOS was released in 1995 and the lates= t > release was in 2000. > >>> > >>> 2. There is Haiku (OpenBeOS) project. Which looks like > reimplementation of BeOS API based on Linux kernel though. I checked Haik= u > package repository [2] and didn't find APR/HTTPD packages. > >>> > >>> 3. APR contains separate code for BeOS (like 19 source code files) > >>> > >>> Given all above I suggest to remove BeOS related source code from > trunk, unless someone comes forward and offers to maintain the BeOS code. > >>> > >>> Partially discussed before: > >>> https://lists.apache.org/thread/r9txh2n1xpx3mh0ckrt8xhzvsqr9s56b > >>> > >>> [1]: https://en.wikipedia.org/wiki/BeOS > >>> [2]: https://depot.haiku-os.org/ > >>> > >>> > >>> > >>> Granted the headers are in a strange place (see attached), but they'r= e > there. I can build Serf and Subversion on Haiku. > >>> > >>> -- Brane > >>> > >> > >> Haiku is an active project that aims to be a spiritual successor of > BeOS. > >> > >> Haiku does not use the Linux kernel [1]. > >> > >> There are APR [2], httpd [3], Serf [4], and Subversion [5] packages fo= r > Haiku. > >> > >> From browsing there, it isn't clear whether these Haiku packages depen= d > on the BeOS support code in APR. It also isn't obvious whom to contact to > ask. I recommend not to remove this code until we can find out more. > >> > >> [1] > >> https://www.haiku-os.org/about/faq/#is-haiku-based-on-linux > >> > >> [2] > https://depot.haiku-os.org/__multipage/pkg/apr/haikuports/haikuports_x86_= 64/1/7/5/-/1/x86_64 > >> > >> [3] > >> > https://depot.haiku-os.org/__multipage/pkg/apache/haikuports/haikuports_x= 86_64/2/4/66/-/1/x86_64 > >> > >> [4] > https://depot.haiku-os.org/__multipage/pkg/serf/haikuports/haikuports_x86= _64/1/3/10/-/1/x86_64 > >> > >> [5] > https://depot.haiku-os.org/__multipage/pkg/subversion/haikuports/haikupor= ts_x86_64/1/14/5/-/2/x86_64 > >> > >> Cheers, > >> Nathan > > > > > > FYI I wrote to the haikuports list to ask whether the APR package for > Haiku depends on these BeOS support files [1]. > > Thanks Nathan for figuring out the list and sending the question. I > see there are a few followups. > > In particular, they created a GitHub issue to track this[2]. > > It seems they were able to build without the BeOS specific files, but > I don't know if there are workarounds for any of the test failures > they had if they built with the BeOS specific code. > > I have installed Haiku on VM and checked BeOS related pre-processor macro= s defined when building APR on Haiku: 1. BEOS macro is not defined. 2. __BEOS__ macro is not defined. 3. BEOS_R5 macro is not defined. 4. HAVE_BONE_VERSION is not defined 5. BEOS_BONE is defined, but it also defined when building on Linux. The configure script identify target system type as "x86_64-unknown-haiku", not as "-beos". So it looks that Haiku doesn't use on BeOS code in APR. --=20 Ivan Zhakov --00000000000004118506518afa28 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div dir=3D"ltr">On Mon, 11 May 2026 at 09:25, Daniel Sahl= berg <<a href=3D"mailto:[email protected]">daniel.l.sahlberg@g= mail.com</a>> wrote:</div><div class=3D"gmail_quote gmail_quote_containe= r"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bord= er-left:1px solid rgb(204,204,204);padding-left:1ex">Den m=C3=A5n 11 maj 20= 26 kl 04:33 skrev Nathan Hartman <<a href=3D"mailto:hartman.nathan@gmail= .com" target=3D"_blank">[email protected]</a>>:<br> ><br> > On Sun, May 10, 2026 at 10:15=E2=80=AFAM Nathan Hartman <<a href=3D= "mailto:[email protected]" target=3D"_blank">[email protected]= m</a>> wrote:<br> >><br> >> On Sun, May 10, 2026 at 8:41=E2=80=AFAM Branko =C4=8Cibej <<a h= ref=3D"mailto:[email protected]" target=3D"_blank">[email protected]</a>> = wrote:<br> >>><br> >>> On 10. 5. 26 14:11, Ivan Zhakov wrote:<br> >>><br> >>> Hi,<br> >>><br> >>> 1. According to Wikipedia [1] BeOS was released in 1995 and th= e latest release was in 2000.<br> >>><br> >>> 2. There is Haiku (OpenBeOS) project. Which looks like reimple= mentation of BeOS API based on Linux kernel though. I checked Haiku package= repository [2] and didn't find APR/HTTPD packages.<br> >>><br> >>> 3. APR contains separate code for BeOS (like 19 source code fi= les)<br> >>><br> >>> Given all above I suggest to remove BeOS related source code f= rom trunk, unless someone comes forward and offers to maintain the BeOS cod= e.<br> >>><br> >>> Partially discussed before:<br> >>> <a href=3D"https://lists.apache.org/thread/r9txh2n1xpx3mh0ckrt= 8xhzvsqr9s56b" rel=3D"noreferrer" target=3D"_blank">https://lists.apache.or= g/thread/r9txh2n1xpx3mh0ckrt8xhzvsqr9s56b</a><br> >>><br> >>> [1]: <a href=3D"https://en.wikipedia.org/wiki/BeOS" rel=3D"nor= eferrer" target=3D"_blank">https://en.wikipedia.org/wiki/BeOS</a><br> >>> [2]: <a href=3D"https://depot.haiku-os.org/" rel=3D"noreferrer= " target=3D"_blank">https://depot.haiku-os.org/</a><br> >>><br> >>><br> >>><br> >>> Granted the headers are in a strange place (see attached), but= they're there. I can build Serf and Subversion on Haiku.<br> >>><br> >>> -- Brane<br> >>><br> >><br> >> Haiku is an active project that aims to be a spiritual successor o= f BeOS.<br> >><br> >> Haiku does not use the Linux kernel [1].<br> >><br> >> There are APR [2], httpd [3], Serf [4], and Subversion [5] package= s for Haiku.<br> >><br> >> From browsing there, it isn't clear whether these Haiku packag= es depend on the BeOS support code in APR. It also isn't obvious whom t= o contact to ask. I recommend not to remove this code until we can find out= more.<br> >><br> >> [1]<br> >> <a href=3D"https://www.haiku-os.org/about/faq/#is-haiku-based-on-l= inux" rel=3D"noreferrer" target=3D"_blank">https://www.haiku-os.org/about/f= aq/#is-haiku-based-on-linux</a><br> >><br> >> [2] <a href=3D"https://depot.haiku-os.org/__multipage/pkg/apr/haik= uports/haikuports_x86_64/1/7/5/-/1/x86_64" rel=3D"noreferrer" target=3D"_bl= ank">https://depot.haiku-os.org/__multipage/pkg/apr/haikuports/haikuports_x= 86_64/1/7/5/-/1/x86_64</a><br> >><br> >> [3]<br> >> <a href=3D"https://depot.haiku-os.org/__multipage/pkg/apache/haiku= ports/haikuports_x86_64/2/4/66/-/1/x86_64" rel=3D"noreferrer" target=3D"_bl= ank">https://depot.haiku-os.org/__multipage/pkg/apache/haikuports/haikuport= s_x86_64/2/4/66/-/1/x86_64</a><br> >><br> >> [4] <a href=3D"https://depot.haiku-os.org/__multipage/pkg/serf/hai= kuports/haikuports_x86_64/1/3/10/-/1/x86_64" rel=3D"noreferrer" target=3D"_= blank">https://depot.haiku-os.org/__multipage/pkg/serf/haikuports/haikuport= s_x86_64/1/3/10/-/1/x86_64</a><br> >><br> >> [5] <a href=3D"https://depot.haiku-os.org/__multipage/pkg/subversi= on/haikuports/haikuports_x86_64/1/14/5/-/2/x86_64" rel=3D"noreferrer" targe= t=3D"_blank">https://depot.haiku-os.org/__multipage/pkg/subversion/haikupor= ts/haikuports_x86_64/1/14/5/-/2/x86_64</a><br> >><br> >> Cheers,<br> >> Nathan<br> ><br> ><br> > FYI I wrote to the haikuports list to ask whether the APR package for = Haiku depends on these BeOS support files [1].<br> <br> Thanks Nathan for figuring out the list and sending the question. I<br> see there are a few followups.<br> <br> In particular, they created a GitHub issue to track this[2].<br> <br> It seems they were able to build without the BeOS specific files, but<br> I don't know if there are workarounds for any of the test failures<br> they had if they built with the BeOS specific code.<br> <br></blockquote>I have installed Haiku on VM and checked BeOS related pre-= processor macros defined when building APR on Haiku:</div><div class=3D"gma= il_quote gmail_quote_container">1. BEOS macro is not defined.</div><div cla= ss=3D"gmail_quote gmail_quote_container">2. __BEOS__ macro is not defined. </div><div class=3D"gmail_quote gmail_quote_container">3. BEOS_R5 macro is = not defined.</div><div class=3D"gmail_quote gmail_quote_container">4. HAVE_= BONE_VERSION is not defined</div><div class=3D"gmail_quote gmail_quote_cont= ainer">5. BEOS_BONE is defined, but it also defined when building on Linux.= </div><div class=3D"gmail_quote gmail_quote_container"></div><div><br></div= ><div>The configure script identify target system type as "x86_64-unkn= own-haiku", not as "-beos".</div><div><br></div><div>So it l= ooks that Haiku doesn't use on BeOS code in APR.</div><div><br></div><s= pan class=3D"gmail_signature_prefix">-- </span><br><div dir=3D"ltr" class= =3D"gmail_signature">Ivan Zhakov</div></div> --00000000000004118506518afa28--