Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Checking Base types ...Ok.
Checking endianess ...FAIL!
endianess:
OOOPPSS! You have CMS_USE_BIG_ENDIAN toggle misconfigured!
Please, edit lcms2.h and comment the CMS_USE_BIG_ENDIAN toggle.
Checking quick floor ...FAIL!
quick floor:
OOOPPSS! _cmsQuickFloor() does not work as expected in your machine!
Please, edit lcms2.h and uncomment the CMS_DONT_USE_FAST_FLOOR toggle.
Checking quick floor word ...FAIL!
quick floor word:
OOOPPSS! _cmsQuickFloorWord() does not work as expected in your machine!
Please, edit lcms2.h and uncomment the CMS_DONT_USE_FAST_FLOOR toggle.
Checking Fixed point 15.16 representation ...Ok.
Checking Fixed point 8.8 representation ...Ok.
Checking D50 roundtrip ...Ok.
Checking Creation of test profiles ................Ok.
Checking 1D interpolation in 2pt tables ...Ok.
Checking 1D interpolation in 3pt tables ...Ok.
Checking 1D interpolation in 4pt tables ...Ok.
Checking 1D interpolation in 6pt tables ...Ok.
Checking 1D interpolation in 18pt tables ...Ok.
Checking 1D interpolation in descending 2pt tables ...Ok.
Checking 1D interpolation in descending 3pt tables ...Ok.
Checking 1D interpolation in descending 6pt tables ...Ok.
Checking 1D interpolation in descending 18pt tables ...Ok.
Checking 3D interpolation Tetrahedral (float) ...make[1]: *** [check] Segmentation fault
make[1]: Leaving directory `/home/test/rpmbuild/BUILD/lcms2-2.6/testbed'
make: *** [check-recursive] Error 1
-------- make check has FAILED --------
Version-Release number of selected component (if applicable):
lcms2-2.6-2.el7
How reproducible:
100%
Steps to Reproduce:
1. make check
2.
3.
Actual results:
see summary, endianess check FAILED on ppc64le
Expected results:
Additional info:
only failing on ppc64le
(In reply to Tomas Pelka from comment #2)
> Matthias is it feasible to fix for 7.2?
>
> It is blocking bug 1246155 which on QA.
My bad it is not, so it can be postponed to 7.3.
*** Bug 1272605 has been marked as a duplicate of this bug. ***
Comment 6Andrew John Hughes
2015-12-16 02:32:20 UTC
Seems odd to me that this wouldn't be fixed for 7.2, given that LCMS 2 build is basically completely broken on ppc64le.
See bug 1272605 which has a fix for this, which also includes enabling the test suite so that issues like this are caught straight away.
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://rhn.redhat.com/errata/RHBA-2016-2426.html
Comment 21Red Hat Bugzilla
2023-09-14 03:03:16 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days