Work around dependency problems

OBS-URL: https://build.opensuse.org/package/show/devel:gcc/binutils?expand=0&rev=371

binutils.spec

@@ -221,6 +221,14 @@ cp gas/config/tc-avr.h gas/config/tc-avr-nesc.h
 #
 # test_vanilla
 %endif
+# in parallel builds, when the flex or bison inputs are patched (possibly
+# in the ...-branch.diff) it might happen that the dependency tracking
+# of automake is confused and uses the old .c files from srcdir/ld/ while
+# also generating the new .c files in builddir/ld leading to trouble.
+# I haven't found the right entries to ensure this doesn't happen, so
+# simply remove the intermediates
+rm -f ld/ldlex.c
+rm -f ld/ldgram.c ld/ldgram.h
 
 %build
 %define _lto_cflags %{nil}

cross-aarch64-binutils.spec

@@ -224,6 +224,14 @@ cp gas/config/tc-avr.h gas/config/tc-avr-nesc.h
 #
 # test_vanilla
 %endif
+# in parallel builds, when the flex or bison inputs are patched (possibly
+# in the ...-branch.diff) it might happen that the dependency tracking
+# of automake is confused and uses the old .c files from srcdir/ld/ while
+# also generating the new .c files in builddir/ld leading to trouble.
+# I haven't found the right entries to ensure this doesn't happen, so
+# simply remove the intermediates
+rm -f ld/ldlex.c
+rm -f ld/ldgram.c ld/ldgram.h
 
 %build
 %define _lto_cflags %{nil}

cross-arm-binutils.spec

@@ -224,6 +224,14 @@ cp gas/config/tc-avr.h gas/config/tc-avr-nesc.h
 #
 # test_vanilla
 %endif
+# in parallel builds, when the flex or bison inputs are patched (possibly
+# in the ...-branch.diff) it might happen that the dependency tracking
+# of automake is confused and uses the old .c files from srcdir/ld/ while
+# also generating the new .c files in builddir/ld leading to trouble.
+# I haven't found the right entries to ensure this doesn't happen, so
+# simply remove the intermediates
+rm -f ld/ldlex.c
+rm -f ld/ldgram.c ld/ldgram.h
 
 %build
 %define _lto_cflags %{nil}

cross-avr-binutils.spec

@@ -224,6 +224,14 @@ cp gas/config/tc-avr.h gas/config/tc-avr-nesc.h
 #
 # test_vanilla
 %endif
+# in parallel builds, when the flex or bison inputs are patched (possibly
+# in the ...-branch.diff) it might happen that the dependency tracking
+# of automake is confused and uses the old .c files from srcdir/ld/ while
+# also generating the new .c files in builddir/ld leading to trouble.
+# I haven't found the right entries to ensure this doesn't happen, so
+# simply remove the intermediates
+rm -f ld/ldlex.c
+rm -f ld/ldgram.c ld/ldgram.h
 
 %build
 %define _lto_cflags %{nil}

cross-epiphany-binutils.spec

@@ -224,6 +224,14 @@ cp gas/config/tc-avr.h gas/config/tc-avr-nesc.h
 #
 # test_vanilla
 %endif
+# in parallel builds, when the flex or bison inputs are patched (possibly
+# in the ...-branch.diff) it might happen that the dependency tracking
+# of automake is confused and uses the old .c files from srcdir/ld/ while
+# also generating the new .c files in builddir/ld leading to trouble.
+# I haven't found the right entries to ensure this doesn't happen, so
+# simply remove the intermediates
+rm -f ld/ldlex.c
+rm -f ld/ldgram.c ld/ldgram.h
 
 %build
 %define _lto_cflags %{nil}

cross-hppa-binutils.spec

@@ -224,6 +224,14 @@ cp gas/config/tc-avr.h gas/config/tc-avr-nesc.h
 #
 # test_vanilla
 %endif
