Bug 1297107 - BITS_PER_LONG is not set during builds of netpbm
Summary: BITS_PER_LONG is not set during builds of netpbm
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: netpbm
Version: 23
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Josef Ridky
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-09 10:25 UTC by Steve Underwood
Modified: 2016-08-08 05:40 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-08-08 05:40:20 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Steve Underwood 2016-01-09 10:25:58 UTC
Some of the utilities in the netpbm package, such as pbmtog3m, do not work properly because the variable BITS_PER_LONG is not set during compilation of the RPMs. These utilities either crash, or sit in an infinite loop. If you look at the log during an RPM build there are actual reports that this variable is not set.

If I take the source RPM for netpbm, fudge the build so BITS_PER_LONG is set to 64, and build the utilities, they seem to work OK. At least Fedora 22 and 23 are affected by this issue.

Comment 1 Steve Underwood 2016-01-09 10:27:55 UTC
There were problems with 64 bit builds of the netpbm RPMs back in 2007. They were fixed, and the utilities were working well for a long time on 64 bit machines. The current problem seems to be something recently introduced.

Comment 2 Fedora Admin XMLRPC Client 2016-07-11 10:15:20 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 3 Josef Ridky 2016-08-05 09:50:17 UTC
I am not able to reproduce described bug.

Please tell me, is this bug still actual and if is, how to reproduce it?

(Tested on Fedora 24, 64 bit architecture with newest netpbm release - 10.75.99)

Comment 4 Steve Underwood 2016-08-07 02:48:11 UTC
I installed netpbm 10.75.99 from the updates-testing repo, and it seems to fix the problem. pbmtog3 is no longer crashing, and the files it produces are identical to ones produced on known good machines.


Note You need to log in before you can comment on or make changes to this bug.