Re: perlctrl and cygwin - using cygwin development tools with pdk

2005-02-15 Thread Edward Peschko
On Tue, Feb 15, 2005 at 11:34:23AM -0800, Jan Dubois wrote:
> On Tue, 15 Feb 2005, Edward Peschko wrote:
> > On Tue, Feb 15, 2005 at 02:31:04AM -0500, Chris Wagner wrote:
> > > At 07:49 PM 2/14/05 -0800, Edward Peschko wrote:
> > > > However, when I try this, I get: No perl found at
> > > > C:\perl\bin\perl.exe
> > > >
> > > > even though there *is* a perl found at C:\perl\bin\perl.exe
> > >
> > > /cygdrive/c/perl/bin/perl.exe
> > >
> > > Cygwin retains Unix's distaste for the MS-DOS style path. Only
> > > ActiveState Perl understands c:\dir\
> >
> > Well, that's the point - I believe that perl itself handles
> > C:/perl/bin/perl.exe.. which is why I believe this is a bug.
> >
> > perlctrl *should* handle c:/perl/bin/perl.exe, and hence it
> > *should* work.
> 
> It handles that quite fine.  I suspect that your C:/perl/bin/perl.exe
> is not a compatible version of ActivePerl.  Can you send me the output
> of `c:\perl\bin\perl -V`?  Please also include the version of the PDK
> you are using.
> 
> > I really don't want to have to give up make, vim, screen, et al, just
> > because I want to make a dll.. Anyone got this to work?
> 
> You don't have to.  You will have to use ActivePerl with PerlCtrl though;
> Cygwin perl will not work.
> 
> Cheers,
> -Jan

Ok, here you go. I'd also be interested in what debugging info you might
need to track down a bug in perlctrl (just in case this *does* turn out 
to be a bug). Is there a 'trace' option to perlctrl?

Ed

(ps - as far as the pdk mailing list goes, I wasn't aware of such a thing..
[EMAIL PROTECTED])


C:/Perl/bin/perl -v

Summary of my perl5 (revision 5 version 8 subversion 4) configuration:
  Platform:
osname=MSWin32, osvers=4.0, archname=MSWin32-x86-multi-thread
uname=''
config_args='undef'
hint=recommended, useposix=true, d_sigaction=undef
usethreads=undef use5005threads=undef useithreads=define 
usemultiplicity=define
useperlio=define d_sfio=undef uselargefiles=define usesocks=undef
use64bitint=undef use64bitall=undef uselongdouble=undef
usemymalloc=n, bincompat5005=undef
  Compiler:
cc='cl', ccflags ='-nologo -Gf -W3 -MD -Zi -DNDEBUG -O1 -DWIN32 -D_CONSOLE 
-DNO_STRICT -DHAVE_DES_FCRYPT  -DNO_HASH_SEED -DPERL_IMPLICIT_CONTEXT 
-DPERL_IMPLICIT_SYS -DUSE_PERLIO -DPERL_MSVCRT_READFIX',
optimize='-MD -Zi -DNDEBUG -O1',
cppflags='-DWIN32'
ccversion='', gccversion='', gccosandvers=''
intsize=4, longsize=4, ptrsize=4, doublesize=8, byteorder=1234
d_longlong=undef, longlongsize=8, d_longdbl=define, longdblsize=10
ivtype='long', ivsize=4, nvtype='double', nvsize=8, Off_t='__int64', 
lseeksize=8
alignbytes=8, prototype=define
  Linker and Libraries:
ld='link', ldflags ='-nologo -nodefaultlib -debug -opt:ref,icf  
-libpath:"C:\Perl\lib\CORE"  -machine:x86'
libpth=C:\PROGRA~1\MICROS~3\VC98\lib
libs=  oldnames.lib kernel32.lib user32.lib gdi32.lib winspool.lib  
comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib  netapi32.lib 
uuid.lib wsock32.lib mpr.lib winmm.lib  version.lib odbc32.lib odbccp32.lib 
msvcrt.lib
perllibs=  oldnames.lib kernel32.lib user32.lib gdi32.lib winspool.lib  
comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib  netapi32.lib 
uuid.lib wsock32.lib mpr.lib winmm.lib  version.lib odbc32.lib odbccp32.lib 
msvcrt.lib
libc=msvcrt.lib, so=dll, useshrplib=yes, libperl=perl58.lib
gnulibc_version='undef'
  Dynamic Linking:
dlsrc=dl_win32.xs, dlext=dll, d_dlsymun=undef, ccdlflags=' '
cccdlflags=' ', lddlflags='-dll -nologo -nodefaultlib -debug -opt:ref,icf  
-libpath:"C:\Perl\lib\CORE"  -machine:x86'


Characteristics of this binary (from libperl): 
  Compile-time options: MULTIPLICITY USE_ITHREADS USE_LARGE_FILES 
PERL_IMPLICIT_CONTEXT PERL_IMPLICIT_SYS
  Locally applied patches:
