Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Sun, 9 Jan 2005 15:01:50 -0800
From: Yitzchak Scott-Thoennes <sthoenna AT efn DOT org>
To: "Gerrit P. Haase" <gp AT familiehaase DOT de>
Cc: cygwin AT cygwin DOT com
Subject: Re: perl 5.8.6
Message-ID: <20050109230150.GA180@efn.org>
References: <41AE7F15 DOT 5030908 AT x-ray DOT at> <41AF2A74 DOT 5040503 AT familiehaase DOT de> <20041202173807 DOT GA124 AT efn DOT org> <41B04E4F DOT 50409 AT familiehaase DOT de> <20041208193053 DOT GD612 AT efn DOT org> <20041209123219 DOT GA1644 AT efn DOT org> <41E165CE DOT 7010407 AT familiehaase DOT de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <41E165CE.7010407@familiehaase.de>
User-Agent: Mutt/1.4.1i
Organization: bs"d
X-IsSubscribed: yes

On Sun, Jan 09, 2005 at 06:11:42PM +0100, Gerrit P. Haase wrote:
> Yitzchak Scott-Thoennes wrote:
> 
> >On Wed, Dec 08, 2004 at 11:30:53AM -0800, Yitzchak Scott-Thoennes wrote:
> >
> >>Gerrit, I've hoped to have some time to work on Win32:: stuff on the
> >>perl side, but haven't gotten around to it.  For 5.8.6, could you give
> >>a try to including the Win32CORE module from the perl-libwin32 package
> >>as a static extension and the Win32 module as a dynamic extension (and
> >>bootstrap Win32CORE in cygwin.c)?  If it works, that would make cygwin
> >>have equivalent to what's in win32 perl.
> >
> >
> >Here's the Win32CORE part.  I'd really like to see the builtin Win32::
> >functions be available in the cygwin perl, and this seems the easiest
> >way to do it for just a cygwin release, but in the longer term I'm
> >really hoping to get the equivalent (only newer now) code in from the
> >regular win32 perl build shared between win32 and cygwin by the time
> >5.8.7 is ready.  AIUI cutoff for that will be February 1st.

Unfortunately, this is looking unlikely at this point.  I've been
working on getting a regular win32 build to work under cygwin so
I can do testing, but haven't had enough time to get very far
with actually making the code shared.

> >This patch should apply to the perl-5.8.6 source, and the tarball has
> >the new files for the Win32CORE extension.  Those are taken verbatim
> >from the perl-libwin32 package, except that I added a "no warnings
> >"redefine"' to the Win32CORE.pm so those who use it don't get warnings.
> >I didn't make it just a no-op in case there are people sharing modules
> >between different versions of perl.
> 
> Hmmm, getting this error:
> 
>   Skipping lib/auto/Win32CORE/Win32CORE.a (directory does not exist)

Can I have a little more context?  If this is during the make, this
is what I see:

chmod 755 ../../lib/auto/DynaLoader/DynaLoader.a
make[1]: Leaving directory `/home/sthoenna/dl/tmp/perl-5.8.6/ext/DynaLoader'

        Making Win32CORE (static_pic)
Processing hints file hints/cygwin.pl
Writing Makefile for Win32CORE
make[1]: Entering directory `/home/sthoenna/dl/tmp/perl-5.8.6/ext/Win32CORE'
make[1]: Leaving directory `/home/sthoenna/dl/tmp/perl-5.8.6/ext/Win32CORE'
make[1]: Entering directory `/home/sthoenna/dl/tmp/perl-5.8.6/ext/Win32CORE'
cp Win32CORE.pm ../../lib/Win32CORE.pm
gcc -c   -DPERL_USE_SAFE_PUTENV -DDEBUGGING -fno-strict-aliasing -pipe  -pipe  -DUSEIMPORTLIB -g   -DVERSION=\"0.01\" -DXS_VERSION=\"0.01\"  "-I../.."  -DMODULE -DBACKPORT Win32CORE.c
rm -rf ../../lib/auto/Win32CORE/Win32CORE.a
/usr/bin/ar cr ../../lib/auto/Win32CORE/Win32CORE.a Win32CORE.o  && : ../../lib/auto/Win32CORE/Win32CORE.a
chmod 755 ../../lib/auto/Win32CORE/Win32CORE.a
make[1]: Leaving directory `/home/sthoenna/dl/tmp/perl-5.8.6/ext/Win32CORE'

--
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/