>>>>> On Sat, 14 Apr 2007 07:35:33 +0100, [EMAIL PROTECTED] said:
[...] > [MSG] [Sat Apr 14 07:35:19 2007] Extracted 'Coro-3.55/META.yml' > [MSG] [Sat Apr 14 07:35:19 2007] Extracted 'Coro-3.55/INSTALL' > [MSG] [Sat Apr 14 07:35:19 2007] Extracted 'Coro-3.55/COPYING' > [MSG] [Sat Apr 14 07:35:19 2007] Extracted 'Coro-3.55/MANIFEST' > [MSG] [Sat Apr 14 07:35:19 2007] Extracted 'Coro-3.55/README.linux-glibc' > [MSG] [Sat Apr 14 07:35:19 2007] Extracted 'Coro' to '/home/cwill1is/.cpanplus/5.8.8/build/Coro-3.55' > [MSG] [Sat Apr 14 07:35:19 2007] > *** Event not found, not build Event support. [...] > [ERROR] [Sat Apr 14 07:35:33 2007] MAKE TEST failed: PERL_DL_NONLAZY=1 /usr/home/cwill1is/perl588/bin/perl "-MExtUtils::Command::MM" "-e" "test_harness(0, 'blib/lib', 'blib/arch')" t/*.t > t/Continuity....dubious > Test returned status 1 (wstat 256, 0x100) > DIED. FAILED test 1 > Failed 1/1 tests, 0.00% okay > Failed Test Stat Wstat Total Fail List of Failed > ------------------------------------------------------------------------------- > t/Continuity.t 1 256 1 1 1 > Failed 1/1 test scripts. 1/1 subtests failed. > Files=1, Tests=1, 0 wallclock secs ( 0.05 cusr + 0.02 csys = 0.07 CPU) > *** Error code 1 > Stop in /usr/home/cwill1is/.cpanplus/5.8.8/build/Continuity-0.92. > # Failed test 'use Continuity;' > # at t/Continuity.t line 9. > # Tried to use 'Continuity'. > # Error: Can't locate Coro/Event.pm in @INC (@INC contains: /usr/home/cwill1is/.cpanplus/5.8.8/build/Continuity-0.92/blib/lib /usr/home/cwill1is/.cpanplus/5.8.8/build/Continuity-0.92/blib/arch /home/cwill1is/.cpanplus/5.8.8/build/AnyEvent-2.52/blib/lib /home/cwill1is/.cpanplus/5.8.8/build/AnyEvent-2.52/blib/arch /home/cwill1is/.cpanplus/5.8.8/build/AnyEvent-2.52/blib /home/cwill1is/.cpanplus/5.8.8/build/Coro-3.55/blib/lib /home/cwill1is/.cpanplus/5.8.8/build/Coro-3.55/blib/arch /home/cwill1is/.cpanplus/5.8.8/build/Coro-3.55/blib /home/cwill1is/.cpanplus/5.8.8/build/Data-Alias-1.03/blib/lib /home/cwill1is/.cpanplus/5.8.8/build/Data-Alias-1.03/blib/arch /home/cwill1is/.cpanplus/5.8.8/build/Data-Alias-1.03/blib /home/cwill1is/.cpanplus/5.8.8/build/Module-Reload-1.07/blib/lib /home/cwill1is/.cpanplus/5.8.8/build/Module-Reload-1.07/blib/arch /home/cwill1is/.cpanplus/5.8.8/build/Module-Reload-1.07/blib /home/cwill1is/.cpanplus/5.8.8/build/Continuity-0.92/blib/lib /home/cwill1is/.cpanplus/5.8.8/build/Continuity-0.92/blib/arch /home/cwill1is/.cpanplus/5.8.8/build/Continuity-0.92/blib /usr/home/cwill1is/perl588/lib/5.8.8/i386-freebsd-thread-multi-64int /usr/home/cwill1is/perl588/lib/5.8.8/i386-freebsd-thread-multi-64int /usr/home/cwill1is/perl588/lib/5.8.8 /usr/home/cwill1is/perl588/lib/site_perl/5.8.8/i386-freebsd-thread-multi-64int /usr/home/cwill1is/perl588/lib/site_perl/5.8.8/i386-freebsd-thread-multi-64int /usr/home/cwill1is/perl588/lib/site_perl/5.8.8 /usr/home/cwill1is/perl588/lib/site_perl/5.8.8/i386-freebsd-thread-multi-64int /usr/home/cwill1is/perl588/lib/site_perl/5.8.8 /usr/home/cwill1is/perl588/lib/site_perl . /usr/home/cwill1is/perl588/lib/5.8.8/i386-freebsd-thread-multi-64int /usr/home/cwill1is/perl588/lib/5.8.8 /usr/home/cwill1is/perl588/lib/site_perl/5.8.8/i386-freebsd-thread-multi-64int /usr/home/cwill1is/perl588/lib/site_perl/5.8.8 /usr/home/cwill1is/perl588/lib/site_perl .) at /usr/home/cwill1is/.cpanplus/5.8.8/build/Continuity-0.92/blib/lib/Continuity.pm line 161. > # BEGIN failed--compilation aborted at t/Continuity.t line 9. > # Compilation failed in require at (eval 3) line 2. > # BEGIN failed--compilation aborted at (eval 3) line 2. > # Looks like you failed 1 test of 1. > Failed 1/1 test programs. 1/1 subtests failed. The reason for this failure is that Coro per default chooses to not build Coro::Event under a pristine perl and that Continuity has no way to express its wish that it (Coro) be built with event support. Ideally, Marc would ask the user if he wants to build Event support (he asks many questions anyway:) and if the user says yes, then he should put the necessary modules (Event? AnyEnvent? Etc.) into its own prerequisites. The answer should default to yes, so that automated build environments build in doubt too many modules. Would that be OK for you, Marc? -- andreas
