public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bugzilla-gcc at thewrittenword dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/20366] AIX g++ -D_LARGE_FILES fails to compile #include <iostream> Date: Wed, 22 Feb 2006 23:43:00 -0000 [thread overview] Message-ID: <20060222234340.6852.qmail@sourceware.org> (raw) In-Reply-To: <bug-20366-10214@http.gcc.gnu.org/bugzilla/> ------- Comment #3 from bugzilla-gcc at thewrittenword dot com 2006-02-22 23:43 ------- Any plans to add _LARGE_FILES support to g++/libstdc++ for AIX? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20366
next parent reply other threads:[~2006-02-22 23:43 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-20366-10214@http.gcc.gnu.org/bugzilla/> 2006-02-22 23:43 ` bugzilla-gcc at thewrittenword dot com [this message] 2007-12-01 22:04 ` haubi at gentoo dot org 2007-12-19 15:58 ` haubi at gentoo dot org 2007-12-20 0:07 ` tcoleman at autowares dot com 2007-12-20 0:17 ` dsanderson at panasas dot com 2007-12-21 0:29 ` dje at gcc dot gnu dot org 2007-12-21 3:59 ` bugzilla-gcc at thewrittenword dot com 2007-12-21 14:59 ` dje at watson dot ibm dot com 2007-12-21 19:14 ` bugzilla-gcc at thewrittenword dot com 2007-12-21 23:23 ` dje at gcc dot gnu dot org 2007-12-21 23:25 ` bugzilla-gcc at thewrittenword dot com 2007-12-22 20:18 ` tcoleman at autowares dot com 2007-12-22 20:52 ` dje at watson dot ibm dot com 2007-12-31 19:29 ` peter at pogma dot com 2007-12-31 19:41 ` bugzilla-gcc at thewrittenword dot com 2008-03-03 21:12 ` bugzilla-gcc at thewrittenword dot com 2008-03-07 6:55 ` rwild at gcc dot gnu dot org 2008-04-04 5:32 ` pogma at gcc dot gnu dot org [not found] <bug-20366-4@http.gcc.gnu.org/bugzilla/> 2010-12-27 19:39 ` pogma at gcc dot gnu.org 2005-03-07 19:12 [Bug c++/20366] New: " gcc-bugzilla at gcc dot gnu dot org 2005-03-07 19:15 ` [Bug target/20366] " pinskia at gcc dot gnu dot org 2005-03-07 19:30 ` dje at gcc dot gnu dot 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=20060222234340.6852.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: linkBe 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).