public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "lsatenstein at yahoo dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/13047] On 32 bit system (UBUNTU Natty) Cannot open a file of size 5GB Date: Sun, 31 Jul 2011 23:24:00 -0000 [thread overview] Message-ID: <bug-13047-131-h4NorSycCb@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-13047-131@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=13047 Leslie Satenstein <lsatenstein at yahoo dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID | --- Comment #3 from Leslie Satenstein <lsatenstein at yahoo dot com> 2011-07-31 23:24:23 UTC --- Here is my come-back. Since one can add a #define to allow using buffered IO (fread, fwrite, etc) for files in excess of 2 gigabytes. then this define should be permanent within stdio.h . I wanted to read an ISO DVD and could not. I would refer the owner of this maintenance problem to the actual libc.pdf file section 4.17, which makes no mention of the #define. (However in respoonse to Andreas Jaeger, personal reply (which I appreciate receiving and for which I thank him), using the search of the libc.PDF I did find a chapter about large file support. Something is wrong when today a large file is one measured in petabytes. Please redirect this topic and this bug to the documentation project and of course to a steering committee to update the stream IO functionality to handle very large files, or to state that in the libc.pdf fopen() document, to refer to the large file section. I lost quite a few hours of digging to independently discoover the #define that enables large file support. I would also ask why large file support is turned on for 64 bit linux? Had 64 bit linux the same constraint, I would have not been concerned. (I was porting code from 64bit to 32bit), for older systems. Thank you again Andreas, for the prompt reply. -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next prev parent reply other threads:[~2011-07-31 23:24 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-07-31 1:11 [Bug libc/13047] New: " lsatenstein at yahoo dot com 2011-07-31 1:12 ` [Bug libc/13047] " lsatenstein at yahoo dot com 2011-07-31 18:58 ` aj at suse dot de 2011-07-31 23:24 ` lsatenstein at yahoo dot com [this message] 2011-08-01 7:22 ` aj at suse dot de 2011-08-07 17:57 ` bugdal at aerifal dot cx 2012-05-14 4:22 ` bugdal at aerifal dot cx 2012-05-14 10:55 ` joseph at codesourcery dot com 2014-06-13 14:36 ` [Bug libc/13047] Make 64-bit off_t the default on i386 and others fweimer at redhat dot com 2014-06-13 14:37 ` fweimer at redhat dot com
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=bug-13047-131-h4NorSycCb@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sources.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: 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).