SHA256
1
0
forked from pool/binutils

Work around dependency problems

OBS-URL: https://build.opensuse.org/package/show/devel:gcc/binutils?expand=0&rev=371
This commit is contained in:
Michael Matz 2021-10-12 14:01:53 +00:00 committed by Git OBS Bridge
parent f755c60377
commit 30b18fbb6b
23 changed files with 184 additions and 0 deletions

View File

@ -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}

View File

@ -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}

View File

@ -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}

View File

@ -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}

View File

@ -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}

View File

@ -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}

View File

@ -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}

View File

@ -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}

View File

@ -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}

View File

@ -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}

View File

@ -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}

View File

@ -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}

View File

@ -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}

View File

@ -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}

View File

@ -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}

View File

@ -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}

View File

@ -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}

View File

@ -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}

View File

@ -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}

View File

@ -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}

View File

@ -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}

View File

@ -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}

View File

@ -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}