Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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: Mon, 20 Oct 2003 13:22:59 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: AW: Patch for building libcrypt.a as a DLL Message-ID: <20031020112259.GF1711@cygbert.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <181645412618 DOT 20031020131546 AT familiehaase DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <181645412618.20031020131546@familiehaase.de> User-Agent: Mutt/1.4.1i On Mon, Oct 20, 2003 at 01:15:46PM +0200, Gerrit P. Haase wrote: > Hello Ralf, > > >> Libutil.a is deprecated and will not be part of future inetutils > >> releases anymore. > > > Only for cygwin or for the whole unix/linux world ? > > > > It seems that some linux based packages (as far as I know kde releated > > package) are using libutil as default, which requires additional patching. > > For this it would help, building a special import library containing the > > libutil relating symbols pointing to the cygwin dll like done with > > libpthread. > > Isn't there a confiure check which tests if the symbols in question are > available in the C library and if not whether libutil is available and > if so use this? This is the usual autotool way, e.g for iconv() (IIRC). > Isn't it possible to push these kind of changes upstream (if changes are > needed to configure)? I agree. Even our very ancient inetutils package checks the needed functions in case there's no libutil.a (see its configure.in). Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- 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/