Lars Wirzenius, le Mon 14 Aug 2006 22:18:20 +0300, a écrit : > la, 2006-08-12 kello 21:37 +0200, [EMAIL PROTECTED] > kirjoitti: > > Hi back, > > > > there's a problem during the build, multiple occurrences of: > > "undefined reference to `pthread_mutex_unlock'" [1] > > > > 1. http://paste.debian.net/10702 or log available on demand. > > > > A solution is to: > > -LDFLAGS = > > +LDFLAGS = -lpthread > > > > in xpdf/Makefile, that makes the `make' step succeed. > > > > I'm not sure whether one should conditionally add > > `-lpthread' in `LDFLAGS = @LDFLAGS@' when we've got > > $(DEB_HOST_ARCH) equal to `hurd-i386' or whether > > that's a bug in a macro or something like that. > > > > Besides that, the build runs OK. > > To me, conditionally adding the -lpthread sounds good, but I'm not > particularly knowledgeable about these things.
Mmm, the Hurd should probably provide weak definitions of pthread_mutex_lock/unlock in its glibc, just like Linux does, since it permits to write libraries that can accomodate linking against libpthread at runtime. -lpthread then becomes useless here. Actually, I already raised this issue some time ago, with no answer... > To: [EMAIL PROTECTED] > Subject: glibc's pthread_mutex_* > Date: Tue, 8 Feb 2005 09:03:26 +0100 > User-Agent: Mutt/1.5.6i-nntp > > Hi, > > Is there any reason for hurd's glibc not to include the POSIX 1x thread > stubs ? > I.E. provide some "{}-functions" as fall-back when libpthread is > not linked: at least pthread_mutex_init(), pthread_mutex_lock(), > pthread_mutex_unlock() and pthread_mutex_destroy(). > > Regards, > Samuel Regards, Samuel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]