Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Message-ID:	<12F176DD950ED411B68E0050DA14ED1033875D@jupiter.gunzphoto.com.au>
From:	Neil Lunn <neillunn AT gunz DOT com DOT au>
To:	"'Charles S. Wilson'" <cwilson AT ece DOT gatech DOT edu>,
	"Victor M. Esquivel"
	<vesquivel AT lucent DOT com>
Cc:	"'cygwin AT cygwin DOT com'" <cygwin AT cygwin DOT com>
Subject:	RE: Perl/Tk with patches no long compiles with CygWin v1.3.1
Date:	Mon, 30 Apr 2001 13:16:03 +1000
MIME-Version:	1.0
X-Mailer:	Internet Mail Service (5.5.2448.0)

> -----Original Message-----
> From: Charles S. Wilson [mailto:cwilson AT ece DOT gatech DOT edu]
> Sent: Saturday, April 28, 2001 7:24 AM
> To: Victor M. Esquivel
> Cc: Neil Lunn; 'cygwin AT cygwin DOT com'
> Subject: Re: Perl/Tk with patches no long compiles with CygWin v1.3.1
> 
> 
> During the initial build of perl itself, perl copies some information
> (from the gcc specs file?) into its Config.pm. file.  I *think* that
> once Eric Fifer rebuilds perl-5.6.1 using the current gcc, the new
> Config.pm file will have the right stuff in it.  However, he's still
> working on fixing the annoying text mode problems that 
> cropped up in the
> current cygwin-perl package; that thorny problem is delaying any new
> release of perl for cygwin(*). AFAIK.
> 

Sorry that I have been away from this, with international timing and all.
I feel a need to clarify this a bit further.

There is no actual problem here at all. A look at the posted patch for
Tk880.022 reveals that the standard LD behaivor (ld2 - call to dlltool) is
being overidden with gcc -shared. Therefor dlltool is searching the w32api
directory.

Including the library path within Config.pm is not going to break a
distribution and is not required once all modules have been correctly
patched.

The patch should be made to the Tk distribution and is really a simple one
liner to include the libary path. I am currently going through all of the
Win32 stuff on CPAN, cleaning it up a bit and trying to test the functions
against native Win32 builds. I would suggest that once this is done it would
probably be worthwile to bundle all of the present libwin32 modules with the
cygwin distribution as is done with ActivePerl.

Neil Lunn

__________________________________________________________________________
Please Note :
Only  the intended recipient is authorised to access or use this e-mail.  If
you are not the intended recipient,
please delete this e-mail and notify the sender immediately.   The contents
of this e-mail are the writer's 
opinion and are not necessarily endorsed by the Gunz Companies unless
expressly stated.

We use virus scanning software but exclude all liability for viruses or
similar in any attachment.



--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

- Raw text -