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

  • From: "bonefish" <trac@xxxxxxxxxxxx>
  • Date: Sun, 06 Nov 2011 22:54:04 -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 bonefish):

 Replying to [comment:6 leavengood]:
 > Replying to [comment:5 bonefish]:
 > > 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.

 Yep, feel to do so.

 > > 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.

 Well, normally the stuff built with the target compiler doesn't need to
 run on the the host platform. If host and target compiler are the same,
 they need to, though. So whichever way you look at it, when you built on
 Haiku with the native compiler, it must work correctly.

 > 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.

 That's why I filed #7824. It should at least possible to actually cross-
 built a new Haiku. Whether it will be possible to use the result to update
 the system in-place is different question.

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

 PM will definitely support system upgrades, if that's what you're
 referring to. We will also improve the whole binutils-gcc-libstdc++
 situation, because eventually libstdc++ will be split off into a separate
 package. It will be possible to update it without updating gcc and vice

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

Other related posts: