Bug 1455489

Summary: jasper broken with default standards c++ after security update [rhel-7]
Product: Red Hat Enterprise Linux 7 Reporter: Tomas Hoger <thoger>
Component: jasperAssignee: Josef Ridky <jridky>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: high Docs Contact:
Priority: high    
Version: 7.3CC: ovasik, tpelka
Target Milestone: rcKeywords: Patch, Regression
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: jasper-1.900.1-31.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1455287 Environment:
Last Closed: 2017-08-01 10:07:04 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Tomas Hoger 2017-05-25 10:21:16 UTC 
Also affects RHEL-7 jasper-devel-1.900.1-30.el7_3


+++ This bug was initially created as a clone of Bug #1455287 +++

Jasper worked fine with 0:1.900.1-16.el6_6.3 but no longer works after update to 0:1.900.1-21.el6_9

--

Simple reproducer

#include <iostream>
#include <jasper/jasper.h>
using namespace std;

int main ()
{
  cout << "Hello World!";
  return 0;
}

# g++ test.cpp
In file included from /usr/include/jasper/jasper.h:77,
                 from test.cpp:2:
/usr/include/jasper/jas_math.h: In function ‘bool jas_safe_size_mul(size_t, size_t, size_t*)’:
/usr/include/jasper/jas_math.h:143: error: ‘SIZE_MAX’ was not declared in this scope
/usr/include/jasper/jas_math.h: In function ‘bool jas_safe_size_add(size_t, size_t, size_t*)’:
/usr/include/jasper/jas_math.h:170: error: ‘SIZE_MAX’ was not declared in this scope
Comment 7 errata-xmlrpc 2017-08-01 10:07:04 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:2322