[Bug other/39979] [4.4/4.5/4.6 Regression] libsupc++(eh_globals.cc)/stlport TLS incompatibility.

[peterf at silvaco dot com]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39979

Peter Foelsche peterf at silvaco dot com changed:

   What|Removed |Added

 CC||peterf at silvaco dot com

--- Comment #22 from Peter Foelsche peterf at silvaco dot com 2012-04-26 
23:52:02 UTC ---
does this mean, that I need to configure g++ in a certain way in case of I want
to use pthread?

[Bug other/39979] [4.4/4.5/4.6 Regression] libsupc++(eh_globals.cc)/stlport TLS incompatibility.

[pluto at agmk dot net]

--- Comment #18 from pluto at agmk dot net  2010-05-13 09:13 ---
(In reply to comment #17)
 Not a bug, you need to configure libstdc++ and stlport the same if you want
 them to work together.

__thread/pthread in eh_globals.cc is an implemetation detail.
how this could conflicts with pthread-based stlport?


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39979

[Bug other/39979] [4.4/4.5/4.6 Regression] libsupc++(eh_globals.cc)/stlport TLS incompatibility.

[redi at gcc dot gnu dot org]

--- Comment #19 from redi at gcc dot gnu dot org  2010-05-13 10:24 ---
(In reply to comment #15)
 the problematic is eh_globals.o which was merged into libstlport.a.

If stlport imports files which are implementation details, then it depends on
those implementation details. isn't that obvious?

If that's by design, then as Andrew said you need to reconfigure stlport.
If it's not by design, it's an stlport bug.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39979

[Bug other/39979] [4.4/4.5/4.6 Regression] libsupc++(eh_globals.cc)/stlport TLS incompatibility.

[pluto at agmk dot net]

--- Comment #20 from pluto at agmk dot net  2010-05-13 10:46 ---
(In reply to comment #19)
 (In reply to comment #15)
  the problematic is eh_globals.o which was merged into libstlport.a.
 
 If stlport imports files which are implementation details, then it depends on
 those implementation details. isn't that obvious?
 
 If that's by design, then as Andrew said you need to reconfigure stlport.
 If it's not by design, it's an stlport bug.

stlport includes some gcc archives in libstlport.a for simplier linking
of stlport-based applications. users just type '-lstlport' and all is linked :)
i see only references to __cxa_finalize in stlport code but this doesn't
touch eh_globals.cc. i'll check this deeply...


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39979

[Bug other/39979] [4.4/4.5/4.6 Regression] libsupc++(eh_globals.cc)/stlport TLS incompatibility.

[redi at gcc dot gnu dot org]

--- Comment #21 from redi at gcc dot gnu dot org  2010-05-13 11:29 ---
(In reply to comment #20)
 
 stlport includes some gcc archives in libstlport.a for simplier linking

for some definition of simpler :)

Either  don't use static linking or rebuild libstlport.a with the gcc version
you plan to use. This isn't a gcc bug though.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39979

[Bug other/39979] [4.4/4.5/4.6 Regression] libsupc++(eh_globals.cc)/stlport TLS incompatibility.

[pinskia at gcc dot gnu dot org]

--- Comment #17 from pinskia at gcc dot gnu dot org  2010-05-12 20:54 
---
Not a bug, you need to configure libstdc++ and stlport the same if you want
them to work together.


-- 

pinskia at gcc dot gnu dot org changed:

   What|Removed |Added

 Status|WAITING |RESOLVED
 Resolution||INVALID


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39979