Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Date:	Thu, 11 Jul 2002 11:26:54 -0400
From:	Christopher Faylor <cgf AT redhat DOT com>
To:	cygwin AT cygwin DOT com
Cc:	deo AT logos-m DOT ru
Subject:	Re: gcc 3.11-2 link error with stdc++
Message-ID:	<20020711152654.GB8291@redhat.com>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com, deo AT logos-m DOT ru
References:	<agjrom$pge$1 AT main DOT gmane DOT org>
Mime-Version:	1.0
In-Reply-To:	<agjrom$pge$1@main.gmane.org>
User-Agent:	Mutt/1.3.23.1i

On Thu, Jul 11, 2002 at 08:58:42PM +0900, Dylan Cuthbert wrote:
>Hi there,
>
>I have downloaded the very latest 3.11 version of gcc for cygwin.
>
>It seems any piece of code using string::replace with iterators causes a
>link error at the moment, this is the error I get:
>
> undefined reference to `
>std::basic_string<char, std::char_traits<char>, std::allocator<char>
>>::replace(std::__normal_iterator<char*, std::basic_string<char,
>std::char_traits<char>, std::allocator<char> > >,
>std::__normal_iterator<char*, std::basic_string<char,
>std::char_traits<char>, std::allocator<char> > >, unsigned, char)'
>collect2: ld returned 1 exit status
>
>If this isn't a cygwin-related problem I'll post to the gcc group, however,
>I haven't seen mention of this kind of problem on there.

Sorry.  I can't offer any insight, especially without a test case, but probably
not even then.

Maybe Egor might have an idea.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -