Red Hat Bugzilla – Bug 677452
util-linux fails to build with gettext-0.17
Last modified: 2012-09-17 14:32:58 EDT
Description of problem:
util-linux-2.13-0.56.el5 fails to build on RHEL 5. It fails in the po directory:
make: Entering directory `/builddir/build/BUILD/util-linux-2.13-pre7/po'
/bin/sh @MKINSTALLDIRS@ /var/tmp/util-linux-root/usr/share
/bin/sh: @MKINSTALLDIRS@: No such file or directory
make: *** [install-data-yes] Error 127
make: Leaving directory `/builddir/build/BUILD/util-linux-2.13-pre7/po'
make: *** [install-recursive] Error 1
error: Bad exit status from /var/tmp/rpm-tmp.80077 (%install)
RPM build errors:
Bad exit status from /var/tmp/rpm-tmp.80077 (%install)
Child returncode was: 1
I'm not yet sure what changed to break this in RHEL 5.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. rebuild util-linux-2.13-0.56.el5 from source rpm
fails with "@MKINSTALLDIRS@: No such file or directory" error in po directory
successful build of util-linux
This looks similar to Fedora bug 217186. That bug was fixed with this commit:
Hmm, this might be due to the rebase to gettext-0.17-1.el5 in RHEL 5.6, see bug 523713. (It was gettext-0.14.6-4.el5 in RHEL 5.5)
Created attachment 478718 [details]
patch to fix po/Makefile.in.in
The patch from Fedora works beautifully. I was able to successfully build util-linux-2.13-0.56.el5.bz677452 with this patch.
This request was evaluated by Red Hat Product Management for inclusion in Red Hat Enterprise Linux 5.7 and Red Hat does not plan to fix this issue the currently developed update.
Contact your manager or support representative in case you need to escalate this bug.
It seems that it should be enough to add
to the spec file, see https://bugzilla.redhat.com/show_bug.cgi?id=523713#c44
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.