Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-ID: <3B6459BF.4010108@ece.gatech.edu> Date: Sun, 29 Jul 2001 14:45:19 -0400 From: Charles Wilson User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.2) Gecko/20010713 X-Accept-Language: en-us MIME-Version: 1.0 To: gp AT familiehaase DOT de CC: cygwin AT sources DOT redhat DOT com Subject: Re: libiconv-1.7 on cygwin-1.3.2 problems References: <3B643579 DOT 4030706 AT ece DOT gatech DOT edu> <3B647288 DOT 32411 DOT 242EE3A1 AT localhost> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Gerri > > I wonder, why no libiconv.a is generated during building libiconv, are all > the lib*.a coming with the .dll's (like libz.a) static versions of the libraries? Because libiconv is an EXPERIMENTAL port of libiconv, using EXPERIMENTAL versions of build tools. It is NOT an official port. I did NOT use the same care that I ordinarily apply when OFFICIALLY porting a package. It was just a TEST! I will NOT respond to this thread again. And I'm tempted to remove the damn thing from my website. --Chuck -- 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/