Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 81104 - libtiff doesn't build
libtiff doesn't build
Product: Red Hat Raw Hide
Classification: Retired
Component: libtiff (Show other bugs)
powerpc Linux
medium Severity medium
: ---
: ---
Assigned To: Jonathan Blandford
Depends On:
  Show dependency treegraph
Reported: 2003-01-04 15:20 EST by franz.sirl-kernel
Modified: 2013-04-02 00:17 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-02-11 12:06:41 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description franz.sirl-kernel 2003-01-04 15:20:17 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux ppc; en-US; rv:1.2.1) Gecko/20021218

Description of problem:
I wonder what tricks are used at RH to build this package, it simply doesn't
work for me.
Each rpm --rebuild gives me:

Creating Makefile from ./Makefile.in
Creating libtiff/Makefile from ./libtiff/Makefile.in
Creating man/Makefile from ./man/Makefile.in
Creating tools/Makefile from ./tools/Makefile.in
Creating port/install.sh from ./port/install.sh.in
+ cd libtiff
+ ln -s libtiff.so.3.5 libtiff.so
+ cd ..
+ export LDOPTS=-s
+ make 'LIBJPEG=-L/usr/lib -ljpeg' 'LIBGZ=-L/usr/lib -lz'
= libtiff
make: invalid option -- L
Usage: make [options] [target] ...
  -b, -m                      Ignored for compatibility.

It seems the culprit is the original tiff-v3.5.7/Makefile.in, it contains:

all default:
        @if [ "no" = yes ]; then \
            ${ECHO} "= "port; cd port; ${MAKE} -${MAKEFLAGS}; \
        else \
            true; \
        @${ECHO} "= "libtiff; cd libtiff; ${MAKE} -${MAKEFLAGS}
        @${ECHO} "= "tools; cd tools; ${MAKE} -${MAKEFLAGS}
        @${ECHO} "= "man; cd man; ${MAKE} -${MAKEFLAGS}

Note the dashes (-) in front of ${MAKEFLAGS}? Together with the LIBJPEG= command
line argument they form the "invalid" -L option for make.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. rpmbuild --rebuild libtiff src rpm

Additional info:
Comment 1 Jonathan Blandford 2003-01-24 16:38:33 EST
Current Rawhide (libtiff-3.5.7-9.src.rpm) works for me.
Comment 2 franz.sirl-kernel 2003-02-01 16:48:10 EST
Now I found out why it works for you, you are building on a SMP machine, or?
Try on a UP one or remove the %{?_smp_mflags} from the make invocation in the
specfile and watch it failing.
Comment 3 Phil Knirsch 2003-02-11 12:06:41 EST
OK, verified and fixed in libtiff-3.5.7-11, building right now and available via
rawhide soon.

Read ya, Phil

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