+# in parallel builds, when the flex or bison inputs are patched (possibly
+# in the ...-branch.diff) it might happen that the dependency tracking
+# of automake is confused and uses the old .c files from srcdir/ld/ while
+# also generating the new .c files in builddir/ld leading to trouble.
+# I haven't found the right entries to ensure this doesn't happen, so
+# simply remove the intermediates
+rm -f ld/ldlex.c
+rm -f ld/ldgram.c ld/ldgram.h
 
 %build
 %define _lto_cflags %{nil}

cross-hppa64-binutils.spec

@@ -224,6 +224,14 @@ cp gas/config/tc-avr.h gas/config/tc-avr-nesc.h
 #
 # test_vanilla
 %endif
+# in parallel builds, when the flex or bison inputs are patched (possibly
+# in the ...-branch.diff) it might happen that the dependency tracking
+# of automake is confused and uses the old .c files from srcdir/ld/ while
+# also generating the new .c files in builddir/ld leading to trouble.
+# I haven't found the right entries to ensure this doesn't happen, so
+# simply remove the intermediates
+rm -f ld/ldlex.c
+rm -f ld/ldgram.c ld/ldgram.h
 
 %build
 %define _lto_cflags %{nil}

cross-i386-binutils.spec

@@ -224,6 +224,14 @@ cp gas/config/tc-avr.h gas/config/tc-avr-nesc.h
 #
 # test_vanilla
 %endif
+# in parallel builds, when the flex or bison inputs are patched (possibly
+# in the ...-branch.diff) it might happen that the dependency tracking
+# of automake is confused and uses the old .c files from srcdir/ld/ while
+# also generating the new .c files in builddir/ld leading to trouble.
+# I haven't found the right entries to ensure this doesn't happen, so
+# simply remove the intermediates
+rm -f ld/ldlex.c
+rm -f ld/ldgram.c ld/ldgram.h
 
 %build
 %define _lto_cflags %{nil}

cross-ia64-binutils.spec

@@ -224,6 +224,14 @@ cp gas/config/tc-avr.h gas/config/tc-avr-nesc.h
 #
 # test_vanilla
 %endif
+# in parallel builds, when the flex or bison inputs are patched (possibly
+# in the ...-branch.diff) it might happen that the dependency tracking
+# of automake is confused and uses the old .c files from srcdir/ld/ while
+# also generating the new .c files in builddir/ld leading to trouble.
+# I haven't found the right entries to ensure this doesn't happen, so
+# simply remove the intermediates
+rm -f ld/ldlex.c
+rm -f ld/ldgram.c ld/ldgram.h
 
 %build
 %define _lto_cflags %{nil}

cross-m68k-binutils.spec

@@ -224,6 +224,14 @@ cp gas/config/tc-avr.h gas/config/tc-avr-nesc.h
 #
 # test_vanilla
 %endif
+# in parallel builds, when the flex or bison inputs are patched (possibly
+# in the ...-branch.diff) it might happen that the dependency tracking
+# of automake is confused and uses the old .c files from srcdir/ld/ while
+# also generating the new .c files in builddir/ld leading to trouble.
+# I haven't found the right entries to ensure this doesn't happen, so
+# simply remove the intermediates
+rm -f ld/ldlex.c
+rm -f ld/ldgram.c ld/ldgram.h
 
 %build
 %define _lto_cflags %{nil}

cross-mips-binutils.spec

@@ -224,6 +224,14 @@ cp gas/config/tc-avr.h gas/config/tc-avr-nesc.h
 #
 # test_vanilla
 %endif
+# in parallel builds, when the flex or bison inputs are patched (possibly
+# in the ...-branch.diff) it might happen that the dependency tracking
+# of automake is confused and uses the old .c files from srcdir/ld/ while
+# also generating the new .c files in builddir/ld leading to trouble.
+# I haven't found the right entries to ensure this doesn't happen, so
+# simply remove the intermediates
+rm -f ld/ldlex.c
+rm -f ld/ldgram.c ld/ldgram.h
 
 %build
 %define _lto_cflags %{nil}

cross-ppc-binutils.spec

@@ -224,6 +224,14 @@ cp gas/config/tc-avr.h gas/config/tc-avr-nesc.h
 #
 # test_vanilla
 %endif
