Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Sun, 19 Oct 2003 22:05:25 +0200 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: Patch for building libcrypt.a as a DLL Message-ID: <20031019200525.GA1711@cygbert.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <3F91AED7.2010504@cwilson.fastmail.fm> <20031019091608.GC25076@cygbert.vinschen.de> <3F92C1CB.8000707@cwilson.fastmail.fm> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3F92C1CB.8000707@cwilson.fastmail.fm> User-Agent: Mutt/1.4.1i On Sun, Oct 19, 2003 at 12:54:35PM -0400, Charles Wilson wrote: > Corinna Vinschen wrote: > > >Sure, thanks for the patch. I've changed the Makefile a bit, using > >`install -d' instead of the `if [ -d ...' expressions and adding the > >installation of a crypt.README file. > > > >Just one question: Does an additional libcrypt.la file make sense? > > Meh. It might, but simply providing the shared version of the library > will solve the issue I was addressing. libtoolizing the package would > be a far more intrusive change (autoconf, Makefile.am, ... etc) so I > didn't want to go there. But it's up to you. Uh, no. I was just thinking of providing a hand-crafted version of libcrypt.la. Never mind. I've upload the new crypt package as is. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin@cygwin.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/