[prev in list] [next in list] [prev in thread] [next in thread]
List: haiku-bugs
Subject: [haiku-bugs] Re: [Haiku] #10938: Could not open "WebPositive" (Missing symbol: _ZSt14__once_functor)
From: "zooey" <trac () haiku-os ! org>
Date: 2014-06-29 16:02:52
Message-ID: 055.fab80a9b3194ecd0858f49fa14126623 () haiku-os ! org
[Download RAW message or body]
#10938: Could not open "WebPositive" (Missing symbol: _ZSt14__once_functor).
----------------------------+----------------------------
Reporter: taos | Owner: bonefish
Type: bug | Status: new
Priority: high | Milestone: R1/alpha5
Component: Build System | Version: R1/Development
Resolution: | Keywords:
Blocked By: | Blocking:
Has a Patch: 0 | Platform: All
----------------------------+----------------------------
Comment (by zooey):
pulkomandy's guess is right on spot. I have just learned that the hard way
when trying to find out why gcc-4.8.3 is no longer buildable on x86_64
with haikuporter - it consistently fails with an internal compiler error
that complains about an unknown instruction in libcpp/lex.c.
Seeing that Jerome managed to build gcc-4.8.3 on x86_64 (after all, there
is a corresponding package), I suspected that the ICE must be triggered by
some change done after Jerome has built that package. Disabling TLS
support explicitly in the recipe let's gcc build again, and indeed, the
current gcc-package has been built on a haiku revision (hrev47170) that
predates the inclusion of ELF-TLS support (hrev47198).
So, what should we do? Explicitly disable TLS when building gcc for now
(in both the recipe and our cross-build script)?
--
Ticket URL: <https://dev.haiku-os.org/ticket/10938#comment:15>
Haiku <https://dev.haiku-os.org>
Haiku - the operating system.
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic