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
Message-ID: <3B97B2F2.D3015C8C@yahoo.com>
Date: Thu, 06 Sep 2001 13:31:30 -0400
From: Earnie Boyd <earnie_boyd AT yahoo DOT com>
Reply-To: cygwin-apps AT cygwin DOT com
MIME-Version: 1.0
To: cygwin-apps AT cygwin DOT com
Subject: Re: fresh perlbuild and cygwin-snapshot
References: <3B97C605 DOT 30719 DOT BBDA346 AT localhost>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

"Gerrit P. Haase" wrote:
> 
> Charles Wilson schrieb am 2001-09-06, 10:58:
> 
> >Gerrit P. Haase wrote:
> >
> >
> >> I tried a second with the latest snapshot (2001-09-04), same result.
> >> I reinstalled 1.3.2 and now it works as before, no idea what is going on.
> >
> >Note that "official" package releases *must* be built only on systems
> >that do not have any snapshots or unreleased versions of dependencies. That
> >is, build your perl against a snapshot if you want, but don't release it to
> >sourceware unless you rebuild against 1.3.2 or 1.3.3. Ditto "unreleased"
> >versions of dependencies like zlib or readline or whatever.
> [...]
> 
> Thanks for the hints.  I hope it will not happen to me.
> 
> I just wanted to try out if there are some obvious differences, but there
> are no differences besides the fact that no functions were found and they
> didn't work for perl like ( time() ) which results in a compiletime error.
> 

Remember, you must also install the headers and libs in the cygwin-inst
for the snapshot when building afresh with a new dll.  You may need to
even rebuild the dependant object libraries, but that isn't always the
case.  Cygwin1.dll remains binary executable backward compatible but not
necessarily binary object backward compatible.

Earnie.

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