public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "peturr02 at ru dot is" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/12882] New: Large file support not complete Date: Mon, 03 Nov 2003 08:42:00 -0000 [thread overview] Message-ID: <20031103084202.12882.peturr02@ru.is> (raw) PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12882 Summary: Large file support not complete Product: gcc Version: 3.4 Status: UNCONFIRMED Severity: normal Priority: P2 Component: libstdc++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: peturr02 at ru dot is CC: gcc-bugs at gcc dot gnu dot org GCC build triplet: i686-pc-linux-gnu GCC host triplet: i686-pc-linux-gnu GCC target triplet: i686-pc-linux-gnu stdio_sync_filebuf::seekoff doesn't have large file support: virtual std::streampos seekoff(std::streamoff __off, std::ios_base::seekdir __dir, std::ios_base::openmode = std::ios_base::in | std::ios_base::out) { [...] if (!fseek(_M_file, __off, __whence)) __ret = std::streampos(std::ftell(_M_file)); return __ret; } Here, fseeko64/ftello64 should be used if available, else fseeko/ftello if available, else fseek/ftell.
next reply other threads:[~2003-11-03 8:42 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-11-03 8:42 peturr02 at ru dot is [this message] 2003-11-03 15:58 ` [Bug libstdc++/12882] " pinskia at gcc dot gnu dot org 2003-11-03 17:43 ` paolo at gcc dot gnu dot org 2003-11-03 20:35 ` paolo at gcc dot gnu dot org 2003-11-21 20:30 ` cvs-commit at gcc dot gnu dot org 2004-01-01 22:26 ` pinskia at gcc dot gnu dot org 2004-07-07 21:39 ` pcarlini at suse dot de 2004-08-18 19:28 ` pinskia at gcc dot gnu dot org 2004-08-18 19:58 ` scrimr at louisville dot stortek dot com 2004-09-21 9:06 ` cvs-commit at gcc dot gnu dot org 2004-09-21 9:31 ` pcarlini at suse dot de
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=20031103084202.12882.peturr02@ru.is \ --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).