[Bug ld/30002] pr26391-5, pr26391-6 ld test failures on sparc64-unknown-linux-gnu since 496afd17055aeb7d8f45e01715c475664f2b73bd

2023-01-16 Thread sam at gentoo dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=30002

--- Comment #15 from Sam James  ---
(In reply to H.J. Lu from comment #13)
> Created attachment 14602 [details]
> Try this one

This looks to have worked! The failures for binutils-try-debian-i386 /
binutils-try-fedora-arm64 / binutils-try-fedora-s390x exist for the non-try
variants, so they fail on master too.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


[Bug ld/30002] pr26391-5, pr26391-6 ld test failures on sparc64-unknown-linux-gnu since 496afd17055aeb7d8f45e01715c475664f2b73bd

2023-01-16 Thread mark at klomp dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=30002

--- Comment #14 from Mark Wielaard  ---
(In reply to H.J. Lu from comment #13)
> Created attachment 14602 [details]
> Try this one

Note that since the gentoo-sparc builder also does binutils-try builds you can
try by pushing to a branch starting with try- under your users name. e.g
push origin :users/hjl/try-pr30002

More documentation here: https://sourceware.org/binutils/wiki/Buildbot

-- 
You are receiving this mail because:
You are on the CC list for the bug.


[Bug ld/30002] pr26391-5, pr26391-6 ld test failures on sparc64-unknown-linux-gnu since 496afd17055aeb7d8f45e01715c475664f2b73bd

2023-01-16 Thread hjl.tools at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30002

H.J. Lu  changed:

   What|Removed |Added

  Attachment #14601|0   |1
is obsolete||

--- Comment #13 from H.J. Lu  ---
Created attachment 14602
  --> https://sourceware.org/bugzilla/attachment.cgi?id=14602=edit
Try this one

-- 
You are receiving this mail because:
You are on the CC list for the bug.


[Bug ld/30002] pr26391-5, pr26391-6 ld test failures on sparc64-unknown-linux-gnu since 496afd17055aeb7d8f45e01715c475664f2b73bd

2023-01-16 Thread sam at gentoo dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=30002

--- Comment #12 from Sam James  ---
(In reply to Sam James from comment #11)
> Thanks H.J., this works!
> 
>   === ld Summary ===
> # of expected passes  1598
> # of expected failures26
> # of untested testcases   1
> # of unsupported tests157
> 
> What was the issue?

Interestingly, it causes failures on some buildbots (not sparc), like
https://builder.sourceware.org/buildbot/#/builders/113/builds/28.

```
FAIL: Build pr26391-5.o
FAIL: Build pr26391-6.o
PASS: Run pr26391-1
PASS: Run pr26391-2
PASS: Run pr26391-3
PASS: Run pr26391-4
FAIL: Run pr26391-5
FAIL: Run pr26391-6
```

```
gcc 
-B/home/builder/shared/bb1-2/worker/binutils-try-opensuseleap-x86_64/binutils-build/ld/tmpdir/ld/
-I/home/builder/shared/bb1-2/worker/binutils-try-opensuseleap-x86_64/binutils-gdb/ld/testsuite/ld-elf
-g -O2   -c -g -O2 -fno-function-sections -c
/home/builder/shared/bb1-2/worker/binutils-try-opensuseleap-x86_64/binutils-gdb/ld/testsuite/ld-elf/pr26391a.c
-o tmpdir/pr26391a.o
Executing on host: sh -c {gcc 
-B/home/builder/shared/bb1-2/worker/binutils-try-opensuseleap-x86_64/binutils-build/ld/tmpdir/ld/
-I/home/builder/shared/bb1-2/worker/binutils-try-opensuseleap-x86_64/binutils-gdb/ld/testsuite/ld-elf
-g -O2   -c -g -O2 -fno-function-sections -c
/home/builder/shared/bb1-2/worker/binutils-try-opensuseleap-x86_64/binutils-gdb/ld/testsuite/ld-elf/pr26391a.c
-o tmpdir/pr26391a.o 2>&1}  /dev/null ld.tmp (timeout = 300)
spawn [open ...]
gcc 
-B/home/builder/shared/bb1-2/worker/binutils-try-opensuseleap-x86_64/binutils-build/ld/tmpdir/ld/
-I/home/builder/shared/bb1-2/worker/binutils-try-opensuseleap-x86_64/binutils-gdb/ld/testsuite/ld-elf
-g -O2   -c -g -O2 -fno-function-sections -c
/home/builder/shared/bb1-2/worker/binutils-try-opensuseleap-x86_64/binutils-gdb/ld/testsuite/ld-elf/pr26391b.c
-o tmpdir/pr26391b.o
Executing on host: sh -c {gcc 
-B/home/builder/shared/bb1-2/worker/binutils-try-opensuseleap-x86_64/binutils-build/ld/tmpdir/ld/
-I/home/builder/shared/bb1-2/worker/binutils-try-opensuseleap-x86_64/binutils-gdb/ld/testsuite/ld-elf
-g -O2   -c -g -O2 -fno-function-sections -c
/home/builder/shared/bb1-2/worker/binutils-try-opensuseleap-x86_64/binutils-gdb/ld/testsuite/ld-elf/pr26391b.c
-o tmpdir/pr26391b.o 2>&1}  /dev/null ld.tmp (timeout = 300)
spawn [open ...]
gcc 
-B/home/builder/shared/bb1-2/worker/binutils-try-opensuseleap-x86_64/binutils-build/ld/tmpdir/ld/
-I/home/builder/shared/bb1-2/worker/binutils-try-opensuseleap-x86_64/binutils-gdb/ld/testsuite/ld-elf
-g -O2   -c -g -O2 -fno-function-sections -c
/home/builder/shared/bb1-2/worker/binutils-try-opensuseleap-x86_64/binutils-gdb/ld/testsuite/ld-elf/pr26391c.c
-o tmpdir/pr26391c.o
Executing on host: sh -c {gcc 
-B/home/builder/shared/bb1-2/worker/binutils-try-opensuseleap-x86_64/binutils-build/ld/tmpdir/ld/
-I/home/builder/shared/bb1-2/worker/binutils-try-opensuseleap-x86_64/binutils-gdb/ld/testsuite/ld-elf
-g -O2   -c -g -O2 -fno-function-sections -c
/home/builder/shared/bb1-2/worker/binutils-try-opensuseleap-x86_64/binutils-gdb/ld/testsuite/ld-elf/pr26391c.c
-o tmpdir/pr26391c.o 2>&1}  /dev/null ld.tmp (timeout = 300)
spawn [open ...]
gcc 
-B/home/builder/shared/bb1-2/worker/binutils-try-opensuseleap-x86_64/binutils-build/ld/tmpdir/ld/
-I/home/builder/shared/bb1-2/worker/binutils-try-opensuseleap-x86_64/binutils-gdb/ld/testsuite/ld-elf
-g -O2   -c -g -O2 -fno-function-sections -c
/home/builder/shared/bb1-2/worker/binutils-try-opensuseleap-x86_64/binutils-gdb/ld/testsuite/ld-elf/pr26391d.c
-o tmpdir/pr26391d.o
Executing on host: sh -c {gcc 
-B/home/builder/shared/bb1-2/worker/binutils-try-opensuseleap-x86_64/binutils-build/ld/tmpdir/ld/
-I/home/builder/shared/bb1-2/worker/binutils-try-opensuseleap-x86_64/binutils-gdb/ld/testsuite/ld-elf
-g -O2   -c -g -O2 -fno-function-sections -c
/home/builder/shared/bb1-2/worker/binutils-try-opensuseleap-x86_64/binutils-gdb/ld/testsuite/ld-elf/pr26391d.c
-o tmpdir/pr26391d.o 2>&1}  /dev/null ld.tmp (timeout = 300)
spawn [open ...]
gcc
-B/home/builder/shared/bb1-2/worker/binutils-try-opensuseleap-x86_64/binutils-build/ld/tmpdir/ld/
  -L/usr/local/x86_64-pc-linux-gnu/lib64 -L/usr/local/lib64 -L/lib64
-L/usr/lib64 -L/usr/local/x86_64-pc-linux-gnu/lib -L/usr/local/lib -L/lib
-L/usr/lib  -o tmpdir/pr26391-5.o  
-L/home/builder/shared/bb1-2/worker/binutils-try-opensuseleap-x86_64/binutils-gdb/ld/testsuite/ld-elf
-Wl,-z,unique-symbol -r tmpdir/pr26391a.o tmpdir/pr26391b.o tmpdir/pr26391c.o
tmpdir/pr26391d.o
Executing on host: sh -c {gcc
-B/home/builder/shared/bb1-2/worker/binutils-try-opensuseleap-x86_64/binutils-build/ld/tmpdir/ld/
  -L/usr/local/x86_64-pc-linux-gnu/lib64 -L/usr/local/lib64 -L/lib64
-L/usr/lib64 -L/usr/local/x86_64-pc-linux-gnu/lib -L/usr/local/lib -L/lib
-L/usr/lib  -o tmpdir/pr26391-5.o  
-L/home/builder/shared/bb1-2/worker/binutils-try-opensuseleap-x86_64/binutils-gdb/ld/testsuite/ld-elf

[Bug ld/30002] pr26391-5, pr26391-6 ld test failures on sparc64-unknown-linux-gnu since 496afd17055aeb7d8f45e01715c475664f2b73bd

2023-01-16 Thread sam at gentoo dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=30002

--- Comment #11 from Sam James  ---
Thanks H.J., this works!

=== ld Summary ===
# of expected passes1598
# of expected failures  26
# of untested testcases 1
# of unsupported tests  157

What was the issue?

-- 
You are receiving this mail because:
You are on the CC list for the bug.


[Bug ld/30002] pr26391-5, pr26391-6 ld test failures on sparc64-unknown-linux-gnu since 496afd17055aeb7d8f45e01715c475664f2b73bd

2023-01-16 Thread mark at klomp dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=30002

--- Comment #10 from Mark Wielaard  ---
(In reply to cvs-com...@gcc.gnu.org from comment #9)
> The try-PR26391 branch has been updated by Mark Wielaard
> :
> 
> https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;
> h=99175c84026b1bfa534f3946150535c39027911d
> 
> commit 99175c84026b1bfa534f3946150535c39027911d
> Author: Sam James 
> Date:   Mon Jan 16 14:03:02 2023 -0800

Sorry, that was me, but a) I mistyped the correct branch name and b) changed
the Author to Sam to show which emails the buildbot sents out.

The actual try build with this patch is actually here:
https://builder.sourceware.org/buildbot/#/changes/17250

try builders for binutils are described here:
https://sourceware.org/binutils/wiki/Buildbot

-- 
You are receiving this mail because:
You are on the CC list for the bug.


[Bug ld/26391] Question regarding duplicate symbols

2023-01-16 Thread cvs-commit at gcc dot gnu.org
https://sourceware.org/bugzilla/show_bug.cgi?id=26391

--- Comment #14 from cvs-commit at gcc dot gnu.org  ---
The try-PR26391 branch has been updated by Mark Wielaard :

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=99175c84026b1bfa534f3946150535c39027911d

commit 99175c84026b1bfa534f3946150535c39027911d
Author: Sam James 
Date:   Mon Jan 16 14:03:02 2023 -0800

ld: Use run_cc_link_tests for PR ld/26391 tests

Use run_cc_link_tests for PR ld/26391 tests to compile PR ld/26391 tests
in C.

PR ld/30002
* testsuite/ld-elf/elf.exp: Use run_cc_link_tests for PR ld/26391
tests.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


[Bug ld/30002] pr26391-5, pr26391-6 ld test failures on sparc64-unknown-linux-gnu since 496afd17055aeb7d8f45e01715c475664f2b73bd

2023-01-16 Thread cvs-commit at gcc dot gnu.org
https://sourceware.org/bugzilla/show_bug.cgi?id=30002

--- Comment #9 from cvs-commit at gcc dot gnu.org  ---
The try-PR26391 branch has been updated by Mark Wielaard :

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=99175c84026b1bfa534f3946150535c39027911d

commit 99175c84026b1bfa534f3946150535c39027911d
Author: Sam James 
Date:   Mon Jan 16 14:03:02 2023 -0800

ld: Use run_cc_link_tests for PR ld/26391 tests

Use run_cc_link_tests for PR ld/26391 tests to compile PR ld/26391 tests
in C.

PR ld/30002
* testsuite/ld-elf/elf.exp: Use run_cc_link_tests for PR ld/26391
tests.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


[Bug ld/30002] pr26391-5, pr26391-6 ld test failures on sparc64-unknown-linux-gnu since 496afd17055aeb7d8f45e01715c475664f2b73bd

2023-01-16 Thread hjl.tools at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30002

--- Comment #8 from H.J. Lu  ---
Created attachment 14601
  --> https://sourceware.org/bugzilla/attachment.cgi?id=14601=edit
Try this.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


[Bug ld/30002] pr26391-5, pr26391-6 ld test failures on sparc64-unknown-linux-gnu since 496afd17055aeb7d8f45e01715c475664f2b73bd

2023-01-16 Thread hjl.tools at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30002

--- Comment #7 from H.J. Lu  ---
The problem is unrelated to -z unique-symbol. I got

$ cc -B/home/hjlu/build/build-sparc64-linux/ld/tmpdir/ld/  
-L=/usr/local/sparc64-unknown-linux-gnu/lib64 -L=/usr/local/lib64 -L=/lib64
-L=/usr/lib64 -L=/usr/local/sparc64-unknown-linux-gnu/lib -L=/usr/local/lib
-L=/lib -L=/usr/lib  -o tmpdir/pr26391-5g  
-L/home/hjlu/git/binutils-gdb/ld/testsuite/ld-elf tmpdir/dummy.o
tmpdir/pr26391a.o tmpdir/pr26391b.o tmpdir/pr26391c.o tmpdir/pr26391d.o
$ tmpdir/pr26391-5g
Illegal instruction (core dumped)
$

-- 
You are receiving this mail because:
You are on the CC list for the bug.


[Bug ld/30002] pr26391-5, pr26391-6 ld test failures on sparc64-unknown-linux-gnu since 496afd17055aeb7d8f45e01715c475664f2b73bd

2023-01-16 Thread hjl.tools at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30002

--- Comment #6 from H.J. Lu  ---
(In reply to Sam James from comment #5)
> (In reply to H.J. Lu from comment #4)
> > I couldn't reproduce it on GCC compiler farm last time.  The Linux/sparc64
> > machine on GCC compiler farm was down.
> 
> I can give you access to this environment if you email me an SSH key. It's
> purely for CI and clean otherwise.

Done.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


[Bug ld/30002] pr26391-5, pr26391-6 ld test failures on sparc64-unknown-linux-gnu since 496afd17055aeb7d8f45e01715c475664f2b73bd

2023-01-16 Thread sam at gentoo dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=30002

--- Comment #5 from Sam James  ---
(In reply to H.J. Lu from comment #4)
> I couldn't reproduce it on GCC compiler farm last time.  The Linux/sparc64
> machine on GCC compiler farm was down.

I can give you access to this environment if you email me an SSH key. It's
purely for CI and clean otherwise.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


[Bug ld/13671] gld creates i386 relocations not supported by Solaris ld.so.1

2023-01-16 Thread hjl.tools at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=13671

--- Comment #31 from H.J. Lu  ---
(In reply to Rainer Orth from comment #29)
> Created attachment 14590 [details]
> Augmented^2 patch

LGTM.  Please send it to the binutils mailing list.  Thanks.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


[Bug ld/30002] pr26391-5, pr26391-6 ld test failures on sparc64-unknown-linux-gnu since 496afd17055aeb7d8f45e01715c475664f2b73bd

2023-01-16 Thread hjl.tools at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30002

--- Comment #4 from H.J. Lu  ---
(In reply to Mark Wielaard from comment #3)
> See also https://sourceware.org/bugzilla/show_bug.cgi?id=26391#c10

I couldn't reproduce it on GCC compiler farm last time.  The Linux/sparc64
machine on GCC compiler farm was down.  Why does "ld -r -z unique-symbol"
generate incorrect outputs on Linux/sparc64?

-- 
You are receiving this mail because:
You are on the CC list for the bug.


[Bug binutils/29993] objcopy --merge-notes slow for large .so with many annobin notes

2023-01-16 Thread wcohen at redhat dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=29993

--- Comment #7 from William Cohen  ---
I rebuilt the binutils-2.39-8.fc38.src.rpm on the f36 machine that I originally
discover merge_gnu_build_note taking a large fraction of the rpmbuild install
and installed the resulting binutils rpms.  The binutils change reduced samples
in merge_gnu_build_note from 70% to 50%.  Overall runtime was 2085 seconds wall
clock time to 1049 seconds, so half of the original.

compared the notes bewteen the system firefox libxul.so and the locally built
one.  There doesn't seem to be crazy differences between them.

[wcohen@haro firefox-108.0.1-3.fc36.x86_64]$ pwd
/home/wcohen/rpmbuild/BUILDROOT/firefox-108.0.1-3.fc36.x86_64
[wcohen@haro firefox-108.0.1-3.fc36.x86_64]$  readelf --notes --wide
/usr/lib64/firefox/libxul.so  > /tmp/orig_xul
readelf: /usr/lib64/firefox/libxul.so: Warning: Gap in build notes detected
from 0xcb7d6f to 0x661aebf
[wcohen@haro firefox-108.0.1-3.fc36.x86_64]$  readelf --notes --wide
usr/lib64/firefox/libxul.so  > /tmp/new_xul
readelf: usr/lib64/firefox/libxul.so: Warning: Gap in build notes detected from
0xcb7d6f to 0x661aebf
[wcohen@haro firefox-108.0.1-3.fc36.x86_64]$ diff -u /tmp/orig_xul /tmp/new_xul 
--- /tmp/orig_xul   2023-01-16 11:40:56.894249366 -0500
+++ /tmp/new_xul2023-01-16 11:41:07.068311517 -0500
@@ -1,15 +1,15 @@

 Displaying notes found in: .note.gnu.build-id
   OwnerData size   Description
-  GNU  0x0014  NT_GNU_BUILD_ID (unique build ID
bitstring) Build ID: c71b2c4767cf93aa91b2d6ba97d520d954e46eaa
+  GNU  0x0014  NT_GNU_BUILD_ID (unique build ID
bitstring) Build ID: 156d9c0ba3cc3b183e52e29aa814bda4bfec1f84

 Displaying notes found in: .gnu.build.attributes
   OwnerData size   Description
   GA$3a1  0x0010  OPENApplies to region
from 0x9df000 to 0x661aeb2
-  GA$3p1093   0x0010  OPENApplies to region
from 0xcb7372 to 0xcb7d6e
+  GA$3p1092   0x0010  OPENApplies to region
from 0xcb7372 to 0xcb7d6e
   GA*strong0x  OPENApplies to region
from 0xcb7372 to 0xcb7d6e
-  GA$annobin gcc 12.2.1 20220819 0x  OPENApplies to
region from 0xcb7372 to 0xcb7d6e
-  GA$plugin name: annobin 0x OPENApplies to region
from 0xcb7372 to 0xcb7d6e
+  GA$annobin gcc 12.2.1 20221121 0x  OPENApplies to
region from 0xcb7372 to 0xcb7d6e
+  GA$plugin name: gcc-annobin 0x OPENApplies to region
from 0xcb7372 to 0xcb7d6e
   GA$running gcc 12.2.1 20221121 0x  OPENApplies to
region from 0xcb7372 to 0xcb7d6e
   GA*0x12 0x  OPENApplies to region
from 0xcb7372 to 0xcb7d6e
   GA*PIC  0x  OPENApplies to region
from 0xcb7372 to 0xcb7d6e

-- 
You are receiving this mail because:
You are on the CC list for the bug.


[Bug gprofng/30006] Failure to build binutils-2.40 on i686

2023-01-16 Thread sch...@linux-m68k.org
https://sourceware.org/bugzilla/show_bug.cgi?id=30006

Andreas Schwab  changed:

   What|Removed |Added

   Assignee|unassigned at sourceware dot org   |vladimir.mezentsev at 
oracle dot c
   ||om
  Component|binutils|gprofng

-- 
You are receiving this mail because:
You are on the CC list for the bug.


[Bug binutils/30006] Failure to build binutils-2.40 on i686

2023-01-16 Thread satadru at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30006

--- Comment #3 from Satadru Pramanik  ---
Apologies. I have attached the entire build log from our build system.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


[Bug binutils/30006] Failure to build binutils-2.40 on i686

2023-01-16 Thread satadru at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30006

--- Comment #2 from Satadru Pramanik  ---
Created attachment 14599
  --> https://sourceware.org/bugzilla/attachment.cgi?id=14599=edit
Build log for binutils 2.40 on  i686

-- 
You are receiving this mail because:
You are on the CC list for the bug.


[Bug binutils/29993] objcopy --merge-notes slow for large .so with many annobin notes

2023-01-16 Thread nickc at redhat dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=29993

--- Comment #6 from Nick Clifton  ---
(In reply to Frank Ch. Eigler from comment #5)
Hi Frank,

Yes - I am afraid that the watermark protocol document is a bit out of date,
and its rules for note merging do need to be updated.

> So, as for a more efficient merging algorithm, I would explore something
> like this:

Your idea is excellent.  However before I go down that route - and probably
break building lots of packages by introducing new bugs - would you care to try
out a scratch build of the binutils which has a tweaked merge algorithm ?

   https://koji.fedoraproject.org/koji/taskinfo?taskID=96203568

I just added a variable to keep track of the last non-deleted note, so that the
backwards search could start from there, rather than the previous note.  With
this patch applied I found that merging libxul.so went down from 10.5 minutes
to 5 minutes on my local machine.  Not an order of magnitude improvement I
know, but would it be enough for you ?  

I am hesitant to rewrite the algorithm entirely because if I get it wrong I am
likely to break the building of other packages - either by corrupting the notes
so that annocheck then complains, or breaking the merge process so that the
rpms do not build or something else.

Cheers
  Nick

-- 
You are receiving this mail because:
You are on the CC list for the bug.


[Bug gas/29991] gas: MicroMIPS flag mistakenly erased after align directives

2023-01-16 Thread cvs-commit at gcc dot gnu.org
https://sourceware.org/bugzilla/show_bug.cgi?id=29991

--- Comment #7 from cvs-commit at gcc dot gnu.org  ---
The master branch has been updated by Alan Modra :

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=5999477d92aecd9df5fb0b2f04c33b987a7db40c

commit 5999477d92aecd9df5fb0b2f04c33b987a7db40c
Author: Alan Modra 
Date:   Fri Jan 13 09:39:19 2023 +1030

PR29991, MicroMIPS flag erased after align directives

PR 29991
* config/tc-mips.c (s_align): Call file_mips_check_options and
mips_mark_labels.
* testsuite/gas/mips/align-after-label.s,
* testsuite/gas/mips/mips-align-after-label.d,
* testsuite/gas/mips/micromips-align-after-label.d: New test.
* testsuite/gas/mips/mips.exp: Run it.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


[Bug binutils/30006] Failure to build binutils-2.40 on i686

2023-01-16 Thread sch...@linux-m68k.org
https://sourceware.org/bugzilla/show_bug.cgi?id=30006

--- Comment #1 from Andreas Schwab  ---
You have stripped the actual error from the build log.  Please also state how
you have configured the build.

-- 
You are receiving this mail because:
You are on the CC list for the bug.