+# in parallel builds, when the flex or bison inputs are patched (possibly
+# in the ...-branch.diff) it might happen that the dependency tracking
+# of automake is confused and uses the old .c files from srcdir/ld/ while
+# also generating the new .c files in builddir/ld leading to trouble.
+# I haven't found the right entries to ensure this doesn't happen, so
+# simply remove the intermediates
+rm -f ld/ldlex.c
+rm -f ld/ldgram.c ld/ldgram.h
 
 %build
 %define _lto_cflags %{nil}

cross-ppc64-binutils.spec

@@ -224,6 +224,14 @@ cp gas/config/tc-avr.h gas/config/tc-avr-nesc.h
 #
 # test_vanilla
 %endif
+# in parallel builds, when the flex or bison inputs are patched (possibly
+# in the ...-branch.diff) it might happen that the dependency tracking
+# of automake is confused and uses the old .c files from srcdir/ld/ while
+# also generating the new .c files in builddir/ld leading to trouble.
+# I haven't found the right entries to ensure this doesn't happen, so
+# simply remove the intermediates
+rm -f ld/ldlex.c
+rm -f ld/ldgram.c ld/ldgram.h
 
 %build
 %define _lto_cflags %{nil}

cross-ppc64le-binutils.spec

@@ -224,6 +224,14 @@ cp gas/config/tc-avr.h gas/config/tc-avr-nesc.h
 #
 # test_vanilla
 %endif
+# in parallel builds, when the flex or bison inputs are patched (possibly
+# in the ...-branch.diff) it might happen that the dependency tracking
+# of automake is confused and uses the old .c files from srcdir/ld/ while
+# also generating the new .c files in builddir/ld leading to trouble.
+# I haven't found the right entries to ensure this doesn't happen, so
+# simply remove the intermediates
+rm -f ld/ldlex.c
+rm -f ld/ldgram.c ld/ldgram.h
 
 %build
 %define _lto_cflags %{nil}

cross-riscv64-binutils.spec

@@ -224,6 +224,14 @@ cp gas/config/tc-avr.h gas/config/tc-avr-nesc.h
 #
 # test_vanilla
 %endif
+# in parallel builds, when the flex or bison inputs are patched (possibly
+# in the ...-branch.diff) it might happen that the dependency tracking
+# of automake is confused and uses the old .c files from srcdir/ld/ while
+# also generating the new .c files in builddir/ld leading to trouble.
+# I haven't found the right entries to ensure this doesn't happen, so
+# simply remove the intermediates
+rm -f ld/ldlex.c
+rm -f ld/ldgram.c ld/ldgram.h
 
 %build
 %define _lto_cflags %{nil}

cross-rx-binutils.spec

@@ -224,6 +224,14 @@ cp gas/config/tc-avr.h gas/config/tc-avr-nesc.h
 #
 # test_vanilla
 %endif
+# in parallel builds, when the flex or bison inputs are patched (possibly
+# in the ...-branch.diff) it might happen that the dependency tracking
+# of automake is confused and uses the old .c files from srcdir/ld/ while
+# also generating the new .c files in builddir/ld leading to trouble.
+# I haven't found the right entries to ensure this doesn't happen, so
+# simply remove the intermediates
+rm -f ld/ldlex.c
+rm -f ld/ldgram.c ld/ldgram.h
 
 %build
 %define _lto_cflags %{nil}

cross-s390-binutils.spec

@@ -224,6 +224,14 @@ cp gas/config/tc-avr.h gas/config/tc-avr-nesc.h
 #
 # test_vanilla
 %endif
+# in parallel builds, when the flex or bison inputs are patched (possibly
+# in the ...-branch.diff) it might happen that the dependency tracking
+# of automake is confused and uses the old .c files from srcdir/ld/ while
+# also generating the new .c files in builddir/ld leading to trouble.
+# I haven't found the right entries to ensure this doesn't happen, so
+# simply remove the intermediates
+rm -f ld/ldlex.c
+rm -f ld/ldgram.c ld/ldgram.h
 
 %build
 %define _lto_cflags %{nil}

cross-s390x-binutils.spec

@@ -224,6 +224,14 @@ cp gas/config/tc-avr.h gas/config/tc-avr-nesc.h
 #
 # test_vanilla
 %endif
