Bug 21882 - make test fails on OS X because fenv.h not included
Summary: make test fails on OS X because fenv.h not included
Status: RESOLVED FIXED
Alias: None
Product: cairo
Classification: Unclassified
Component: general (show other bugs)
Version: 1.9.1
Hardware: x86 (IA32) Mac OS X (All)
: medium normal
Assignee: Carl Worth
QA Contact: cairo-bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-22 13:49 UTC by Andrew Lavin
Modified: 2009-06-03 01:20 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
additionally includes fenv.h if HAVE_FECLEAREXCEPT is defined (641 bytes, patch)
2009-05-22 13:49 UTC, Andrew Lavin
Details | Splinter Review

Description Andrew Lavin 2009-05-22 13:49:46 UTC
Created attachment 26129 [details] [review]
additionally includes fenv.h if HAVE_FECLEAREXCEPT is defined

Macintosh-5:cairo aj$ make test
Making all in src
Making all in doc
Making all in public
Making all in util
Making all in .
Making all in cairo-script
Making all in examples
Making all in boilerplate
Making all in test
Making all in pdiff
Making all in .
Making all in perf
Making check in pdiff
==================
All 0 tests passed
==================
Making check in .
Making all in pdiff
Making all in .
  CC    invalid-matrix.o
invalid-matrix.c: In function ‘draw’:
invalid-matrix.c:367: error: implicit declaration of function ‘feclearexcept’
invalid-matrix.c:367: warning: nested extern declaration of ‘feclearexcept’
invalid-matrix.c:367: error: ‘FE_INVALID’ undeclared (first use in this function)
invalid-matrix.c:367: error: (Each undeclared identifier is reported only once
invalid-matrix.c:367: error: for each function it appears in.)
make[5]: *** [invalid-matrix.o] Error 1
make[4]: *** [check-am] Error 2
make[3]: *** [check-recursive] Error 1
make[2]: *** [check] Error 2
Making html in pdiff
Making html in .
Creating index.html
Macintosh-5:cairo aj$
Comment 1 Chris Wilson 2009-06-03 01:20:16 UTC
Pushed, thanks.


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.