Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: gdb-buildbot@sergiodj.net, gdb-patches@sourceware.org,
	Sergio Durigan Junior <sergiodj@redhat.com>
Subject: Re: Breakage on builder Fedora-x86_64-w64-mingw32, revision 49b000dc5686e016f05b717f18d2c8f865eb3617 [gdb-8.12-branch]
Date: Thu, 12 Jul 2018 16:21:00 -0000	[thread overview]
Message-ID: <7a005da3-801d-b730-7f7d-22955796c58a@redhat.com> (raw)
In-Reply-To: <E1fdWVq-0000mc-9L@kwanyin.sergiodj.net>

On 07/12/2018 08:59 AM, gdb-buildbot@sergiodj.net wrote:
> yes
> checking for memcmp... In file included from ../../binutils-gdb/intl/plural.y:35:0:
> ../../binutils-gdb/intl/plural-exp.h:102:23: error: conflicting types for 'libintl_gettextparse'
>  # define PLURAL_PARSE libintl_gettextparse
>                        ^

This is completely unrelated to the pointed commit: 

	GDB: Work around D;PID handling bug in older GDBservers (PR gdb/23377)
	49b000dc5686e016f05b717f18d2c8f865eb3617

Looking at the builder's build logs, I see several prior builds failing
in the same way.

Sergio, while looking at the builder's log, I noticed that the build
just before the one in this mail, this one here:

  https://gdb-build.sergiodj.net/builders/Fedora-x86_64-w64-mingw32/builds/2158

fails with:

../../binutils-gdb/gdb/ser-tcp.c: In function 'int try_connect(const addrinfo*, unsigned int*)':
../../binutils-gdb/gdb/ser-tcp.c:176:25: error: invalid conversion from 'int*' to 'u_long* {aka long unsigned int*}' [-fpermissive]
   ioctl (sock, FIONBIO, &ioarg);
                         ^~~~~~
In file included from ../../binutils-gdb/gdb/serial.h:23:0,
                 from ../../binutils-gdb/gdb/ser-tcp.c:21:
/usr/x86_64-w64-mingw32/sys-root/mingw/include/winsock2.h:977:34: note:   initializing argument 3 of 'int ioctlsocket(SOCKET, long int, u_long*)'
   WINSOCK_API_LINKAGE int WSAAPI ioctlsocket(SOCKET s,__LONG32 cmd,u_long *argp);
                                  ^~~~~~~~~~~
make[2]: *** [Makefile:1610: ser-tcp.o] Error 1

Thanks,
Pedro Alves


  reply	other threads:[~2018-07-12 16:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-12  7:59 Oh dear. I regret to inform you that commit 49b000dc5686e016f05b717f18d2c8f865eb3617 might be unfortunate [gdb-8.12-branch] gdb-buildbot
2018-07-12  7:59 ` Breakage on builder Fedora-x86_64-w64-mingw32, revision 49b000dc5686e016f05b717f18d2c8f865eb3617 [gdb-8.12-branch] gdb-buildbot
2018-07-12 16:21   ` Pedro Alves [this message]
2018-07-12 16:53     ` Sergio Durigan Junior
2018-07-13 10:55       ` Wiederhake, Tim
2018-07-13 11:16         ` Pedro Alves
2018-07-13 11:21           ` Pedro Alves
2018-07-20 20:40             ` Joseph Myers

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=7a005da3-801d-b730-7f7d-22955796c58a@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-buildbot@sergiodj.net \
    --cc=gdb-patches@sourceware.org \
    --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