From: Achim Gratz <Stromeko@nexgo.de>
To: binutils@sourceware.org
Subject: Re: GNU Binutils 2.40 released
Date: Sun, 15 Jan 2023 22:18:29 +0100 [thread overview]
Message-ID: <87a62j5wey.fsf@Rainer.invalid> (raw)
In-Reply-To: <87h6wtgmhy.fsf@redhat.com> (Nick Clifton via Binutils's message of "Sat, 14 Jan 2023 15:32:41 +0000")
Nick Clifton via Binutils writes:
> We are pleased to announce that version 2.40 of the GNU Binutils project
> sources have been released and are now available for download at:
Thanks.
This release is slightly broken on systems that already use texinfo 7
due to an error in the libctf configure script. Patch:
--8<---------------cut here---------------start------------->8---
--- origsrc/binutils-2.40/libctf/configure.ac
+++ src/binutils-2.40/libctf/configure.ac
@@ -184,7 +184,7 @@
# We require texinfo to be 6.3 or later, for a working synindex
# and validatemenus: otherwise we fall back to /bin/true.
if ${MAKEINFO} --version \
- | egrep 'texinfo[^0-9]*(6\.[3-9]|[7-9][0-9])' >/dev/null 2>&1; then
+ | egrep 'texinfo[^0-9]*(6\.[3-9]|[7-9]\.[0-9])' >/dev/null 2>&1; then
build_info=yes
else
build_info=
--8<---------------cut here---------------end--------------->8---
Also, it doesn't build on Cygwin (and when building the cross compilers
to MinGW64) when enabling target x86_64-pep due to doubly defined
symbols when linking ld-new (pep-dll-x86_64 defines the same symbols as
pep-dll). The following patch seems to fix that particular issue, but
is unlikely to do the right thing when other configure options are used.
--8<---------------cut here---------------start------------->8---
--- origsrc/binutils-2.40/ld/configure.tgt
+++ src/binutils-2.40/ld/configure.tgt
@@ -1051,12 +1051,12 @@
;;
x86_64-*-cygwin) targ_emul=i386pep ;
targ_extra_emuls=i386pe
- targ_extra_ofiles="deffilep.o pdb.o pep-dll.o pe-dll.o"
+ targ_extra_ofiles="deffilep.o pdb.o pe-dll.o"
test "$targ" != "$host" && LIB_PATH='${tooldir}/lib/w32api'
;;
x86_64-*-mingw*) targ_emul=i386pep ;
targ_extra_emuls=i386pe
- targ_extra_ofiles="deffilep.o pdb.o pep-dll.o pe-dll.o"
+ targ_extra_ofiles="deffilep.o pdb.o pe-dll.o"
;;
x86_64-*-gnu*) targ_emul=elf_x86_64
targ_extra_emuls="elf32_x86_64 elf_iamcu elf_i386"
--8<---------------cut here---------------end--------------->8---
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Wavetables for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables
next prev parent reply other threads:[~2023-01-15 21:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-14 15:32 Nick Clifton
2023-01-15 9:17 ` Xi Ruoyao
2023-01-16 10:58 ` Nick Clifton
2023-01-16 11:35 ` Nick Clifton
2023-01-15 21:18 ` Achim Gratz [this message]
2023-01-16 7:59 ` Jan Beulich
2023-01-16 12:51 ` ASSI
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a62j5wey.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=binutils@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).