delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin-apps/2002/01/09/15:10:28

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: <http://sources.redhat.com/ml/cygwin-apps/>
List-Post: <mailto:cygwin-apps AT cygwin DOT com>
List-Help: <mailto:cygwin-apps-help AT cygwin DOT com>, <http://sources.redhat.com/lists.html#faqs>
Delivered-To: mailing list cygwin-apps AT cygwin DOT com
Message-ID: <3C3CA387.D4DEFC83@yahoo.com>
Date: Wed, 09 Jan 2002 15:09:43 -0500
From: Earnie Boyd <earnie_boyd AT yahoo DOT com>
Reply-To: CA List <Cygwin-Apps AT cygwin DOT com>
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Stipe Tolj <tolj AT wapme-systems DOT de>
CC: cygwin-apps <cygwin-apps AT cygwin DOT com>
Subject: Re: [ANN] apache_1.3.22 package available for setup inclusion
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> <3C3C6842 DOT 3030403 AT ece DOT gatech DOT edu> <3C3C6A3B DOT F6FE54BF AT wapme-systems DOT de>

Stipe Tolj wrote:
> 
> > Suppose you had both a native apache port and a cygwin apache port.
> > Assume both were built "shared" -- so both had a "libhttpd.dll" shared
> > library.  However, one is msvcrt.dll based, the other cygwin1.dll based.
> >   Because the respective httpd.exe's are inherently linked to these
> > DLL's, both require that the dirs containing those DLLs are in the
> > global system path -- but one of them must come first, since there's
> > only one global system path.
> 
> mop, the Win32 native ports of Apache use ApacheCore.dll and
> ApacheFooBar.dll name structures for the shared libs.
> 

Yet, if the dll is dependent on cygwin1.dll it must be prefixed with
`cyg'.  There is not a point of argument, it is an agreed upon
standard.  Not all packages that existed before the standard was stated
have been upgraded to the standard.  However, new packages being added
must meet that standard, regardless of other points of view.

My guess is that you're using a cross build platform that hasn't
incorporated the necessary changes to binutils to accomplish this
naturally.  If this is true then you need to upgrade your binutils cross
to the most current versions of cygwin released binutils source.

I am not trying to make it harder for you just because I feel like it. 
I am trying to make it easier for everyone to create, use and port tools
in a standard fashion.  If we allow exceptions, then it will be harder
to determine standard in the future.

Earnie.

_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com

- Raw text -


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