From issues-return-2539-apmail-stdcxx-issues-archive=stdcxx.apache.org@stdcxx.apache.org Sat Feb 14 22:38:28 2009 Return-Path: Delivered-To: apmail-stdcxx-issues-archive@minotaur.apache.org Received: (qmail 52102 invoked from network); 14 Feb 2009 22:38:28 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 14 Feb 2009 22:38:28 -0000 Received: (qmail 40752 invoked by uid 500); 14 Feb 2009 22:38:28 -0000 Delivered-To: apmail-stdcxx-issues-archive@stdcxx.apache.org Received: (qmail 40724 invoked by uid 500); 14 Feb 2009 22:38:28 -0000 Mailing-List: contact issues-help@stdcxx.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@stdcxx.apache.org Delivered-To: mailing list issues@stdcxx.apache.org Received: (qmail 40713 invoked by uid 99); 14 Feb 2009 22:38:28 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 14 Feb 2009 14:38:28 -0800 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 14 Feb 2009 22:38:20 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id C1BAB234C48B for ; Sat, 14 Feb 2009 14:37:59 -0800 (PST) Message-ID: <1120457351.1234651079774.JavaMail.jira@brutus> Date: Sat, 14 Feb 2009 14:37:59 -0800 (PST) From: "Martin Sebor (JIRA)" To: issues@stdcxx.apache.org Subject: [jira] Reopened: (STDCXX-1029) [gcc 4.3.1] build error: _RWSTD_SEEK_SET, CUR, END not defined in bitset.cpp In-Reply-To: <366116769.1231104584227.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/STDCXX-1029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Sebor reopened STDCXX-1029: ---------------------------------- As indicated in gcc bug #[37405 | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37405] the compiler error is due to an incorrect gcc installation. Reopening to revert committed changes. > [gcc 4.3.1] build error: _RWSTD_SEEK_SET, CUR, END not defined in bitset.cpp > ---------------------------------------------------------------------------- > > Key: STDCXX-1029 > URL: https://issues.apache.org/jira/browse/STDCXX-1029 > Project: C++ Standard Library > Issue Type: Bug > Components: Build and Installation > Affects Versions: 4.2.1 > Environment: gcc 4.3.1, Red Hat Enterprise Linux AS release 4 (Nahant Update 4) > Reporter: Martin Sebor > Assignee: Martin Sebor > Fix For: 4.2.2 > > Original Estimate: 2h > Time Spent: 1h > Remaining Estimate: 1h > > stdcxx 4.2.x fails to build with gcc 4.3.1 with the following errors: > {noformat} > gcc -c -I/amd/homes/sebor/stdcxx-4.2.1/include/ansi \ > -D_RWSTDDEBUG -pthread \ > -I/amd/homes/sebor/stdcxx-4.2.1/include \ > -I/build/sebor/stdcxx-4.2.1-gcc-4.3.1-15D/include \ > -pedantic -nostdinc++ -g -W -Wall -Wcast-qual -Winline -Wshadow -Wwrite-strings -Wno-long-long -Wcast-align -fPIC \ > /amd/homes/sebor/stdcxx-4.2.1/src/bitset.cpp > In file included from /amd/homes/sebor/stdcxx-4.2.1/include/string:39, > from /amd/homes/sebor/stdcxx-4.2.1/include/bitset:34, > from /amd/homes/sebor/stdcxx-4.2.1/src/bitset.cpp:31: > /amd/homes/sebor/stdcxx-4.2.1/include/rw/_iosfwd.h:176: error: '_RWSTD_SEEK_SET' was not declared in this scope > /amd/homes/sebor/stdcxx-4.2.1/include/rw/_iosfwd.h:177: error: '_RWSTD_SEEK_CUR' was not declared in this scope > /amd/homes/sebor/stdcxx-4.2.1/include/rw/_iosfwd.h:178: error: '_RWSTD_SEEK_END' was not declared in this scope > make[2]: *** [bitset.o] Error 1 > make[2]: Leaving directory `/build/sebor/stdcxx-4.2.1-gcc-4.3.1-15D/lib' > make[1]: *** [lib] Error 2 > make[1]: Leaving directory `/build/sebor/stdcxx-4.2.1-gcc-4.3.1-15D' > make: *** [libstd] Error 2 > {noformat} -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.