[haiku-development] Re: New Haiku architectures

  • From: "Ingo Weinhold" <ingo_weinhold@xxxxxx>
  • To: haiku-development@xxxxxxxxxxxxx
  • Date: Wed, 27 Jun 2012 21:38:30 +0200

scottmc wrote:
> I figured that now with an optional package or two that have PPC
> versions and with the GSoC x86_64 port, that it was time to reopen the
> discussion that was part of trac ticket 2451, that is adding new Haiku
> architectures to uname, config.guess, etc.
> http://dev.haiku-os.org/ticket/2451#comment:14
> What is needed and what should they be?

uname() needs to be adjusted to fill in the platform field correctly, but 
that's part of the Haiku port to that architecture. The "BeBox" and "BeMac" 
nonsense should be replaced with something more fitting, (e.g. "PowerPC" or 
"ppc" (seems to be used for Linux)). For x86-64 it will be "x86_64" etc. For 
x86 we keep "BePC" for sake of compatibility.

> The current version of config.guess only has one entry for Haiku at
> this time, that being:
> i586-pc-haiku

The canonical forms for the other architectures should be 
"<arch>-unknown-haiku" (note that it seems to be "powerpc" here) where the 
"unknown" part can be replaced, if it isn't generic hardware for that 
architecture, but something specialized. I'd generally go with what is used for 
Linux in those cases.

Anyway, both uname() and config.guess become relevant only when Haiku on that 
architecture actually has a working userland. Call me pessimistic, but the only 
architecture for which I see any time soon that is x86_64. OTOH it doesn't harm 
to add entries for the other architecture either.

I don't recall what other autotools architecture OS patches are needed -- 
possibly none at all. Some grepping would help.

Regarding the mandatory optional packages, those must initially be 
cross-compiled for new architectures (until they are self-hosting).

CU, Ingo

Other related posts: