Summary: | Configure fails to find libpthread with CPPFLAG -H | ||
---|---|---|---|
Product: | cairo | Reporter: | Peter Dyballa <Peter_Dyballa> |
Component: | general | Assignee: | Chris Wilson <chris> |
Status: | RESOLVED MOVED | QA Contact: | cairo-bugs mailing list <cairo-bugs> |
Severity: | normal | ||
Priority: | medium | CC: | freedesktop |
Version: | 1.12.14 | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Mac OS X (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Peter Dyballa
2013-01-12 22:19:59 UTC
This appears to be a general bug in the pthread test. The CAIRO_CHECK_PTHREAD macro uses CAIRO_CC_TRY_LINK_WITH_ENV_SILENT for the actual tests for compileability with various flags. There, "The link step must complete without dnl warnings or errors to stderr." But using various flags that the user could want to use might legitimately trigger unrelated compiler diagnostic output, which incorrectly is treated as a failure/unsupported pthread flag. Reported as a visible downstream bug even without specifying any flags due to the default behavior of an OS X compiler. See: https://sourceforge.net/p/fink/package-submissions/4614/ Yes, this is really painful. We should investigate whether we can replace our custom pthread detection with AX_PTHREAD. -- 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/cairo/cairo/issues/231. |
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.