ActivePerl Build 810
22751 Update to Test.pm 1.25
21540 Fix backward-compatibility issues in if.pm
  Built under MSWin32
  Compiled at Jun  1 2004 11:52:21
  %ENV:
PERL5LIB="C:\Program Files\ActiveState Perl Dev Kit 6.0\lib\"
PERL5SHELL="sh -c"
PERLDB_OPTS="RemotePort=127.0.0.1:2000"
  @INC:
C:\Program Files\ActiveState Perl Dev Kit 6.0\lib\
c:/Perl/lib
c:/Perl/site/lib
.
> 
> 
___
Perl-Win32-Users mailing list
Perl-Win32-Users@listserv.ActiveState.com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs


RE: perlctrl and cygwin - using cygwin development tools with pdk

2005-02-15 Thread Jan Dubois
On Tue, 15 Feb 2005, Edward Peschko wrote:
> On Tue, Feb 15, 2005 at 02:31:04AM -0500, Chris Wagner wrote:
> > At 07:49 PM 2/14/05 -0800, Edward Peschko wrote:
> > > However, when I try this, I get: No perl found at
> > > C:\perl\bin\perl.exe
> > >
> > > even though there *is* a perl found at C:\perl\bin\perl.exe
> >
> > /cygdrive/c/perl/bin/perl.exe
> >
> > Cygwin retains Unix's distaste for the MS-DOS style path. Only
> > ActiveState Perl understands c:\dir\
>
> Well, that's the point - I believe that perl itself handles
> C:/perl/bin/perl.exe.. which is why I believe this is a bug.
>
> perlctrl *should* handle c:/perl/bin/perl.exe, and hence it
> *should* work.

It handles that quite fine.  I suspect that your C:/perl/bin/perl.exe
is not a compatible version of ActivePerl.  Can you send me the output
of `c:\perl\bin\perl -V`?  Please also include the version of the PDK
you are using.

> I really don't want to have to give up make, vim, screen, et al, just
> because I want to make a dll.. Anyone got this to work?

You don't have to.  You will have to use ActivePerl with PerlCtrl though;
Cygwin perl will not work.

Cheers,
-Jan

PS: You may want to use the PDK mailing list for PDK problems to reach
a more targeted audience.


___
Perl-Win32-Users mailing list
Perl-Win32-Users@listserv.ActiveState.com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs


Re: perlctrl and cygwin - using cygwin development tools with pdk

2005-02-15 Thread Edward Peschko
On Tue, Feb 15, 2005 at 02:31:04AM -0500, Chris Wagner wrote:
> At 07:49 PM 2/14/05 -0800, Edward Peschko wrote:
> >However, when I try this, I get:
> > No perl found at C:\perl\bin\perl.exe
> >
> >even though there *is* a perl found at C:\perl\bin\perl.exe
> 
> /cygdrive/c/perl/bin/perl.exe
> 
> Cygwin retains Unix's distaste for the MS-DOS style path.  Only ActiveState
> Perl understands c:\dir\

Well, that's the point - I believe that perl itself handles 
C:/perl/bin/perl.exe..
which is why I believe this is a bug.

perlctrl *should* handle c:/perl/bin/perl.exe, and hence it *should* work.

I really don't want to have to give up make, vim, screen, et al, just because
I want to make a dll.. Anyone got this to work?

Ed
___
Perl-Win32-Users mailing list
Perl-Win32-Users@listserv.ActiveState.com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs


RE: perlctrl and cygwin - using cygwin development tools with pdk

2005-02-15 Thread Arms, Mike
wagnerc AT plebeian DOT com wrote:
> Edward Peschko (esp5 AT pge DOT com) wrote:
> >However, when I try this, I get:
> > No perl found at C:\perl\bin\perl.exe
> >
> >even though there *is* a perl found at C:\perl\bin\perl.exe
> 
> /cygdrive/c/perl/bin/perl.exe
> 
> Cygwin retains Unix's distaste for the MS-DOS style path.  
> Only ActiveState
> Perl understands c:\dir\

Ah, but cygwin also understands paths that use the drive
letter, colon, and forward slashes. Example:

  ls -l C:/perl/bin/perl.exe

So that is another possibility for Edward.

--
Mike Arms


___
Perl-Win32-Users mailing list
Perl-Win32-Users@listserv.ActiveState.com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs


Re: perlctrl and cygwin - using cygwin development tools with pdk

2005-02-14 Thread Chris Wagner
At 07:49 PM 2/14/05 -0800, Edward Peschko wrote:
>However, when I try this, I get:
>   No perl found at C:\perl\bin\perl.exe
>
>even though there *is* a perl found at C:\perl\bin\perl.exe

/cygdrive/c/perl/bin/perl.exe

Cygwin retains Unix's distaste for the MS-DOS style path.  Only ActiveState
Perl understands c:\dir\






___
Perl-Win32-Users mailing list
Perl-Win32-Users@listserv.ActiveState.com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs