Summary: | /usr/include/pthread.h:368:11: note: previous declaration of '__libc_thr_self' was here | ||
---|---|---|---|
Product: | XCB | Reporter: | Stephen Fisher <sfisher> |
Component: | Utils | Assignee: | xcb mailing list dummy <xcb> |
Status: | RESOLVED MOVED | QA Contact: | xcb mailing list dummy <xcb> |
Severity: | normal | ||
Priority: | medium | ||
Version: | 1.11 | ||
Hardware: | x86-64 (AMD64) | ||
OS: | NetBSD | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Stephen Fisher
2014-12-09 00:49:33 UTC
As explained in the README, configure intentionally doesn't check libpthread, only the default libraries such as libc, so it can determine if it needs to provide stubs for programs which don't want to link with threads libraries. BTW, libpthread-stubs 0.3 is the current version, not 0.1 - I don't know if that matters for this issue though, or if NetBSD simply never had anyone contribute support for it yet. (In reply to Alan Coopersmith from comment #1) > As explained in the README, configure intentionally doesn't check libpthread, > only the default libraries such as libc, so it can determine if it needs to > provide stubs for programs which don't want to link with threads libraries. Would it make sense then to remove the #include <pthread.h> since it isn't trying to link to libpthread by default? > BTW, libpthread-stubs 0.3 is the current version, not 0.1 - I don't know if > that matters for this issue though, or if NetBSD simply never had anyone > contribute support for it yet. Thanks for catching that. I've updated to libpthread-stubs 0.3 and have the same issue. -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/lib/libxcb-cursor/issues/6. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.