public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ljrittle at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/24012] [3.4/4.0/4.1 regression] #define _POSIX_C_SOURCE breaks #include <iostream>
Date: Thu, 22 Sep 2005 19:21:00 -0000	[thread overview]
Message-ID: <20050922192044.31075.qmail@sourceware.org> (raw)
In-Reply-To: <20050922151550.24012.gerald@pfeifer.com>


------- Additional Comments From ljrittle at gcc dot gnu dot org  2005-09-22 19:20 -------
The better way to fix this IMHO is to mirror how we fixed other conditionally
missing symbols. Add a _DYNAMIC hook, add the support guards in various places
where the HAVE_X guards exist, add a correctly written define in os_defines.h to
describe the OS-level macro used to key the visibility of the "standard"
function or other symbol.  See the current FreeBSD os_defines.h for some examples.

In my further opinion, this is merely a QoI issue (granted, annoying): The user
defining a macro in implementor space may get this type of result.

Regards,
Loren

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|                            |1
   Last reconfirmed|0000-00-00 00:00:00         |2005-09-22 19:20:40
               date|                            |


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24012


  parent reply	other threads:[~2005-09-22 19:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-22 15:16 [Bug libstdc++/24012] New: [3.4,4.0,4,1 " gerald at pfeifer dot com
2005-09-22 15:20 ` [Bug libstdc++/24012] [3.4/4.0/4.1 " schwab at suse dot de
2005-09-22 15:21 ` [Bug target/24012] " pinskia at gcc dot gnu dot org
2005-09-22 15:38 ` pinskia at gcc dot gnu dot org
2005-09-22 15:50 ` gerald at pfeifer dot com
2005-09-22 19:21 ` ljrittle at gcc dot gnu dot org [this message]
2005-09-24 16:34 ` gerald at pfeifer dot com
     [not found] <bug-24012-231@http.gcc.gnu.org/bugzilla/>
2005-10-30 23:22 ` pinskia 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=20050922192044.31075.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: 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).