Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Date: Thu, 27 Jan 2005 20:09:56 -0500
From: Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Compiling GNU sed
Message-ID: <20050128010956.GF3961@trixie.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
References: <6 DOT 1 DOT 2 DOT 0 DOT 1 DOT 20050127235728 DOT 026e9008 AT pop DOT ntlworld DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <6.1.2.0.1.20050127235728.026e9008@pop.ntlworld.com>
User-Agent: Mutt/1.4.1i

On Fri, Jan 28, 2005 at 12:13:53AM +0000, www.mail wrote:
>I have just updated my Cygwin, and I'm trying to compile the latest GNU
>sed (4.1.3) with the command:
>
>CC="gcc -mno-cygwin" ./configure --disable-nls
>
>It compiles OK.  But when I run make, I get several errors stating
>"undefined reference to `_wcrtomb'".
>
>If I compile it without the -mno-cygwin option, make produces the
>executable successfully.
>
>During compilation without -mno-cygwin, there is a message:
>
>checking for wcrtomb...  yes
>
>But during compilation with -mno-cygwin, the corresponding message is:
>
>checking for wcrtomb...  no
>
>Please could someone tell me my I'm getting ths error?  All I know
>about wcrtomb is that it's included in wchar.h.  I don't have all
>Cygwin packages, but the ones that I do have are the latest versions.
>
>Any help would be much appreciated.

Either don't use -mno-cygwin, or don't expect configure to be able to
figure out that _wcrtomb doesn't exist when running in a cygwin
environment when it actually does exist in a cygwin environment.

Or, perhaps you need to talk to the people at the mingw project:
http://www.mingw.org/ .

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/