Mail Archives: cygwin-apps/2002/01/09/10:08:56

Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-apps-owner AT cygwin DOT com
List-Subscribe: <mailto:cygwin-apps-subscribe AT cygwin DOT com>
List-Archive: <>
List-Post: <mailto:cygwin-apps AT cygwin DOT com>
List-Help: <mailto:cygwin-apps-help AT cygwin DOT com>, <>
Delivered-To: mailing list cygwin-apps AT cygwin DOT com
Date: Wed, 9 Jan 2002 16:08:51 +0100
From: Corinna Vinschen <vinschen AT redhat DOT com>
To: cygapp <cygwin-apps AT cygwin DOT com>
Subject: Re: [ANN] apache_1.3.22 package available for setup inclusion
Message-ID: <>
Reply-To: cygwin-apps AT cygwin DOT com
Mail-Followup-To: cygapp <cygwin-apps AT cygwin DOT com>
References: <3C3BFC4C DOT 15C3C81A AT wapme-systems DOT de> <20020109124852 DOT C1242 AT cygbert DOT vinschen DOT de> <816103055 DOT 20020109125245 AT familiehaase DOT de> <3C3C5A24 DOT 23D6C6E1 AT wapme-systems DOT de>
Mime-Version: 1.0
In-Reply-To: <>
User-Agent: Mutt/

On Wed, Jan 09, 2002 at 03:56:36PM +0100, Stipe Tolj wrote:
> "Gerrit P. Haase" wrote:
> > 
> >  Corinna,
> > 
> > 2002-01-09 12:50:02, du schriebst:
> > 
> > > On Wed, Jan 09, 2002 at 09:16:12AM +0100, Stipe Tolj wrote:
> > >> Users may have to include /usr/libexec to their PATH, due to the fact
> > >> that libhttpd.dll resides there. Should we move at least that core
> > >> library to /usr/bin to have it in PATH like the other cygfoo.dlls?
> > 
> > > Shouldn't that be /usr/bin/cyghttpd.dll?
> > >                            ^^^
> > 
> > It is the same like it is with perl or python.  These packages
> > doesn't use libtool and to change the name would need some additional
> > patches in a lot of build related files which would blow up the patch.
> yep, Gerrit is right here. 
> I may change it if absolutely required, but it has to be patched in
> the Makefile.tmpl's and the main src/Configure script.
> Is it _absolutely_ required? setup.html does not state it, IMO?!

I would not like to force users to add $libexecdir to their path.
Either the dll is loaded eplicitely at runtime or it's linked in
so that it's inherently loaded at application start.  In the first
case you can even put the lib into /usr/lib (which would then make
sense, IMO).  In the second case it should go to /usr/bin.


Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin AT cygwin DOT com
Red Hat, Inc.

- Raw text -

  webmaster     delorie software   privacy  
  Copyright 2019   by DJ Delorie     Updated Jul 2019