From: Jan Nijtmans <jan.nijtmans@gmail.com>
To: cygwin@cygwin.com
Subject: Problem in mingw64-i686-binutils [Was: Updated: binutils-2.34+1git.de9c1b7cfe-1 (x86/x86_64)]
Date: Mon, 6 Apr 2020 12:07:46 +0200 [thread overview]
Message-ID: <CAO1jNwtsZ_2JzydqvavfbNzn_xh-noU8EXSNG_xdrH_7fdt5=Q@mail.gmail.com> (raw)
In-Reply-To: <CAO1jNwvJsgL92nOdyTMfdL8_Rj211o=T3Aro=6PouDoM_T+X7g@mail.gmail.com>
Ping.
Would it be possible to release a version of mingw64-i686-binutils with the
same patch as done for binutils-2.34+1git.de9c1b7cfe-1? I suspect
this would resolve the problem described here.
Thanks!
Jan Nijtmans
Op wo 1 apr. 2020 om 13:33 schreef Jan Nijtmans <jan.nijtmans@gmail.com>:
>
> > The following packages have been uploaded to the Cygwin distribution:
> >
> > * binutils-2.34+1git.de9c1b7cfe
> >
> > This release should fix libtool shared library builds on 32bit Cygwin.
>
> When building latest Tcl/Tk 8.6.10 on Cygwin and Win32, I noted that
> on mingw64-i686 the built executables crash immediately. Reverting
> mingw64-i686-binutils from version 2.34-1 back to version
> 2.13.1.be46fa23-1 makes the build work again.
>
> So, it looks like binutils for mingw64 (32-bit only) has the same
> problem as the Cygwin-32 version.
>
> Would it be possible to re-build mingw64-i686-binutils with
> the same patch?
>
> Regards,
> Jan Nijtmans
next prev parent reply other threads:[~2020-04-06 10:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-19 0:25 [ANNOUNCEMENT] Updated: binutils-2.34+1git.de9c1b7cfe-1 (x86/x86_64) Steven Penny
2020-03-19 5:25 ` Marco Atzeri
2020-03-19 23:18 ` Brian Inglis
2020-03-20 19:24 ` Hans-Bernhard Bröker
2020-03-21 4:55 ` Marco Atzeri
2020-03-21 6:40 ` Marco Atzeri
2020-03-22 20:19 ` Yaakov Selkowitz
2020-03-22 23:05 ` Marco Atzeri
2020-04-01 11:33 ` Jan Nijtmans
2020-04-06 10:07 ` Jan Nijtmans [this message]
2020-04-06 23:55 ` Problem in mingw64-i686-binutils [Was: Updated: binutils-2.34+1git.de9c1b7cfe-1 (x86/x86_64)] JonY
2020-04-07 0:57 ` Yaakov Selkowitz
2020-04-07 10:29 ` JonY
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='CAO1jNwtsZ_2JzydqvavfbNzn_xh-noU8EXSNG_xdrH_7fdt5=Q@mail.gmail.com' \
--to=jan.nijtmans@gmail.com \
--cc=cygwin@cygwin.com \
/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).