On Mon, May 11, 2026 at 9:46 AM Ivan Zhakov <[email protected]> wrote:
> On Mon, 11 May 2026 at 09:25, Daniel Sahlberg <[email protected]> > wrote: > >> Den mån 11 maj 2026 kl 04:33 skrev Nathan Hartman < >> [email protected]>: >> > >> > On Sun, May 10, 2026 at 10:15 AM Nathan Hartman < >> [email protected]> wrote: >> >> >> >> On Sun, May 10, 2026 at 8:41 AM Branko Čibej <[email protected]> wrote: >> >>> >> >>> On 10. 5. 26 14:11, Ivan Zhakov wrote: >> >>> >> >>> Hi, >> >>> >> >>> 1. According to Wikipedia [1] BeOS was released in 1995 and the >> latest release was in 2000. >> >>> >> >>> 2. There is Haiku (OpenBeOS) project. Which looks like >> reimplementation of BeOS API based on Linux kernel though. I checked Haiku >> 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're 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 >> for Haiku. >> >> >> >> From browsing there, it isn't clear whether these Haiku packages >> depend 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_x86_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/haikuports_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 > macros 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. > > -- > Ivan Zhakov > Looks like it has been established by both the Haiku port maintainers and us, that Haiku isn't using the BeOS support (the 19 source files Ivan mentioned in the original message). I think it's safe to remove them. They have some patches, mentioned in their GitHub Issue [1]: "For this issue, check to see if our patches are still needed to build their current repo main. Review our patch(es) and submit to APR." I took a cursory look at the patches [2]; they seem to affect the build only (config.layout, configure.in), not any actual code. They also have some test suite failures. (These failures appear whether our BeOS files are present or not. This makes sense, because those files are not being used.) Now, they are using APR 1.7.5. Perhaps they should try upgrading to 1.7.6 before attempting to diagnose the failures? I'll suggest that... [1] https://github.com/haikuports/haikuports/issues/14120 [2] https://github.com/haikuports/haikuports/blob/e60b8aa2ec232d5d8b5a0d3f074da4fa1ba8fa95/dev-libs/apr/patches/apr-1.7.5.patchset Cheers, Nathan
