public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: paulf@sea.checkpoint.com
To: gcc-gnats@gcc.gnu.org
Cc: marka@sea.checkpoint.com
Subject: libstdc++/5627: cstdio header failes to compile on sparc-sun-solaris2.7 with _FILE_OFFSET_BITS == 64
Date: Thu, 07 Feb 2002 13:16:00 -0000	[thread overview]
Message-ID: <20020207210631.1345.qmail@sources.redhat.com> (raw)


>Number:         5627
>Category:       libstdc++
>Synopsis:       cstdio header failes to compile on sparc-sun-solaris2.7 with _FILE_OFFSET_BITS == 64
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          rejects-legal
>Submitter-Id:   net
>Arrival-Date:   Thu Feb 07 13:16:01 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     Paul Forgey
>Release:        gcc version 2.95.2 19991024 (release)
>Organization:
>Environment:
sparc-sun-solaris2.7
>Description:
when _FILE_OFFSET_BITS is set to `64', the system's stdio.h will actually make the symbols fopen, freopen, tmpfile, fgetpos and fsetpos unavailable at all, even as normal function definitions, if they are #undef'd.  This causes the later part of the header file pulling these into namespace std to fail with complaints these symbols are undefined.
>How-To-Repeat:
attempt to build Berkeley db-3.3.11 after passing --enable-cxx to the configure script.
>Fix:
This is probably not the best fix, but it got me past the issue.  Somebody who knows their way around the solaris headers better than I do could probably come up with a more "real" fix:

in $prefix/include/g++-v3/bits/std_cstdio.h, remove the #undef macros for these symbols, and add the following code at line 43 (right after #include <stdio.h>):

// The following functions _can not_ be #undef'd if we are using 64
// bit file pointers
#if ! (defined (sun) && !defined (_LP64) && _FILE_OFFSET_BITS == 64)

#undef fopen
#undef freopen
#undef tmpfile
#undef fgetpos
#undef fsetpos

#endif // whew

>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2002-02-07 21:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-07 13:16 paulf [this message]
2002-05-03 18:17 bkoz
2003-05-10 10:10 Dara Hazeghi
2003-05-10 18:16 Dara Hazeghi

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=20020207210631.1345.qmail@sources.redhat.com \
    --to=paulf@sea.checkpoint.com \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=marka@sea.checkpoint.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: 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).