From: Yao Qi <yao@codesourcery.com>
To: asmwarrior <asmwarrior@gmail.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [mingw CVS HEAD] build error as there is no sys/socket.h under MinGW
Date: Tue, 23 Apr 2013 15:49:00 -0000 [thread overview]
Message-ID: <5175E0CE.6050509@codesourcery.com> (raw)
In-Reply-To: <5175D5A2.3050604@gmail.com>
On 04/23/2013 08:28 AM, asmwarrior wrote:
> I just get a build error on CVS HEAD:
>
> mingw32-gcc -O0 -g -D__USE_MINGW_ACCESS -I. -I../../gdb/gdb -I../../gdb/gdb/common -I../../gdb/gdb/config -DLOCALEDIR="\"/mingw/share/locale\"" -DHAVE_CONFIG_H -I../../gdb/gdb/../include/opcode -I../../gdb/gdb/../opcodes/.. -I../../gdb/gdb/../readline/.. -I../bfd -I../../gdb/gdb/../bfd -I../../gdb/gdb/../include -I../libdecnumber -I../../gdb/gdb/../libdecnumber -I../../gdb/gdb/gnulib/import -Ibuild-gnulib/import -IE:/code/python27/include -IE:/code/python27/include -Wall -Wdeclaration-after-statement -Wpointer-arith -Wformat-nonliteral -Wpointer-sign -Wno-unused -Wunused-value -Wunused-function -Wno-switch -Wno-char-subscripts -Wmissing-prototypes -Wdeclaration-after-statement -Wempty-body -Wno-format -Werror -c -o filestuff.o -MT filestuff.o -MMD -MP -MF .deps/filestuff.Tpo ../../gdb/gdb/common/filestuff.c
> ../../gdb/gdb/common/filestuff.c:31:24: fatal error: sys/socket.h: No such file or directory
I can reproduce this build failure with my mingw32 gcc as well. It is
caused by recent committed patch "close-on-exec internal file
descriptors". For the reference sake, I've replied the failure in that
thread http://sourceware.org/ml/gdb-patches/2013-04/msg00683.html.
--
Yao (é½å°§)
next prev parent reply other threads:[~2013-04-23 1:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-23 13:54 asmwarrior
2013-04-23 15:49 ` Yao Qi [this message]
2013-04-24 14:31 ` asmwarrior
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=5175E0CE.6050509@codesourcery.com \
--to=yao@codesourcery.com \
--cc=asmwarrior@gmail.com \
--cc=gdb-patches@sourceware.org \
/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