From: Sim Tov <smntov@gmail.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: binutils@sourceware.org
Subject: Re: Cross-compilation related bug
Date: Thu, 21 Jul 2022 21:40:35 +0300 [thread overview]
Message-ID: <CA+X_a+yk-pjTH=SKnZPAn2usCaS9PNquBnApAvbCQO-Yki13YQ@mail.gmail.com> (raw)
In-Reply-To: <CA+X_a+xShDuFZRdsGYK8UQkcEjJ31XL+x+2XxcxmCPJHaG_4bA@mail.gmail.com>
If you don't have a Windows machine to install MSYS2:
https://www.msys2.org/
We would be more than happy to follow your instructions in a live
session (e.g. via IRC, etc) and provide you
with the outputs, logs, screenshots and screen sharing...
Thank you!
On Thu, Jul 21, 2022 at 5:33 PM Sim Tov <smntov@gmail.com> wrote:
>
> That's the problem - this bug doesn't occur on a regular Linux...
>
> But maybe one, who is familiar with the internals of binutils, can
> guess what is wrong, being provided with the file names and lines:
>
> binutils-gdb/bfd/cofflink.c:2279
> binutils-gdb/bfd/coff-x86_64.c:696
>
> https://sourceware.org/bugzilla/show_bug.cgi?id=29389
>
> Thank you!
>
> On Thu, Jul 21, 2022 at 5:08 PM Jan Beulich <jbeulich@suse.com> wrote:
> >
> > On 21.07.2022 15:49, Sim Tov via Binutils wrote:
> > > It would be great, if somebody from the developers could take a look
> > > on this cross-compilation related bug:
> > >
> > > https://sourceware.org/bugzilla/show_bug.cgi?id=29389
> > >
> > > It affects quite a few people and blocks us from advancing...
> >
> > I guess it would help quite a bit if a simpler repro was made
> > available. I don't think what is provided in the bugzilla entry
> > is quite suitable for anyone not familiar with MingW.
> >
> > Jan
next prev parent reply other threads:[~2022-07-21 18:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-21 13:49 Sim Tov
2022-07-21 14:08 ` Jan Beulich
2022-07-21 14:33 ` Sim Tov
2022-07-21 18:40 ` Sim Tov [this message]
2022-07-22 3:05 ` Alan Modra
2022-07-22 12:29 ` Sim Tov
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='CA+X_a+yk-pjTH=SKnZPAn2usCaS9PNquBnApAvbCQO-Yki13YQ@mail.gmail.com' \
--to=smntov@gmail.com \
--cc=binutils@sourceware.org \
--cc=jbeulich@suse.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).