[haiku-bugs] Re: [Haiku] #12532: Incorporation of GCC 5
- From: "bonefish" <trac@xxxxxxxxxxxx>
- Date: Tue, 12 Apr 2016 22:50:07 -0000
#12532: Incorporation of GCC 5
----------------------------+----------------------------
Reporter: korli | Owner: korli
Type: enhancement | Status: new
Priority: normal | Milestone: Unscheduled
Component: Build System | Version: R1/Development
Resolution: | Keywords:
Blocked By: | Blocking:
Has a Patch: 0 | Platform: All
----------------------------+----------------------------
Comment (by bonefish):
Replying to [comment:7 korli]:
OK, though GCC doesn't provide a shared libsupc++ by default, not so
standard set-up in my book.
OK, that seems to have changed since the earlier gcc 4 versions. At least
on Linux a shared libsupc++ was available back then. That no longer seems
to be the case, though.
Our use of libsupc++ is somewhat questionable, for instance, libdevice
links against libbe and libsupc++. libbe links against libstdc++. this
leads to two copies of libsupc++ in memory (the one in libstdc++ and the
one in libsupc++). Or do I miss something?
No, you're right. Consequently the shared libstdc++ would link against the
shared libsupc++ instead of including it, so that there wouldn't be such a
duplication. But I don't think doing it this way (unlike everyone else) is
worth the hassle. I'd just drop the shared libsupc++ and change the Haiku
build system to linking against libstdc++. In case external packages use
the shared libsupc++, a symlink to libstdc++ could be provided temporarily
(only in lib/, though, not develop/lib/).
--
Ticket URL: <
https://dev.haiku-os.org/ticket/12532#comment:8>
Haiku <
https://dev.haiku-os.org>
Haiku - the operating system.
Other related posts: