From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28536 invoked by alias); 21 Apr 2011 00:03:13 -0000 Received: (qmail 28528 invoked by uid 22791); 21 Apr 2011 00:03:12 -0000 X-SWARE-Spam-Status: No, hits=-2.8 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from localhost (HELO gcc.gnu.org) (127.0.0.1) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 21 Apr 2011 00:02:59 +0000 From: "paolo.carlini at oracle dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/36231] ostream includes unistd.h outside namespace std, polluting X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: paolo.carlini at oracle dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Date: Thu, 21 Apr 2011 00:03:00 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2011-04/txt/msg02222.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36231 --- Comment #18 from Paolo Carlini 2011-04-21 00:02:02 UTC --- Thanks Ralf, I didn't know AC_CHECK_SIZEOF and AC_CHECK_ALIGNOF even existed, in similar situations probably I would have dumbly re-invented both basing on AC_COMPUTE_INT ;) Otherwise, about the issue which prompted my question, seems still tough, because actually gthr.h is included by a few different headers, also in locale, not just via the path explained in the PR. Frankly, I don't know how much we can get into this within the existing ABI... To Ivan I have to remember that we don't control in general the underlying .h headers, it's the usual question, how far we can go without assuming much about the C headers and of course without changing the headers themselves...