Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com
List-Subscribe: <mailto:cygwin-apps-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-apps/>
List-Post: <mailto:cygwin-apps AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-apps-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/lists.html#faqs>
Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com
Message-ID: <3BEACDAB.4050203@ece.gatech.edu>
Date: Thu, 08 Nov 2001 13:23:39 -0500
From: Charles Wilson <cwilson AT ece DOT gatech DOT edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2
X-Accept-Language: en-us
MIME-Version: 1.0
To: "Gerrit P. Haase" <cygwin-apps AT cygwin DOT com>
Subject: Re: berkeley db?
References: <16713088420 DOT 20011108164830 AT familiehaase DOT de> <3BEAB3E8 DOT 6060207 AT ece DOT gatech DOT edu> <6818860930 DOT 20011108182442 AT familiehaase DOT de>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Gerrit P. Haase wrote:

> 
>>>I don't remember what the problem was with db-3.1.17, why was it not
>>>included in the dist?
>>>
> 
>>1. new package moratorium
>>
> 
> This will be gone soon, I hope.


Yep.

>>2. not fully ported (IMO, a library is fully ported when it (a) has no 
>>remaining text/binary issues, (b) can be built as both a static lib and as 
>>a DLL)
>>
> 
> (a) Don't know about issues here. BTW, the current(blead) perl has a new cr/lf
>     behaviour;) If you export PERLIO=perlio it works as expected in all cases.
>     If not (it seems to default to PERLIO=stdio) the same problem as before.


That's when *perl* handles the actual on-disk IO.  However, when you use 
the db:: routines, the db::whatever perl statements trigger certain library 
routines inside libdb.a -- like db_open() -- which themselves call file 
access functions -- like fopen().  So, libdb itself needs to be 
"dos-proofed" by fixing the appropriate fopen and open function calls.

> 
> (b) db-3.1.17 is built with static and dynamic libs. 3x builds OOTB as static.
>     Why is it a must to have dynamic libs?


Well, it's not a *must* -- it's *my* preference.  However, since I am not 
volunteering to support that package, I don't suppose it really matters 
what I think. :-)


>>3. nobody volunteered to contribute, support, and maintain it
>>
> 
> Hmm, I guess there will be someone out there who will do it.  If sleepycat upgrades
> to the latest autoconf and automake and libtool it will probably build OOTB with
> both, static and dynamic libs (I hope they will do so soon).


No, probably not.  The "latest" libtool only kinda-sorta supports building 
DLL's -- and only if you jump thru a number of hoops (see the goatbook).

For "clean" unix-like shared library building on cygwin, we have to wait 
for Robert Collin's changes to get folded into the official libtool.  Gary 
Vaughan is on the case...but I haven't been pushing.  I'm waiting for the 
autoconf/automake wrapper script packages that I wrote , with the 
side-by-side installation of 2.52/2.13 and 1.4p5/1.5, to be added to the 
official cygwin distro.  But that, in turn, is waiting on the new setup...

THEN I'll start pushing Gary. :-)

--Chuck