From: Iain Buclaw <ibuclaw@gdcproject.org>
To: Luis Machado <lgustavo@codesourcery.com>
Cc: Joel Brobecker <brobecker@adacore.com>,
gdb-patches@sourceware.org, keiths@redhat.com,
Jan Kratochvil <jan.kratochvil@redhat.com>,
yunlian@google.com
Subject: Re: GDB 7.10 release 2015-07-17 status update?
Date: Mon, 20 Jul 2015 10:13:00 -0000 [thread overview]
Message-ID: <CABOHX+dZ-MnG=EjV-jNHAws=ODV_bDv_BiwaU_7KTbSbHA4o4Q@mail.gmail.com> (raw)
In-Reply-To: <55A94B87.5060901@codesourcery.com>
On 17 July 2015 at 20:37, Luis Machado <lgustavo@codesourcery.com> wrote:
> On 07/17/2015 03:32 PM, Joel Brobecker wrote:
>>>
>>> Do we consider the fact that mingw32 (and maybe other non-GNU) builds
>>> have
>>> been broken since this libiberty sync a blocker/critical issue?
>>>
>>> https://sourceware.org/ml/gdb-patches/2015-06/msg00405.html
>>>
>>> Last we heard of it was here...
>>>
>>> https://sourceware.org/ml/gdb-patches/2015-06/msg00654.html
>>>
>>> But we received no word from Yunlian Jiang yet.
>>>
>>> Maybe it should be added to the wiki too?
>>
>>
>> It's strange, it builds fine for me on Windows/MinGW - but perhaps
>> the problem doesn't happen if you use MinGW64, which is what I think
>> my compiler provides.
>>
>> But, back to your question, very definitely. If we can't even build
>> on Windows, we should at least decide what to do next. I haven't seen
>> the error; do you happen to have a link handy? Do you happen to have
>> a link?
>>
>
> Jan-Benedict posted one example here:
>
> https://sourceware.org/ml/gdb-patches/2015-06/msg00650.html
>
> I see something similar related to the implicit declaration of asprintf.
I know that Pedro suggested fixing up bfd's configure.ac, has this
been tried out?
https://sourceware.org/ml/gdb-patches/2015-06/msg00654.html
I can send in a patch, but admittedly I'll be making the change blind.
next prev parent reply other threads:[~2015-07-20 10:13 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-17 17:53 Joel Brobecker
2015-07-17 18:14 ` Luis Machado
2015-07-17 18:32 ` Joel Brobecker
2015-07-17 18:38 ` Luis Machado
2015-07-17 19:06 ` Eli Zaretskii
2015-07-17 20:48 ` Joel Brobecker
2015-07-17 20:57 ` Luis Machado
2015-07-20 10:13 ` Iain Buclaw [this message]
2015-07-21 17:16 ` Joel Brobecker
2015-07-17 19:04 ` Eli Zaretskii
2015-07-17 19:03 ` Eli Zaretskii
2015-07-24 9:26 ` Pedro Alves
2015-07-24 14:31 ` Iain Buclaw
2015-07-24 14:37 ` Pedro Alves
2015-07-17 18:25 ` Keith Seitz
2015-07-17 18:28 ` Jan Kratochvil
2015-07-17 18:35 ` Joel Brobecker
2015-07-17 20:15 ` Simon Marchi
2015-07-17 20:57 ` Joel Brobecker
2015-07-17 21:00 ` Simon Marchi
2015-07-17 20:24 ` Sergio Durigan Junior
2015-07-20 10:06 ` Yao Qi
2015-07-21 17:11 ` Joel Brobecker
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='CABOHX+dZ-MnG=EjV-jNHAws=ODV_bDv_BiwaU_7KTbSbHA4o4Q@mail.gmail.com' \
--to=ibuclaw@gdcproject.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=keiths@redhat.com \
--cc=lgustavo@codesourcery.com \
--cc=yunlian@google.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