From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: <gdb-patches@sourceware.org>
Cc: "'Eli Zaretskii'" <eliz@gnu.org>,
"'Pedro Alves'" <pedro@codesourcery.com>
Subject: [RFA/Obvious] Fix go32v2 compilation.
Date: Tue, 12 Oct 2010 15:01:00 -0000 [thread overview]
Message-ID: <002401cb6a1e$4eaf5e30$ec0e1a90$@muller@ics-cnrs.unistra.fr> (raw)
Go32v2 native target doesn't compile anymore...
since a patch by Pedro dating back 2010-08-20 :(
Which sadly means that not many persons currently still try to use
current CVS tree for go32v2...
I almost checked this in as obvious, but
I didn't really get if this function was necessary or not.
Pedro, is setting this function to NULL enough to
maintain old functionality for DJGPP
or should a dos specific function be implemented?
Pierre Muller
Pascal language support maintainer for GDB
ChangeLog entry:
2010-10-12 Pierre Muller <muller@ics.u-strasbg.fr>
* ser-go32.c (struct dos_ops) Add missing fdopen field.
Index: ser-go32.c
===================================================================
RCS file: /cvs/src/src/gdb/ser-go32.c,v
retrieving revision 1.24
diff -u -p -r1.24 ser-go32.c
--- ser-go32.c 20 Aug 2010 18:49:20 -0000 1.24
+++ ser-go32.c 12 Oct 2010 14:54:53 -0000
@@ -843,6 +843,7 @@ static struct serial_ops dos_ops =
0,
dos_open,
dos_close,
+ NULL, /* fdopen, not implemented */
dos_readchar,
dos_write,
dos_noop, /* flush output */
next reply other threads:[~2010-10-12 15:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-12 15:01 Pierre Muller [this message]
2010-10-12 15:27 ` Pedro Alves
2010-10-12 15:33 ` Eli Zaretskii
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='002401cb6a1e$4eaf5e30$ec0e1a90$@muller@ics-cnrs.unistra.fr' \
--to=pierre.muller@ics-cnrs.unistra.fr \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.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