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:	Mon, 20 Oct 2003 13:15:46 +0200
From:	"Gerrit P. Haase" <freeweb AT nyckelpiga DOT de>
Reply-To:	"Gerrit P. Haase" <freeweb AT nyckelpiga DOT de>
Organization:	Esse keine toten Tiere
X-Priority:	3 (Normal)
Message-ID:	<181645412618.20031020131546@familiehaase.de>
To:	cygwin AT cygwin DOT com
Subject:	Re: AW: Patch for building libcrypt.a as a DLL
In-Reply-To:	<JGEMLHPCGMNLEIGOCPMGOEFKIGAA.Ralf.Habacker@freenet.de>
References:	<JGEMLHPCGMNLEIGOCPMGOEFKIGAA DOT Ralf DOT Habacker AT freenet DOT de>
MIME-Version:	1.0

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)?


Gerrit
-- 
=^..^=                                     http://nyckelpiga.de/donate.html


--
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/

- Raw text -