diff --git a/binutils.spec b/binutils.spec
index 21a6ab7..5f7ac23 100644
--- a/binutils.spec
+++ b/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}
diff --git a/cross-aarch64-binutils.spec b/cross-aarch64-binutils.spec
index 73b019d..5a02801 100644
--- a/cross-aarch64-binutils.spec
+++ b/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}
diff --git a/cross-arm-binutils.spec b/cross-arm-binutils.spec
index cdaa9e2..04956da 100644
--- a/cross-arm-binutils.spec
+++ b/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}
diff --git a/cross-avr-binutils.spec b/cross-avr-binutils.spec
index 85a3ef2..3103ae7 100644
--- a/cross-avr-binutils.spec
+++ b/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}
diff --git a/cross-epiphany-binutils.spec b/cross-epiphany-binutils.spec
index 23d0385..70ab959 100644
--- a/cross-epiphany-binutils.spec
+++ b/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}
diff --git a/cross-hppa-binutils.spec b/cross-hppa-binutils.spec
index c95383e..fbe4179 100644
--- a/cross-hppa-binutils.spec
+++ b/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}
diff --git a/cross-hppa64-binutils.spec b/cross-hppa64-binutils.spec
index 30b6c82..4276412 100644
--- a/cross-hppa64-binutils.spec
+++ b/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}
diff --git a/cross-i386-binutils.spec b/cross-i386-binutils.spec
index f520509..9d6d6a8 100644
--- a/cross-i386-binutils.spec
+++ b/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}
diff --git a/cross-ia64-binutils.spec b/cross-ia64-binutils.spec
index 1bc4482..98c06bc 100644
--- a/cross-ia64-binutils.spec
+++ b/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}
diff --git a/cross-m68k-binutils.spec b/cross-m68k-binutils.spec
index db0e870..799190e 100644
--- a/cross-m68k-binutils.spec
+++ b/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}
diff --git a/cross-mips-binutils.spec b/cross-mips-binutils.spec
index 66f0f2f..a21d9be 100644
--- a/cross-mips-binutils.spec
+++ b/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}
diff --git a/cross-ppc-binutils.spec b/cross-ppc-binutils.spec
index b9ea0d1..70415ac 100644
--- a/cross-ppc-binutils.spec
+++ b/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}
diff --git a/cross-ppc64-binutils.spec b/cross-ppc64-binutils.spec
index 75b57a0..b1ebea0 100644
--- a/cross-ppc64-binutils.spec
+++ b/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}
diff --git a/cross-ppc64le-binutils.spec b/cross-ppc64le-binutils.spec
index 8604c2f..118c6f1 100644
--- a/cross-ppc64le-binutils.spec
+++ b/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}
diff --git a/cross-riscv64-binutils.spec b/cross-riscv64-binutils.spec
index 0722960..f99672c 100644
--- a/cross-riscv64-binutils.spec
+++ b/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}
diff --git a/cross-rx-binutils.spec b/cross-rx-binutils.spec
index 314ac6c..53c8601 100644
--- a/cross-rx-binutils.spec
+++ b/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}
diff --git a/cross-s390-binutils.spec b/cross-s390-binutils.spec
index 56b91ec..daf187b 100644
--- a/cross-s390-binutils.spec
+++ b/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}
diff --git a/cross-s390x-binutils.spec b/cross-s390x-binutils.spec
index d9376aa..ab15386 100644
--- a/cross-s390x-binutils.spec
+++ b/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}
diff --git a/cross-sparc-binutils.spec b/cross-sparc-binutils.spec
index 8963693..6a36c3b 100644
--- a/cross-sparc-binutils.spec
+++ b/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}
diff --git a/cross-sparc64-binutils.spec b/cross-sparc64-binutils.spec
index 44b6789..d64e901 100644
--- a/cross-sparc64-binutils.spec
+++ b/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}
diff --git a/cross-spu-binutils.spec b/cross-spu-binutils.spec
index 36be068..21b3d4a 100644
--- a/cross-spu-binutils.spec
+++ b/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}
diff --git a/cross-x86_64-binutils.spec b/cross-x86_64-binutils.spec
index 8d034c1..5734106 100644
--- a/cross-x86_64-binutils.spec
+++ b/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}
diff --git a/cross-xtensa-binutils.spec b/cross-xtensa-binutils.spec
index 4452ff7..029d76b 100644
--- a/cross-xtensa-binutils.spec
+++ b/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}