Summary: | Cairo requires -DREENTRANT (along with -D_POSIX_THREAD_SEMANTICS) to compile on Solaris 10 with pthreads | ||
---|---|---|---|
Product: | cairo | Reporter: | Michael <mjbauer> |
Component: | general | Assignee: | Carl Worth <cworth> |
Status: | RESOLVED FIXED | QA Contact: | cairo-bugs mailing list <cairo-bugs> |
Severity: | normal | ||
Priority: | medium | ||
Version: | 1.8.0 | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: | Define _POSIX_C_SOURCE |
Description
Michael
2008-10-10 14:12:16 UTC
Whats the reason for -D_POSIX_THREAD_SEMANTICS? Also I guess -D_POSIX_C_SOURCE would be a better define for flockfile (plus apparently the feature check should be based on _POSIX_THREAD_SAFE_FUNCTIONS). My understanding is that Solaris, by default on seeing -D_REENTRANT, uses Solaris threads. -D_POSIX_PTHREAD_SEMANTICS tells it to use PThreads instead. Created attachment 19580 [details] [review] Define _POSIX_C_SOURCE Can you try this patch to see if addresses the (build) issue? FYI, I've pushed the #define _POSIX_C_SOURCE patch to 1.8, from which we want to make a 1.8.2 release soon. I'd be grateful if you can either try the attached patch or build from git and verify whether that patch alone is sufficient. Thank you. The patch worked: both Cairo and the test suite built without further modification. I applied the patch rather than build from git. Cheers for confirming that we don't yet need REENTRANT - I'm trying to keep the number of random defines to a minimum ;-) Please send the summary and some examples of the test suite failures to the mailing list - we'll help identify if you have any critical failures. Certainly most developers do not have access to Solaris, so it'll be useful for us to look at typical output on that platform. And hopefully it'll encourage a few more people to report their failures/successes. |
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.