public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: mfbrown1@students.uiuc.edu To: gcc-gnats@gcc.gnu.org Subject: preprocessor/6020: _FILE_OFFSET_BITS token error on HPUX 11.0 Date: Wed, 20 Mar 2002 10:16:00 -0000 [thread overview] Message-ID: <20020320181439.26086.qmail@sources.redhat.com> (raw) >Number: 6020 >Category: preprocessor >Synopsis: _FILE_OFFSET_BITS token error on HPUX 11.0 >Confidential: no >Severity: non-critical >Priority: low >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Wed Mar 20 10:16:09 PST 2002 >Closed-Date: >Last-Modified: >Originator: Michael Brown >Release: 3.0.4 >Organization: >Environment: hpux 11.0 hppa2.0w-hp-hpux11.00 >Description: g++ has problems with system headers on HPUX when trying to compile code where _FILE_OFFSET_BITS has been defined. Compiler exits with errors. >How-To-Repeat: g++ hello.C >Fix: do not use "#define _FILE_OFFSET_BITS 64" define statement. >Release-Note: >Audit-Trail: >Unformatted: ----gnatsweb-attachment---- Content-Type: text/plain; name="hello.C" Content-Disposition: inline; filename="hello.C" #define _FILE_OFFSET_BITS 64 #include <iostream.h> int main() { cout << "Hello, World!" << endl; return 0; }
reply other threads:[~2002-03-20 18:16 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20020320181439.26086.qmail@sources.redhat.com \ --to=mfbrown1@students.uiuc.edu \ --cc=gcc-gnats@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).