Bug 12726

Summary: Make check (of package) fails 2 of 4 tests.
Product: cairo Reporter: Dr Alan J Bartlett <ajb.stxsl>
Component: generalAssignee: Carl Worth <cworth>
Status: RESOLVED FIXED QA Contact: cairo-bugs mailing list <cairo-bugs>
Severity: normal    
Priority: medium CC: ajb.stxsl, chris
Version: 1.4.10   
Hardware: x86 (IA32)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments: Log files from configure & make of cairo 1.4.10

Description Dr Alan J Bartlett 2007-10-07 06:37:44 UTC 
Downloaded cairo-1.4.10.tar.gz from cairographics.org site.
Configured as required for system, generating config.log file.
Made package; "make > LOG.1 2> LOG.err.1"; no errors noted.
Performed "make check > LOG.2 2> LOG.err.2"; errors noted in log file; "2 of 4 tests failed. Please report to http://bugs.freedesktop.org/enter_bug.cgi?product=cairo". This is what I am doing.
I need a working version of the cairo library to be able to compile other packages; can you please clarify the status of the cairo package I have just compiled. The files config.log, LOG.1, LOG.err.1, LOG.2 & LOG.err.2 are available upon request. Thanks.
Comment 1 Dr Alan J Bartlett 2007-10-08 04:22:33 UTC 
Created attachment 11934 [details]
Log files from configure & make of cairo 1.4.10

These are the files mentioned in original report.
Comment 2 Dr Alan J Bartlett 2007-10-15 04:01:58 UTC 
I really need to know: is the Cairo package stable to use (i.e. it's just an internal error of "make check")?
Comment 3 Behdad Esfahbod 2007-10-15 11:25:33 UTC 
It's not an internal make check error, but cairo is stable enough for your needs.  Go ahead and compile other packages.
Comment 4 Chris Wilson 2008-01-11 08:19:46 UTC 
The issue here is that the compiler is too old to support symbol visibility, but make check reports it as an error - i.e. it is a false positive from an overzealous test.

This is fixed by commit 6d3ed95, which skips the symbol visibility tests if it is not supported by the compiler.

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.