+# in parallel builds, when the flex or bison inputs are patched (possibly
+# in the ...-branch.diff) it might happen that the dependency tracking
+# of automake is confused and uses the old .c files from srcdir/ld/ while
+# also generating the new .c files in builddir/ld leading to trouble.
+# I haven't found the right entries to ensure this doesn't happen, so
+# simply remove the intermediates
+rm -f ld/ldlex.c
+rm -f ld/ldgram.c ld/ldgram.h
 
 %build
 %define _lto_cflags %{nil}

cross-sparc-binutils.spec

@@ -224,6 +224,14 @@ cp gas/config/tc-avr.h gas/config/tc-avr-nesc.h
 #
 # test_vanilla
 %endif
+# in parallel builds, when the flex or bison inputs are patched (possibly
+# in the ...-branch.diff) it might happen that the dependency tracking
+# of automake is confused and uses the old .c files from srcdir/ld/ while
+# also generating the new .c files in builddir/ld leading to trouble.
+# I haven't found the right entries to ensure this doesn't happen, so
+# simply remove the intermediates
+rm -f ld/ldlex.c
+rm -f ld/ldgram.c ld/ldgram.h
 
 %build
 %define _lto_cflags %{nil}

cross-sparc64-binutils.spec

@@ -224,6 +224,14 @@ cp gas/config/tc-avr.h gas/config/tc-avr-nesc.h
 #
 # test_vanilla
 %endif
+# in parallel builds, when the flex or bison inputs are patched (possibly
+# in the ...-branch.diff) it might happen that the dependency tracking
+# of automake is confused and uses the old .c files from srcdir/ld/ while
+# also generating the new .c files in builddir/ld leading to trouble.
+# I haven't found the right entries to ensure this doesn't happen, so
+# simply remove the intermediates
+rm -f ld/ldlex.c
+rm -f ld/ldgram.c ld/ldgram.h
 
 %build
 %define _lto_cflags %{nil}

cross-spu-binutils.spec

@@ -224,6 +224,14 @@ cp gas/config/tc-avr.h gas/config/tc-avr-nesc.h
 #
 # test_vanilla
 %endif
+# in parallel builds, when the flex or bison inputs are patched (possibly
+# in the ...-branch.diff) it might happen that the dependency tracking
+# of automake is confused and uses the old .c files from srcdir/ld/ while
+# also generating the new .c files in builddir/ld leading to trouble.
+# I haven't found the right entries to ensure this doesn't happen, so
+# simply remove the intermediates
+rm -f ld/ldlex.c
+rm -f ld/ldgram.c ld/ldgram.h
 
 %build
 %define _lto_cflags %{nil}

cross-x86_64-binutils.spec

@@ -224,6 +224,14 @@ cp gas/config/tc-avr.h gas/config/tc-avr-nesc.h
 #
 # test_vanilla
 %endif
+# in parallel builds, when the flex or bison inputs are patched (possibly
+# in the ...-branch.diff) it might happen that the dependency tracking
+# of automake is confused and uses the old .c files from srcdir/ld/ while
+# also generating the new .c files in builddir/ld leading to trouble.
+# I haven't found the right entries to ensure this doesn't happen, so
+# simply remove the intermediates
+rm -f ld/ldlex.c
+rm -f ld/ldgram.c ld/ldgram.h
 
 %build
 %define _lto_cflags %{nil}

cross-xtensa-binutils.spec

@@ -224,6 +224,14 @@ cp gas/config/tc-avr.h gas/config/tc-avr-nesc.h
 #
 # test_vanilla
 %endif
+# in parallel builds, when the flex or bison inputs are patched (possibly
+# in the ...-branch.diff) it might happen that the dependency tracking
+# of automake is confused and uses the old .c files from srcdir/ld/ while
+# also generating the new .c files in builddir/ld leading to trouble.
+# I haven't found the right entries to ensure this doesn't happen, so
+# simply remove the intermediates
+rm -f ld/ldlex.c
+rm -f ld/ldgram.c ld/ldgram.h
 
 %build
 %define _lto_cflags %{nil}