Bug 9951 - glibc src.rpm breaks when trying to rebuild
Summary: glibc src.rpm breaks when trying to rebuild
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: glibc
Version: 6.2
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Cristian Gafton
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2000-03-04 05:04 UTC by Matthew Miller
Modified: 2008-05-01 15:37 UTC (History)
0 users

Clone Of:
Last Closed: 2000-03-04 18:23:57 UTC

Attachments (Terms of Use)

Description Matthew Miller 2000-03-04 05:04:43 UTC
The glibc src rpm doesn't seem to want to rebuild properly under RH 6.2
beta. (I've also tried glibc-2.1.3-14.src.rpm from Rawhide, with the same
results.) I'm installing the srpm and doing a rpm -bb, with no success.

It all seems to compile fine, and then dies during the install stage, with:

../scripts/mkinstalldirs /var/tmp/glibc-2.1.3-root/usr/info
mkdir /var/tmp/glibc-2.1.3-root/usr/info
for file in libc.info*; do \
  /usr/bin/install -c -m 644 $file
/var/tmp/glibc-2.1.3-root/usr/info/$file; \
/usr/bin/install: libc.info*: No such file or directory
make[2]: *** [/var/tmp/glibc-2.1.3-root/usr/info/libc.info] Error 1
make[2]: Leaving directory `/usr/src/redhat/BUILD/glibc-2.1.3/manual'
make[1]: *** [manual/subdir_install] Error 2
make[1]: Leaving directory `/usr/src/redhat/BUILD/glibc-2.1.3'
make: *** [install] Error 2
make: Leaving directory
Bad exit status from /var/tmp/rpm-tmp.85277 (%install)

I've not tried this under 6.1....

Comment 1 Matthew Miller 2000-03-04 18:18:59 UTC
I get this same problem trying to build the glibc-2.1.2-11.src.rpm from RH 6.1.
Is there some special requirement for building this RPM which I'm missing?

Comment 2 Cristian Gafton 2000-03-04 18:23:59 UTC
Do you have texinfo installed?
Check carefully the output of the /.configure step

Comment 3 Matthew Miller 2000-03-04 18:41:59 UTC
Ah, good call. No, I didn't have texinfo installed.  Rebuilding now with it
there. Thanks.

PS -- might this be a good "BuildRequires" option for the spec file?

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