From: Anton Kolesov <Anton.Kolesov@synopsys.com>
To: Pedro Alves <palves@redhat.com>, Yao Qi <qiyaoltc@gmail.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
Francois Bedard <Francois.Bedard@synopsys.com>,
Sergio Durigan Junior <sergiodj@redhat.com>
Subject: RE: [PATCH] Import setenv and unsetenv from gnulib
Date: Wed, 05 Jul 2017 10:32:00 -0000 [thread overview]
Message-ID: <39A54937CC95F24AA2F794E2D2B66B135876E65F@DE02WEMBXB.internal.synopsys.com> (raw)
In-Reply-To: <e81c33b7-1800-3285-5b76-91be8b064714@redhat.com>
>
> On 07/04/2017 07:06 PM, Anton Kolesov wrote:
> > Selftests pass on x86_64-linux. On Windows with this patch there is a
> > failure in iconv sefltest, which seems unrelated (was present even
> > when I've tried to use putenv directly instead of importing gnulib module).
>
> I take it you meant the s/iconv/gdb_environ/ selftest.
> Can you show what does "maint selftest" say?
z:\tmp>gdb.exe -ex "mt selftest" -batch
Self test failed: Converting character sets: No error.
Ran 11 unit tests, 1 failed
Grepping for "Converting character sets" points to iconv_wrapper in charset.c.
I'm cross-building with Mingw GCC 4.9.2 from EPEL repositories for CentOS/RHEL 6.
Maybe some problems with this toolchain or my windows environment.
Anton
>
> Thanks,
> Pedro Alves
next prev parent reply other threads:[~2017-07-05 10:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-03 10:04 [PATCH] Fix build breakage on MinGW due to missing setenv Anton Kolesov
2017-07-03 11:21 ` Yao Qi
2017-07-03 15:26 ` Sergio Durigan Junior
2017-07-03 16:27 ` [PATCH] Import setenv and unsetenv from gnulib Anton Kolesov
2017-07-03 19:35 ` Sergio Durigan Junior
2017-07-04 10:20 ` Yao Qi
2017-07-04 18:06 ` Anton Kolesov
[not found] ` <8737ac6j91.fsf@redhat.com>
2017-07-05 9:50 ` Anton Kolesov
2017-07-06 15:34 ` Sergio Durigan Junior
2017-07-05 9:56 ` Pedro Alves
2017-07-05 10:32 ` Anton Kolesov [this message]
2017-07-07 8:24 ` Yao Qi
2017-07-07 9:35 ` Anton Kolesov
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=39A54937CC95F24AA2F794E2D2B66B135876E65F@DE02WEMBXB.internal.synopsys.com \
--to=anton.kolesov@synopsys.com \
--cc=Francois.Bedard@synopsys.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=qiyaoltc@gmail.com \
--cc=sergiodj@redhat.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