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.
Created attachment 136750 [details] patch which adds required %if %{build_java}
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