From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] common/filestuff.c: No sockets on DJGPP.
Date: Wed, 22 May 2013 02:50:00 -0000 [thread overview]
Message-ID: <83txlvu3ss.fsf@gnu.org> (raw)
In-Reply-To: <20130521203302.23510.45135.stgit@brno.lan>
> From: Pedro Alves <palves@redhat.com>
> Date: Tue, 21 May 2013 21:33:02 +0100
>
> Building gdb with --host=i586-pc-msdosdjgpp ends up with:
>
> i586-pc-msdosdjgpp-gcc -g -O2 -I../../src/gdb/config/djgpp -I. -I../../src/gdb -I../../src/gdb/common -I../../src/gdb/config -DLOCALEDIR="\"/usr/local/share/locale\"" -DHAVE_CONFIG_H -I../../src/gdb/../include/opcode -I../../src/gdb/../opcodes/.. -I../../src/gdb/../readline/.. -I../bfd -I../../src/gdb/../bfd -I../../src/gdb/../include -I../libdecnumber -I../../src/gdb/../libdecnumber -I./../intl -I../../src/gdb/gnulib/import -Ibuild-gnulib/import -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 -Werror -c -o filestuff.o -MT filestuff.o -MMD -MP -MF .deps/filestuff.Tpo ../../src/gdb/common/filestuff.c
> ../../src/gdb/common/filestuff.c:38:24: fatal error: sys/socket.h: No such file or directory
>
> There are no sockets on djgpp. This #ifdef's out the bits in the file
> that use sockets, depending on whether winsock or sys/socket.h is
> available.
This is fine with me, thanks.
> As alternative approach, given ser-tcp.c, ser-pipe.c, etc. are split
> into separate files, and which to use is selected by configure.ac:
Looks like overhead to me, but if others prefer this, I can go with
this as well.
Thanks.
next prev parent reply other threads:[~2013-05-22 2:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-21 20:33 Pedro Alves
2013-05-22 2:50 ` Eli Zaretskii [this message]
2013-05-23 18:25 ` Tom Tromey
2013-05-23 18:37 ` Pedro Alves
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=83txlvu3ss.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=palves@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