Bug 690369 - Cannot Make Jasper as Part of GS 8.64 Required by Artifex
Summary: Cannot Make Jasper as Part of GS 8.64 Required by Artifex
Status: RESOLVED DUPLICATE of bug 688184
Alias: None
Product: JasPer
Classification: Unclassified
Component: Build Process (show other bugs)
Version: 1.701.0
Hardware: HP HP-UX
: P4 major
Assignee: Ralph Giles
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-01 08:52 UTC by Dante Bell
Modified: 2010-05-02 02:36 UTC (History)
0 users

See Also:
Customer:
Word Size: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dante Bell 2009-04-01 08:52:20 UTC
configure of gs-8.64 runs fine, but make returns the following:

jasper/src/libjasper/include/jasper/jas_types.h:151: error: conflicting types 
for 'int_fast8_t'
/usr/include/sys/_inttypes.h:133: error: previous declaration of 'int_fast8_t' 
was here
jasper/src/libjasper/include/jasper/jas_types.h:157: error: conflicting types 
for 'uint_fast8_t'
/usr/include/sys/_inttypes.h:136: error: previous declaration 
of 'uint_fast8_t' was here
jasper/src/libjasper/include/jasper/jas_types.h:162: error: conflicting types 
for 'int_fast16_t'
/usr/include/sys/_inttypes.h:145: error: previous declaration 
of 'int_fast16_t' was here
jasper/src/libjasper/include/jasper/jas_types.h:168: error: conflicting types 
for 'uint_fast16_t'
/usr/include/sys/_inttypes.h:148: error: previous declaration 
of 'uint_fast16_t' was here
*** Error exit code 1

HP-UX HOSTNAME B.11.11 U 9000/800 1503414882 unlimited-user license


model
9000/800/SD32A
Comment 1 Ralph Giles 2009-04-01 23:17:10 UTC
These configuration issues are difficult to fix generally without access to the
system in question. It would help to know what header is pulling in
/usr/include/sys/_inttypes.h. Is it from inttypes.h?

You can also try adding this to the build as a work around:

-DINT_FAST8_MIN=-127 -DUINT_FAST8_MAX=255 -DINT_FAST16_MIN=-32768
-DUINT_FAST16_MAX=65535
Comment 2 Hin-Tak Leung 2010-05-02 02:36:48 UTC

*** This bug has been marked as a duplicate of bug 688184 ***