public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "paolo dot carlini at oracle dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/43738] basic_file_stdio.cc uses ioctl on a fd, but not available on mingw32
Date: Thu, 15 Apr 2010 16:04:00 -0000 [thread overview]
Message-ID: <20100415160413.17764.qmail@sourceware.org> (raw)
In-Reply-To: <bug-43738-10752@http.gcc.gnu.org/bugzilla/>
------- Comment #9 from paolo dot carlini at oracle dot com 2010-04-15 16:04 -------
Agreed, if ioctlsocket can't really replace ioctl, let's just explicitly #if
out the affected targets for now. We can still improve it later.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43738
next prev parent reply other threads:[~2010-04-15 16:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-12 23:33 [Bug libstdc++/43738] New: " sherpya at netfarm dot it
2010-04-12 23:34 ` [Bug libstdc++/43738] " pinskia at gcc dot gnu dot org
2010-04-12 23:36 ` sherpya at netfarm dot it
2010-04-15 0:55 ` paolo dot carlini at oracle dot com
2010-04-15 1:03 ` davek at gcc dot gnu dot org
2010-04-15 1:17 ` davek at gcc dot gnu dot org
2010-04-15 3:10 ` paolo dot carlini at oracle dot com
2010-04-15 7:54 ` dannysmith at users dot sourceforge dot net
2010-04-15 10:04 ` sherpya at netfarm dot it
2010-04-15 10:13 ` davek at gcc dot gnu dot org
2010-04-15 16:04 ` paolo dot carlini at oracle dot com [this message]
2010-04-20 21:27 ` paolo dot carlini at oracle dot com
2010-04-21 2:17 ` davek at gcc dot gnu dot org
2010-04-21 3:36 ` paolo dot carlini at oracle dot com
2010-04-22 15:32 ` sherpya at netfarm dot it
2010-08-13 18:00 ` paolo dot carlini at oracle dot com
[not found] <bug-43738-4@http.gcc.gnu.org/bugzilla/>
2010-12-02 13:15 ` ktietz at gcc dot gnu.org
2010-12-02 13:17 ` ktietz at gcc dot gnu.org
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=20100415160413.17764.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).