[haiku-bugs] Re: [Haiku] #8093: Haiku build system using system libstdc++.so on Haiku

  • From: "leavengood" <trac@xxxxxxxxxxxx>
  • Date: Sun, 06 Nov 2011 20:21:01 -0000

#8093: Haiku build system using system libstdc++.so on Haiku
----------------------------+----------------------------
   Reporter:  leavengood    |      Owner:  bonefish
       Type:  bug           |     Status:  closed
   Priority:  normal        |  Milestone:  R1
  Component:  Build System  |    Version:  R1/Development
 Resolution:  duplicate     |   Keywords:  libstdc++
 Blocked By:                |   Blocking:
Has a Patch:  0             |   Platform:  x86
----------------------------+----------------------------

Comment (by leavengood):

 Replying to [comment:5 bonefish]:
 >
 > The build system strictly separates host and target platform (which is
 why cross-compiling works at all). A compiler is needed for both
 platforms. In case of Haiku as the host platform the build system, as a
 convenience hack, allows to use the host compiler as the target compiler.
 This works fine (though I wouldn't propose it as a method to build
 official images) as long as the target doesn't change in a way that also
 requires compiler changes which aren't compatible with the host system
 (the multi-byte character related changes Oliver has worked on during the
 BeGeistert coding sprint might be such an example).

 Yeah, I get all that. I did cross compiling of Haiku and even WebKit for a
 long time.

 > Anyway, in this case the problem was actually that you just didn't
 install the new native gcc correctly.

 I followed the instructions in buildtools/INSTALL-gcc4-from-source-Haiku
 exactly, if those don't produce a correct installation then they should be
 adjusted or removed.

 > The STL headers and the installed runtime libsupc++ and libstdc++ need
 to match. Otherwise code compiled for the host system might not run on it.

 I'm OK with programs I compile with the new GCC not necessarily being able
 to run on the host system (at least not without putting some libraries in
 a lib subdirectory for whatever I'm trying to run.) This happens a lot
 with Haiku anyhow, when the kernel, libroot or libbe (or other system
 libraries) change a lot. But if I change the compiler things should build
 at least.

 Of course things like a major compiler change should not happen too often.
 But it should be possible to upgrade that from within an existing Haiku,
 without needing another system or completely reinstalling Haiku.

 But maybe this is something that can wait for now. Maybe package
 management will help, I don't know.

-- 
Ticket URL: <http://dev.haiku-os.org/ticket/8093#comment:6>
Haiku <http://dev.haiku-os.org>
Haiku - the operating system.

Other related posts: