Windows testers, please

[Andy Lester]

Can I please get a Windows user or two to test out a new version of File::Next?

Rob has added support for named pipes to File::Next, but neither of us have a Windows box to test it on.

Brave volunteer: Please clone https://github.com/petdance/file-next and run "make test" on it and report back, please.

Thanks,

xoxo,

Andy

--
Andy Lester => an...@petdance.com => www.petdance.com => AIM:petdance

[Christopher J. Madsen]

On 5/7/2012 3:53 PM, Andy Lester wrote:
> Can I please get a Windows user or two to test out a new version of File::Next?
>
> Rob has added support for named pipes to File::Next, but neither of us have a Windows box to test it on.
>
> Brave volunteer: Please clone https://github.com/petdance/file-next and run "make test" on it and report back, please.

File-Next 1.06-26-g3cc44d2 using Perl 5.14.2 compiled myself with Visual
C++ 6 on Windows XP:

Microsoft (R) Program Maintenance Utility Version 6.00.8168.0
Copyright (C) Microsoft Corp 1988-1998. All rights reserved.

E:\Prog\Perl\5.14.2\bin\perl.exe "-MExtUtils::Command::MM" "-e"
"test_harness(0, 'blib\lib', 'blib\arch')" t/*.t
# Testing File::Next 1.06, Perl 5.014002, E:\Prog\Perl\514~1.2\bin\perl.exe
t/00-load.t ............... ok
t/api.t ................... ok
t/basic.t ................. ok
t/dirs.t .................. ok
t/dot.t ................... ok
t/everything.t ............ ok
t/follow.t ................ skipped: System does not support symlinks.
t/methods.t ............... ok
t/parms.t ................. ok
t/pod-coverage.t .......... ok
t/pod.t ................... ok
t/process-substitution.t .. 'bash' is not recognized as an internal or
external command,
operable program or batch file.
t/process-substitution.t .. skipped: You need bash to run this test
t/sort.t .................. ok
t/zero.t .................. ok
All tests successful.
Files=14, Tests=62, 2 wallclock secs ( 0.09 usr + 0.03 sys = 0.13 CPU)
Result: PASS

--
Chris Madsen pe...@cjmweb.net
-------------------- http://www.cjmweb.net --------------------

[mMontu]

On May 7, 5:53 pm, Andy Lester <A...@PETDANCE.COM> wrote:
> Can I please get a Windows user or two to test out a new version of File::Next?
>
> Rob has added support for named pipes to File::Next, but neither of us have a Windows box to test it on.
>

> Brave volunteer: Please clonehttps://github.com/petdance/file-nextand run "make test" on it and report back, please.
>
> Thanks,
> xoxo,
> Andy
>
> --
> Andy Lester => a...@petdance.com =>www.petdance.com=> AIM:petdance

Possible there is something wrong with my machine, but anyway:

Microsoft Windows XP [versão 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\petdance-file-next-1.06-26-g3cc44d2\petdance-file-next-3cc44d2>make
test
make: *** No rule to make target `test'. Stop.

C:\petdance-file-next-1.06-26-g3cc44d2\petdance-file-next-3cc44d2>perl
Makefile.PL
Checking if your kit is complete...
Looks good
Writing Makefile for File::Next
Writing MYMETA.yml and MYMETA.json

C:\petdance-file-next-1.06-26-g3cc44d2\petdance-file-next-3cc44d2>make
test
process_begin: CreateProcess(NULL, rem, ...) failed.
make (e=2): O sistema nÒo pode encontrar o arquivo especificado.
make: *** [blibdirs] Error 2
C:\petdance-file-next-1.06-26-g3cc44d2\petdance-file-next-3cc44d2>make
--version
GNU Make 3.81
Copyright (C) 2006 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.

This program built for i386-pc-mingw32

[Andy Lester]

On May 8, 2012, at 7:28 AM, mMontu wrote:

C:\petdance-file-next-1.06-26-g3cc44d2\petdance-file-next-3cc44d2>make
test
make: *** No rule to make target `test'.  Stop.

I'm sorry I didn't specify.  You still have to do the "perl Makefile.PL" and "make".  But I fear you may not have a make set up on your machine.

xoa

[mMontu]

> I'm sorry I didn't specify.  You still have to do the "perl Makefile.PL" and "make".  But I fear you may not have a make set up on your machine.

No problems, I had also tried "make" before "make test" got the same
results.
I know that the setup on this machine works fine for AVR-
microcontrollers projects.

I've tried also on MinGW portable, but got the same results.
On both attempts I've used the latest Strawberry Perl portable.

[Packy Anderson]

Using Strawberry 5.12.1 under cygwin:

$ perl Makefile.PL

Checking if your kit is complete...

Looks good

Writing Makefile for File::Next

Writing MYMETA.yml and MYMETA.json

$ make

make: rem: Command not found

make: *** [blibdirs] Error 127

I'm guessing this isn't a configuration most people have.

--
You received this message because you are subscribed to the Google Groups "ack dev/users" group.
To post to this group, send email to ack-...@googlegroups.com.
To unsubscribe from this group, send email to ack-users+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/ack-users?hl=en.

--
Packy Anderson

Email:  PackyA...@gmail.com
GVoice: (646) 833-8832

[Elliot Shank]

On 5/8/12 12:07 PM, Packy Anderson wrote:
> Using Strawberry 5.12.1 under cygwin:

[chop]

> I'm guessing this isn't a configuration most people have.

It's not a configuration that's going to work at all. You want to run dmake, which is what's used in Strawberry; otherwise, you've got mixed build chains.

[Bill Ricker]

On Tue, May 8, 2012 at 10:03 AM, Andy Lester <an...@petdance.com> wrote:

I'm sorry I didn't specify.  You still have to do the "perl Makefile.PL" and "make".  But I fear you may not have a make set up on your machine.

Availability of classical 'make' on Windows is quite limited. 

nmake and dmake if available *may* be sufficiently compatible, sometimes.

This is why pre-built modules or pure perl modules that can be installed by mere copying are prevalent.

I forget if  there is an ExtUtils work-around to emulate make ? 

--
Bill
@n1vux bill....@gmail.com

[Mark Richmond]

I just ran into this problem building Eclipse Lyo  http://www.eclipse.org/lyo/ an OSCL tool kit now that its fixed. I understand what's going on. should have be obvious. 

Use dmake not gmake which is installed as "make" by the MinGW tool kit I use for GGC  In the makefile we have something like: 

NOOP = rem

This is no understood by gnumake dmake seems to deal with fine its a windows thing after all.

Bottom line know which make you are using