summaryrefslogtreecommitdiff
path: root/open_issues/libpthread_dlopen.mdwn
diff options
context:
space:
mode:
authorThomas Schwinge <thomas@schwinge.name>2011-08-30 12:03:36 +0200
committerThomas Schwinge <thomas@schwinge.name>2011-08-30 12:03:36 +0200
commit016433b123ce4b60eee550dbdb7812ba623d16e7 (patch)
tree5b0c66777ca1dae1ac112d1eee8c05ba2c840d4b /open_issues/libpthread_dlopen.mdwn
parentedd7d582fce7a52565efd3e404bb0419f7e34474 (diff)
Minor tweaks.
Diffstat (limited to 'open_issues/libpthread_dlopen.mdwn')
-rw-r--r--open_issues/libpthread_dlopen.mdwn14
1 files changed, 7 insertions, 7 deletions
diff --git a/open_issues/libpthread_dlopen.mdwn b/open_issues/libpthread_dlopen.mdwn
index 0cd761f2..0d3628ec 100644
--- a/open_issues/libpthread_dlopen.mdwn
+++ b/open_issues/libpthread_dlopen.mdwn
@@ -15,7 +15,7 @@ IRC, OFTC, #debian-hurd, 2011-07-21.
<youpi> there's one known issue with pthreads
<youpi> you can't dlopen() it
-[ if the main application is not already linked against it ]
+... if the main application is not already linked against it.
<youpi> which also means you can't dlopen() a module which depends on it if
the main application hasn't used -lpthread already
@@ -43,12 +43,12 @@ The fix thus being: link the main application with -lpthread.
The same symptom appears in an odd case, for instance:
-buildd@hurd:~$ ldd /usr/bin/openjade
- libthreads.so.0.3 => /lib/libthreads.so.0.3 (0x0103d000)
- libosp.so.5 => /usr/lib/libosp.so.5 (0x01044000)
- libpthread.so.0.3 => /lib/libpthread.so.0.3 (0x01221000)
- libnsl.so.1 => /lib/i386-gnu/libnsl.so.1 (0x01232000)
-...
+ buildd@hurd:~$ ldd /usr/bin/openjade
+ libthreads.so.0.3 => /lib/libthreads.so.0.3 (0x0103d000)
+ libosp.so.5 => /usr/lib/libosp.so.5 (0x01044000)
+ libpthread.so.0.3 => /lib/libpthread.so.0.3 (0x01221000)
+ libnsl.so.1 => /lib/i386-gnu/libnsl.so.1 (0x01232000)
+ [...]
openjade links against *both* libthreads and libpthread. The result is that libc
early-initializes libthreads only, and thus libpthread is not early-initialized,