Bug 64018 - compiling glibc rpm for --target athlon fails
compiling glibc rpm for --target athlon fails
Product: Red Hat Linux
Classification: Retired
Component: glibc (Show other bugs)
athlon Linux
medium Severity low
: ---
: ---
Assigned To: Jakub Jelinek
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2002-04-23 16:31 EDT by Wilton Wong
Modified: 2007-04-18 12:42 EDT (History)
0 users

See Also:
Fixed In Version: 2.3.2-27.9
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-04-17 13:15:40 EDT
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 Wilton Wong 2002-04-23 16:31:13 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020401

Description of problem:
compiling glibc rpm for --target athlon fails because prelink is never
decompressed and libs aldo end up in /lib/i686 and not /lib/athlon

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

How reproducible:

Steps to Reproduce:
1.rpm -ba --target athlon glibc-2.2.5-....

Actual Results:  %build will fail at prelink portion

Expected Results:  sucessful compile and rpm build

Additional info:

change the lines in glibc.spec: 
%ifarch i686
mkdir prelink
tar x --bzip2 -C prelink -f %{SOURCE2}
%ifarch i686 athlon
mkdir prelink
tar x --bzip2 -C prelink -f %{SOURCE2}

and change the lines:
%ifarch i686 athlon
rm -f $RPM_BUILD_ROOT%{_prefix}/%{_lib}/debug/{libc,libm,libpthread}[-.]*.so*
cp -a $RPM_BUILD_ROOT/%{_lib}/%{_target_cpu}/lib*.so*
%ifarch i686 athlon
rm -f $RPM_BUILD_ROOT%{_prefix}/%{_lib}/debug/{libc,libm,libpthread}[-.]*.so*
cp -a $RPM_BUILD_ROOT/%{_lib}/i686/lib*.so* $RPM_BUILD_ROOT%{_prefix}/%{_lib}/debug/
Comment 1 Ulrich Drepper 2003-04-17 13:15:40 EDT
The glibc .spec file doesn't contain these lines anymore.  It'll use an already
installed prelink package.

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