First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 77876
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Mark Loeser <halcy0n@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: golloza@web.de
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
pthread-patch.diff Quick&Dirty solution patch golloza@web.de 2005-01-13 12:08 0000 292 bytes Details | Diff
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 77876 depends on: Show dependency tree
Bug 77876 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2005-01-13 12:04 0000 
I emerged xerces-c-2.6.0, linked something (Half-Life 2 Linux SDK if that
matters) against libxerces-c.so and got these errors:
/usr/lib/libxerces-c.so: undefined reference to `pthread_mutexattr_destroy'
/usr/lib/libxerces-c.so: undefined reference to `pthread_mutexattr_settype'
/usr/lib/libxerces-c.so: undefined reference to `pthread_mutexattr_init'

I prepended `LDFLAGS="${LDFLAGS} -lpthread"` to the econf line, now it gets
linked against libpthread.so and works for me.

But I don't know whether or not this is the right solution (does it break with
nptl/nptlonly?).

Shouldn't the ebuild better use runConfigure instead econf?
http://xml.apache.org/xerces-c/build-winunix.html#UNIX

------- Comment #1 From golloza@web.de 2005-01-13 12:08:35 0000 ------- 
Created an attachment (id=48414) [edit]
Quick&Dirty solution

------- Comment #2 From golloza@web.de 2005-03-22 09:33:46 0000 ------- 
Any comments, John?

------- Comment #3 From Thiago 2005-04-17 09:24:50 0000 ------- 
Christoph, I had the sabe problem here trying to compile HL2 SDK and your
solution worked fine, thanks.

The LDFLAGS variable probably is one of the "strange environment variables you
need to use..." mentioned at the build structions of xerces-c. I hope that this
is the only problem caused by not using the provided runConfigure script.

------- Comment #4 From Mark Loeser 2005-07-07 20:31:12 0000 ------- 
Taking over maintainership of this package.

------- Comment #5 From Mark Loeser 2005-07-07 20:36:13 0000 ------- 
I switched the ebuild to use runConfigure instead.  The patch is not needed. 
Thanks for the report.  Try out xerces-c-2.6.0-r1.
First Last Prev Next    No search results available      Search page      Enter new bug