[haiku-development] Re: Updates relating to build-o-matic, haiku-files.org

  • From: "Michael Lotz" <mmlr@xxxxxxxx>
  • To: haiku-development@xxxxxxxxxxxxx
  • Date: Tue, 17 May 2011 20:52:34 +0200

> On Tue, May 17, 2011 at 11:37 AM, Michael Lotz <mmlr@xxxxxxxx> wrote:
> > On a hybrid build however there are two sets of libraries, gcc2 and
> > gcc4 ones. That means when a gcc4 app is loaded, it will be loaded 
> > with
> > gcc4 libs, resulting in a pure gcc4 environment (and the other way
> > around), hence there is no compatibility problem.
> Ok. I guess I remember this being a bigger problem when it was last 
> discussed.
> I also seem to recall there was some question about compiling a gcc4
> app (webpositive, for example) against gcc2-compiled versions of
> libcurl and openssl - did that also get resolved then?

That's the same problem of course. To ensure compatibility such a gcc4 
WebPositive needs to be linked to gcc4 libraries only, including curl, 
openssl, etc. So a hybrid build should bring such libraries with it. I 
don't think it currently does, IIRC it brings along only the optional 
packages for the base gcc version. So this is probably still 

Basically one should think of these sets (gcc2 vs. gcc4 binaries, 
libraries) as different (and incompatibile) platforms. Like in the 64 
bit case, where 64 bit binaries will work only with 64 bit libraries. 
That it kind of works is more or less by chance, because we use the 
same binary format and, since there is no name mangling in C, the 
symbols happen to be named the same for both.


Other related posts: