Bug 207303

Summary: cannot rebuild gcc when build_java is 0
Product: Red Hat Enterprise Linux 4 Reporter: John Reiser <jreiser>
Component: gccAssignee: Jakub Jelinek <jakub>
Status: CLOSED ERRATA QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 4.0   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: RHSA-2007-0220 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-05-01 17:08:28 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
patch which adds required %if %{build_java} none

Description John Reiser 2006-09-20 15:51:08 UTC
Description of problem: Rebuilding gcc-3.4.6-3 fails when build_java is 0. 
There are two places in the .spec that need "%if %{build_java}".


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

How reproducible:
always

Steps to Reproduce:
1. Change build_java to 0 at line 10 of the .spec .
2. rpmbuild -ba --target i686 gcc.spec
3.
  
Actual results:
+ sed -i -e 's/lib: /&%{static:%eJava programs cannot be linked statically}/'
/var/tmp/gcc-3.4.6-3-root/usr/lib/gcc/i686-redhat-linux/3.4.6/libgcj.spec
sed: can't read
/var/tmp/gcc-3.4.6-3-root/usr/lib/gcc/i686-redhat-linux/3.4.6/libgcj.spec: No
such file or directory
   <<then, after fixing that problem, there is another:>>
+ mv -f /var/tmp/gcc-3.4.6-3-root/usr/share/java/libgcj-3.4.6.jar
/var/tmp/gcc-3.4.6-3-root/usr/share/java/libgcj-3.4.3.jar
mv: cannot stat `/var/tmp/gcc-3.4.6-3-root/usr/share/java/libgcj-3.4.6.jar': No
such file or directory


Expected results:
successful build


Additional info:  Patch will be attached.

Comment 1 John Reiser 2006-09-20 15:51:08 UTC
Created attachment 136750 [details]
patch which adds required %if %{build_java}

Comment 7 Red Hat Bugzilla 2007-05-01 17:08:28 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHSA-2007-0220.html