[haiku-bugs] Re: [Haiku] #8093: Haiku build system using system libstdc++.so on Haiku
- From: "bonefish" <trac@xxxxxxxxxxxx>
- Date: Sun, 06 Nov 2011 18:11:48 -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:4 leavengood]:
> I followed the method described in the build tools document just like
siarzhuk did here: http://dev.haiku-os.org/ticket/7792#comment:22
>
> In my case there was a libstdc++.so on the system, it was just the 4.4.4
version.
>
> I don't understand all the problems you had in #7824, when the method
described in the build tools document works so well, excluding this aspect
of it.
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).
Anyway, in this case the problem was actually that you just didn't install
the new native gcc correctly. 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.
--
Ticket URL: <http://dev.haiku-os.org/ticket/8093#comment:5>
Haiku <http://dev.haiku-os.org>
Haiku - the operating system.
Other related posts:
