Red Hat Bugzilla – Bug 244778
libjpeg patch4 is not applied
Last modified: 2013-07-02 23:13:38 EDT
Description of problem:
the cflags patch patch4 is not applied. please have it applied
[ new maintainer here... ] That patch seems a tad random, and given the lack of other complaints I'm not
in any big hurry to turn it on. What problem are you hoping it would solve?
without it turned on sparc64 fails to build as gcc is used to link. the
default sparc cflags are for sparc not sparc64 the patch makes linking
correct in all cases.
OK, so here's the long answer:
We need a sparc and sparc64 set of BuildRequires for gcc and glibc. This means
that libjpeg needs to be built for both architecture variants. Unfortunately,
without passing CFLAGS on every invocation of CC, gcc assumes that we want to
build for sparc32 (-m32). This works fine on sparc32, but when we're trying to
build for sparc64, this fails (sometimes, we get files built as sparc32
binaries, sometimes, the object files build as sparc64, but gcc tries to link it
as a sparc32 binary which explodes violently). This patch simply enforces that
CFLAGS are used whenever CC is called, and ensures that we get a clean build out
on sparc64. This is always going to be correct, it just happens to cause a
failure on sparc64.
Please apply the patch. :)
The real fix here is probably to forcibly apply a modern autoconf script, but for the moment I've
incorporated this patch into libjpeg-6b-38, pushed to F7 testing today.
libjpeg-6b-38.fc7 has been pushed to the Fedora 7 testing repository. If problems still persist, please make note of it in this bug report.
libjpeg-6b-38.fc7 has been pushed to the Fedora 7 stable repository. If problems still persist, please make note of it in this bug report.