Linked by Thom Holwerda on Wed 29th Aug 2012 14:14 UTC, submitted by fran
Thread beginning with comment 533185
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: How will be 32bit programs supported on it?
by jscipione on Thu 30th Aug 2012 20:58
in reply to "RE: How will be 32bit programs supported on it?"
...let's assume 64bit would be entirely Gcc4
x86_64 is gcc4 only, gcc2 is for x86 only.
...does that mean 3 sets of libraries?
Yes, each application needs to be packaged into 3 binaries, one for x86 gcc2, one for x86 gcc4, and a third for x86_64.
Right now it is difficult enough to maintain separate x86 gcc2 and gcc4 packages, x86_64 will add a 3rd. This is a good opportunity for the package manager and IDEs to make this easier by automatically generating "Fat" binaries that run on all architectures.
However, this is a problem that must not be solved immediately because the official Haiku R1 release will be x86 gcc2h (32-bit). Official x86_64 support will come in R2.
RE[3]: How will be 32bit programs supported on it?
by henderson101 on Thu 30th Aug 2012 22:34
in reply to "RE[2]: How will be 32bit programs supported on it?"




Member since:
2006-05-30
doesn't Haiku already do this for the Hybrid? So, let's assume 64bit would be entirely Gcc4 (because, why wouldn't it?) does that mean 3 sets of libraries? Gcc2.x 32bit, gcc4.x 32bit, gcc4.x 64bit??? This seems quite an excessive amount of binaries! But I'm guessing it would be needed to support all 3 architectures.
Edit: I think my main point here is that Gcc2.x is necessary to support legacy BeOS closed source apps (the original goal of Haiku back when it was called Open BeOS) but gcc4 is required to support some of the newer stuff (hence hybrid) and that addind a new architecture (64bit) will double the required base libraries (if not more of the OS level executables)
Edited 2012-08-30 08:50 UTC