RE: supposed missing iconv with cygwin 1.7.0

["Bobby McNulty" <snyder100 at bellsouth dot net>]

Thanks Dave.
I have libiconv from the cygwin mirrors. After configuring binutils with
disable-nls, libiconv is still reported missing during build. Since I am on
an English (US) system, I really don't need those international conversions.
Dave, it built fine here. Now onto GCC 4.3 with this knowledge (admittedly a
memory jog would have done better.) I knew this, but throughout the 11 years
of Linux and 7 with Cygwin, forgot it.
My experience goes back to the VIC 20 days with BASIC and assembly
languages.
Bobby

-----Original Message-----
From: binutils-owner@sourceware.org [mailto:binutils-owner@sourceware.org]
On Behalf Of Dave Korn
Sent: Thursday, September 27, 2007 11:29 AM
To: binutils@sourceware.org
Subject: RE: supposed missing iconv with cygwin 1.7.0

On 27 September 2007 17:01, Bobby McNulty wrote:

  Hi Bobby!

> When building binutils with cygwin 1.7.0 cvs and snapshot, make reports
that
> iconv is missing. I think it also happens with gcc.
> This was captured from cygwin's bash.
> Is this a known issue? The only solution I could come up with is
installing
> a new libiconv, but the current libibiconv is from 2006.
> This has made me hesitant about trying the new dll.
> It compiles fine under cygwin 1.5.24-2, the current dll.

  Hmm, that's odd, for two reasons:

1) it doesn't even check for iconv with the older one, let alone check and
not
find it.

2) it doesn't end with your standard 'configure failed' error message, but
with a SIGINT as if you'd hit Ctrl-C.

  Since 1.7.0 is in a state of flux, it's quite possible you've run into
some
kind of signal-handling bug with the second part there, so it could be a red
herring.  I reckon your best bet would be to see if adding "--disable-nls"
to
the configure command-line helps any.


    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....