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.
Bug 1250914 - ppc64le endianess check FAILED
Summary: ppc64le endianess check FAILED
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: lcms2
Version: 7.2
Hardware: ppc64le
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Richard Hughes
QA Contact: Desktop QE
URL:
Whiteboard:
: 1272605 (view as bug list)
Depends On:
Blocks: 1243784 1246155 1289025 1295396 1297828 1297830 1313485 1317949 1334445
TreeView+ depends on / blocked
 
Reported: 2015-08-06 09:47 UTC by Tomas Pelka
Modified: 2023-09-14 03:03 UTC (History)
8 users (show)

Fixed In Version: lcms2-2.6-3.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-04 06:20:42 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2426 0 normal SHIPPED_LIVE lcms2 bug fix update 2016-11-03 13:59:52 UTC

Description Tomas Pelka 2015-08-06 09:47:42 UTC 
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
Comment 1 Tomas Pelka 2015-08-06 09:48:19 UTC 
Full log at http://beaker-archive.app.eng.bos.redhat.com/beaker-logs/2015/08/10408/1040891/2130083/33086114/TESTOUT.log (scroll down)
Comment 2 Tomas Pelka 2015-09-07 09:40:46 UTC 
Matthias is it feasible to fix for 7.2?

It is blocking bug 1246155 which on QA.
Comment 3 Tomas Pelka 2015-09-07 10:00:28 UTC 
(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.
Comment 4 Tomas Pelka 2015-10-23 12:55:57 UTC 
*** Bug 1272605 has been marked as a duplicate of this bug. ***
Comment 6 Andrew 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.
Comment 8 Dan Horák 2016-01-13 12:52:56 UTC 
Can we make a z-stream for this fix? It is causing an immediate segfault in ghostscript on ppc64le.
Comment 9 Andrew John Hughes 2016-01-14 01:08:16 UTC 
Yes, as I said in comment 6, I don't see how the version shipped in 7.2 would be in any way usable. It's built as big-endian.
Comment 20 errata-xmlrpc 2016-11-04 06:20:42 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://rhn.redhat.com/errata/RHBA-2016-2426.html
Comment 21 Red 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
Note You need to log in before you can comment on or make changes to this bug.