From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18290 invoked by alias); 22 Feb 2003 00:46:01 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 18268 invoked by uid 71); 22 Feb 2003 00:46:00 -0000 Date: Sat, 22 Feb 2003 00:46:00 -0000 Message-ID: <20030222004600.18267.qmail@sources.redhat.com> To: geoffk@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: Geoffrey Keating Subject: Re: other/9274: [pch] cannot create libstdc++-v3 pch Reply-To: Geoffrey Keating X-SW-Source: 2003-02/txt/msg01093.txt.bz2 List-Id: The following reply was made to PR other/9274; it has been noted by GNATS. From: Geoffrey Keating To: bkoz@redhat.com, gcc-gnats@gcc.gnu.org, geoffk@geoffk.org, geoffk@gcc.gnu.org, gcc-bugs@gcc.gnu.org, pcarlini@unitus.it Cc: Subject: Re: other/9274: [pch] cannot create libstdc++-v3 pch Date: Fri, 21 Feb 2003 16:42:01 -0800 I've confirmed that this problem still exists, at least partly. On Darwin, test1.cc prints: ld: Undefined symbols: std::basic_ostream >::operator<<(std::basic_ostream >& (*)(std::basic_ostream >&)) and test2.cc prints: ld: Undefined symbols: std::basic_string, std::allocator >::basic_string[in-charge](char const*, std::allocator const&) std::basic_string, std::allocator >::~basic_string [in-charge]() std::allocator::allocator[in-charge]() std::allocator::~allocator [in-charge]() std::basic_ostream >& std::operator<< , std::allocator >(std::basic_ostream >&, std::basic_string, std::allocator > const&) This is an improvement, but it's not quite working yet.