[Mono-bugs] [Bug 54694][Nor] New - runtime compilation failure (__tls_get_addr) [HELPWANTED]

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Sat, 21 Feb 2004 09:56:06 -0500 (EST)

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by vargaz@freemail.hu.


--- shadow/54694	2004-02-21 09:56:06.000000000 -0500
+++ shadow/54694.tmp.1781	2004-02-21 09:56:06.000000000 -0500
@@ -0,0 +1,47 @@
+Bug#: 54694
+Product: Mono/Runtime
+Version: unspecified
+OS: GNU/Linux [Other]
+OS Details: 
+Status: NEW   
+Priority: Normal
+Component: misc
+AssignedTo: mono-bugs@ximian.com                            
+ReportedBy: vargaz@freemail.hu               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+Summary: runtime compilation failure (__tls_get_addr) [HELPWANTED]
+Some users reported compilation failures like this:
+/bin/sh ../../libtool --mode=link gcc  -g -O2 -fno-strict-aliasing -g
+-Wall -Wunused -Wmissing-prototypes -Wmissing-declarations
+-Wstrict-prototypes  -Wmissing-prototypes -Wnested-externs
+-Wpointer-arith -Wno-cast-qual -Wcast-align -Wwrite-strings  -o mono
+-export-dynamic main.o libmono.la                    -pthread
+-lgthread-2.0 -lglib-2.0                       -Wl,--export-dynamic
+-lgmodule-2.0 -ldl -lglib-2.0   -lm               -lpthread -lm
+-L/usr/lib -licui18n -licuuc -licudata -lpthread -lm -lnsl -lpthread -lm
+gcc -g -O2 -fno-strict-aliasing -g -Wall -Wunused -Wmissing-prototypes
+-Wmissing-declarations -Wstrict-prototypes -Wmissing-prototypes
+-Wnested-externs -Wpointer-arith -Wno-cast-qual -Wcast-align
+-Wwrite-strings -o .libs/mono main.o -Wl,--export-dynamic
+-Wl,--export-dynamic  ./.libs/libmono.so -L/usr/lib -pthread
+/usr/lib/libgthread-2.0.so /usr/lib/libgmodule-2.0.so -ldl
+/usr/lib/libglib-2.0.so -licui18n -licuuc -licudata -lnsl -lpthread -lm
+-Wl,--rpath -Wl,/opt/mono//lib
+./.libs/libmono.so: undefined reference to `___tls_get_addr'
+This seems to be triggered by the usage of the __thread keyword in
+runtime code. A workaround is to pass the --with-nptl=no option to 
+Could somebody how encounters this problem produce a simple testcase ?
+We could use the testcase to check for this problem in the configure