Bugzilla Bug 66377

well, summary says it all. Just check with the following simple test program:

#include <ical.h>

int main(void)
{
	struct icaltimetype x;
	icaltime_compare(x, x);
}

`gcc icaltest.c -lical` blows up with:
/usr/lib/gcc/i686-pc-linux-gnu/3.4.2/../../../libical.so: undefined reference to `pthread_getspecific'
/usr/lib/gcc/i686-pc-linux-gnu/3.4.2/../../../libical.so: undefined reference to `pthread_once'
/usr/lib/gcc/i686-pc-linux-gnu/3.4.2/../../../libical.so: undefined reference to `pthread_key_create'
/usr/lib/gcc/i686-pc-linux-gnu/3.4.2/../../../libical.so: undefined reference to `pthread_setspecific'
collect2: ld returned 1 exit status

It doesn't happen when I build libical with LDFLAGS=-lpthread

OK, fix is in Portage. Thank you for the submission!

As of 0.27 the bug re-emerged:

ld /usr/lib/libical.so
ld: warning: cannot find entry symbol _start; not setting start address
/usr/lib/libical.so: undefined reference to `pthread_key_create'
/usr/lib/libical.so: undefined reference to `pthread_once'
/usr/lib/libical.so: undefined reference to `pthread_getspecific'
/usr/lib/libical.so: undefined reference to `pthread_setspecific'

Reopening old bug.

*** Bug 239227 has been marked as a duplicate of this bug. ***

I committed version 0.33-r1 with the same fixes as in version 0.26.7.
Could you test if the fix is still working for you?

(In reply to comment #5)
> I committed version 0.33-r1 with the same fixes as in version 0.26.7.
> Could you test if the fix is still working for you?
> 

Version 0.33-r1 is OK but 0.27 is stable in portage and that version still has
the bug.

(In reply to comment #6)
I know that: I wanted the fix to be tested before spreading it to all
versions...

All the ebuilds in Portage have been fixed.
Thanks for the heads up!