Bug 112918 - LTC5736 - 32 bit glibc not properly installed.
Summary: LTC5736 - 32 bit glibc not properly installed.
Status: CLOSED DUPLICATE of bug 137258
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: kernel
Version: 4.0
Hardware: powerpc
OS: Linux
Target Milestone: ---
: ---
Assignee: Dave Jones
QA Contact: Brian Brock
Depends On:
TreeView+ depends on / blocked
Reported: 2004-01-05 23:10 UTC by Mike Ranweiler
Modified: 2015-01-04 22:04 UTC (History)
4 users (show)

Clone Of:
Last Closed: 2004-11-21 09:38:59 UTC

Attachments (Terms of Use)

Description Mike Ranweiler 2004-01-05 23:10:09 UTC
Hardware Environment: 64bit iSeries

Software Environment: RHEL 3 QU1

Steps to Reproduce:
1. Install RHEL 3 QU1 from a network based QU1 install source.  Do not
the 'Kernel Development' group.
2. After installation add the 'Kernel Development' group using
3. Attempt to compile a kernel.

Actual Results:
The following error is reported:

[root@rchlp626e linux-2.4.21-6.EL]# make dep
gcc -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -o scripts/mkdep
/usr/bin/ld: cannot open crt1.o: No such file or directory
collect2: ld returned 1 exit status
make: *** [scripts/mkdep] Error 1

Expected Results:
I expected that both the 32 and 64bit glibc-devel packages would be
installed when I added the 'Kernel Development' group.

Additional Information:
I checked through redhat-config-packages and all the necessary
'Compatibility Arch Development Support', 'Compatibility Arch
Support', 'Kernel Development' and 'Development Tools' packages appear
to be selected.

When I perform an rpm query I see the following:
[root@rchlp626e mnt]# rpm -q --qf
-%{NAME}-%{VERSION}-%{RELEASE}.%{ARCH}\n" glibc glibc-devel

The 32bit glibc-devel also needs to be installed.  I was able to
resolve the problem by installing the glibc-devel-2.3.2-95.6.ppc rpm.

Comment 1 Jeremy Katz 2004-01-05 23:19:30 UTC
This is a package bug in that the kernel-source package doesn't
express that it requires the 32bit glibc.

Comment 2 Julie DeWandel 2004-01-16 19:31:14 UTC
Reassigning to Ernie for investigation.Thanks Ernie!

Comment 3 IBM Bug Proxy 2004-02-15 16:48:52 UTC
----- Additional Comments From khoa@us.ibm.com  2004-02-15 11:46 -------
Any update on this bug ? 

Comment 4 IBM Bug Proxy 2004-02-16 01:54:30 UTC
----- Additional Comments From mranweil@us.ibm.com  2004-02-15 20:54 -------
I don't believe this was on the list for QU2 -> will target for QU3.  Might be
easy, though. 

Comment 7 Bob Johnson 2004-07-20 12:26:34 UTC
IBM, work around exists - not a candidate for U3.

Comment 8 IBM Bug Proxy 2004-07-26 12:09:25 UTC
----- Additional Comments From pbowen@us.ibm.com  2004-07-26 08:09 -------
Per Bob, moving to RHEL4 tgt 

Comment 10 IBM Bug Proxy 2004-08-17 21:06:37 UTC
----- Additional Comments From khoa@us.ibm.com  2004-08-17 15:18 -------
I'd like to defer this bug until RHEL4 for now.  We'll re-open all RHEL3 bugs 
that have RHEL4 as target this week and mirror them to RH as RHEL4 bugs. 

Comment 11 Jeff Needle 2004-09-13 13:41:38 UTC
Removing from u4 blocker list for now

Comment 12 IBM Bug Proxy 2004-10-27 22:49:54 UTC
----- Additional Comments From pbowen@us.ibm.com  2004-10-27 18:48 EDT -------
Hey RedHat. We need to address this for RHEL4. 

Comment 13 Ernie Petrides 2004-10-27 23:14:14 UTC
Reopened and reassigned to DaveJ per last comment.

Comment 14 IBM Bug Proxy 2004-11-14 22:51:15 UTC
----- Additional Comments From pbowen@us.ibm.com  2004-11-14 15:48 EDT -------
Redhat - pls add your comments on where you think that this fix should be 

Comment 15 IBM Bug Proxy 2004-11-16 19:59:43 UTC
----- Additional Comments From robbiew@us.ibm.com  2004-11-16 14:56 EDT -------
This bug is a dup of a NEWER bug LTC12085/RH137258, which is where we should
probably continue to work.  I recommend closing this older bug as a DUP. 

Comment 16 Jay Turner 2004-11-21 09:38:59 UTC
Closing as a dup as recommended in commnet 15.

*** This bug has been marked as a duplicate of 137258 ***

Comment 17 IBM Bug Proxy 2004-11-22 07:59:23 UTC
----- Additional Comments From khoa@us.ibm.com  2004-11-22 02:58 EDT -------

*** This bug has been marked as a duplicate of 12085 *** 

Comment 18 IBM Bug Proxy 2004-11-22 07:59:44 UTC
----- Additional Comments From khoa@us.ibm.com  2004-11-22 02:59 EDT -------
Closing this bug report per comments above.  Thanks. 

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