Re: HP-UX state
On Mon 21 Jan 2002 19:25, Simon Glover [EMAIL PROTECTED] wrote: On Mon, 21 Jan 2002, H.Merijn Brand wrote: perl vtable_h.pl make: *** No rule to make target `include/parrot/rxstacks.h', needed by `test_main.o'. Stop. This exists (and has done for a couple of days) but isn't in the MANIFEST at the moment (I've already sent a patch). Could that be causing the problem? I'm only active on perl5, and perl6 is smoking every night, but the last OK report was Dec 6. My previous HP-UX report in what was failing was from Jan 9 and dealt with LDFLAGS, which was addressed by Andy D IIRC. If I find a little time to check /why/ the parrot smokes stall, I'll just give it a manual flip and send in the results, in the hope it'll help you guys. Sometimes it's just a bad sync moment, sometimes it's a fundamental problem. If you like a different approach (that doesn't take much more time of my side), just give a yell. -- H.Merijn BrandAmsterdam Perl Mongers (http://amsterdam.pm.org/) using perl-5.6.1, 5.7.2 631 on HP-UX 10.20 11.00, AIX 4.2, AIX 4.3, WinNT 4, Win2K pro WinCE 2.11. Smoking perl CORE: [EMAIL PROTECTED] http:[EMAIL PROTECTED]/ [EMAIL PROTECTED] send smoke reports to: [EMAIL PROTECTED], QA: http://qa.perl.org
HP-UX state
l1:/pro/3gl/CPAN/parrot-current 114 perl Configure.pl --default Parrot Version 0.0.3 Configure Copyright (C) 2001-2002 Yet Another Society Since you're running this script, you obviously have Perl 5--I'll be pulling some defaults from its configuration. Checking the MANIFEST to make sure you have a complete Parrot kit... Okay, we found everything. Next you'll need to answer a few questions about your system. Defaults are in square brackets, and you can hit enter to accept them. If you don't want the default, type a new value in. If that new value starts with a '+', it will be concatenated to the default value. Determining if your C compiler is actually gcc (this could take a while): Your C compiler is not gcc. Probing Perl 5's configuration to determine which headers you have (this could take a while on slow machines)... Determining C data type sizes by compiling and running a small C program (this could take a while): Building ./test.c from test_c.in... Figuring out the formats to pass to pack() for the various Parrot internal types... Figuring out what integer type we can mix with pointers... We'll use 'unsigned int'. Building a preliminary version of include/parrot/config.h, your Makefiles, and other files: Building include/parrot/config.hfrom config_h.in... Building ./Makefile from Makefile.in... Building ./classes/Makefile from classes/Makefile.in... Building ./docs/Makefilefrom docs/Makefile.in... Building ./languages/Makefile from languages/Makefile.in... Building ./languages/jako/Makefile from languages/jako/Makefile.in... Building ./languages/miniperl/Makefile from languages/miniperl/Makefile.in... Building ./languages/scheme/Makefilefrom languages/scheme/Makefile.in... Building Parrot/Types.pmfrom Types_pm.in... Building Parrot/Config.pm from Config_pm.in... Checking some things by compiling and running another small C program (this could take a while): Building ./testparrotsizes.cfrom testparrotsizes_c.in... Updating include/parrot/config.h: Building include/parrot/config.hfrom config_h.in... Okay, we're done! You can now use `make' (or your platform's equivalent to `make') to build your Parrot. After that, you can use `make test' to run the test suite. Happy Hacking, The Parrot Team l1:/pro/3gl/CPAN/parrot-current 115 make perl vtable_h.pl make: *** No rule to make target `include/parrot/rxstacks.h', needed by `test_main.o'. Stop. Exit 2 l1:/pro/3gl/CPAN/parrot-current 116 cat .timestamp 1011556802 Sun Jan 20 20:00:02 2002 UTC (time of this cvs update) l1:/pro/3gl/CPAN/parrot-current 117 -- H.Merijn BrandAmsterdam Perl Mongers (http://amsterdam.pm.org/) using perl-5.6.1, 5.7.2 631 on HP-UX 10.20 11.00, AIX 4.2, AIX 4.3, WinNT 4, Win2K pro WinCE 2.11. Smoking perl CORE: [EMAIL PROTECTED] http:[EMAIL PROTECTED]/ [EMAIL PROTECTED] send smoke reports to: [EMAIL PROTECTED], QA: http://qa.perl.org
HP-UX state report
HP-UX is very unwilling at this stage, including two show-stoppers 1. The LDFLAGS is extended with flags from config that are meant to be passed to cc, not to ld 2. Undefined symbols inhibit the basic build a5:/pro/3gl/CPAN/parrot-current 101 perl Configure.pl --default Parrot Version 0.0.3 Configure Copyright (C) 2001-2002 Yet Another Society Since you're running this script, you obviously have Perl 5--I'll be pulling some defaults from its configuration. Checking the MANIFEST to make sure you have a complete Parrot kit... Okay, we found everything. Next you'll need to answer a few questions about your system. Defaults are in square brackets, and you can hit enter to accept them. If you don't want the default, type a new value in. If that new value starts with a '+', it will be concatenated to the default value. Determining if your C compiler is actually gcc (this could take a while): Your C compiler is not gcc. Probing Perl 5's configuration to determine which headers you have (this could take a while on slow machines)... Determining C data type sizes by compiling and running a small C program (this could take a while): Building ./test.c from test_c.in... Figuring out the formats to pass to pack() for the various Parrot internal types... Figuring out what integer type we can mix with pointers... We'll use 'unsigned int'. Building a preliminary version of include/parrot/config.h, your Makefiles, and other files: Building include/parrot/config.hfrom config_h.in... Building ./Makefile from Makefile.in... Building ./classes/Makefile from classes/Makefile.in... Building ./docs/Makefilefrom docs/Makefile.in... Building ./languages/Makefile from languages/Makefile.in... Building ./languages/jako/Makefile from languages/jako/Makefile.in... Building ./languages/miniperl/Makefile from languages/miniperl/Makefile.in... Building ./languages/scheme/Makefilefrom languages/scheme/Makefile.in... Building Parrot/Types.pmfrom Types_pm.in... Building Parrot/Config.pm from Config_pm.in... Checking some things by compiling and running another small C program (this could take a while): Building ./testparrotsizes.cfrom testparrotsizes_c.in... Updating include/parrot/config.h: Building include/parrot/config.hfrom config_h.in... Okay, we're done! You can now use `make' (or your platform's equivalent to `make') to build your Parrot. After that, you can use `make test' to run the test suite. Happy Hacking, The Parrot Team a5:/pro/3gl/CPAN/parrot-current 102 make perl vtable_h.pl perl make_vtable_ops.pl vtable.ops perl ops2c.pl C core.ops vtable.ops perl ops2c.pl CPrederef core.ops vtable.ops cc -DDEBUGGING -Ae -D_HPUX_SOURCE -I/pro/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I./include -o test_main.o -c test_main.c cc -DDEBUGGING -Ae -D_HPUX_SOURCE -I/pro/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I./include -o global_setup.o -c global_setup.c cc -DDEBUGGING -Ae -D_HPUX_SOURCE -I/pro/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I./include -o interpreter.o -c interpreter.c cc -DDEBUGGING -Ae -D_HPUX_SOURCE -I/pro/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I./include -o parrot.o -c parrot.c cc -DDEBUGGING -Ae -D_HPUX_SOURCE -I/pro/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I./include -o register.o -c register.c cc -DDEBUGGING -Ae -D_HPUX_SOURCE -I/pro/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I./include -o core_ops.o -c core_ops.c cc -DDEBUGGING -Ae -D_HPUX_SOURCE -I/pro/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I./include -o core_ops_prederef.o -c core_ops_prederef.c cc -DDEBUGGING -Ae -D_HPUX_SOURCE -I/pro/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I./include -o memory.o -c memory.c cc -DDEBUGGING -Ae -D_HPUX_SOURCE -I/pro/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I./include -o packfile.o -c packfile.c cc -DDEBUGGING -Ae -D_HPUX_SOURCE -I/pro/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I./include -o stacks.o -c stacks.c cc -DDEBUGGING -Ae -D_HPUX_SOURCE -I/pro/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I./include -o string.o -c string.c cc -DDEBUGGING -Ae -D_HPUX_SOURCE -I/pro/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I./include -o encoding.o -c encoding.c cc -DDEBUGGING -Ae -D_HPUX_SOURCE -I/pro/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I./include -o chartype.o -c chartype.c cc -DDEBUGGING -Ae -D_HPUX_SOURCE -I/pro/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I./include -o runops_cores.o -c runops_cores.c cc -DDEBUGGING -Ae -D_HPUX_SOURCE -I/pro/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I./include -o
HP-UX is dead :(
# perl configure --default : : Okay, we're done! You can now use `make parrot' (or your platform's equivalent to `make') to build your Parrot. Happy Hacking, The Parrot Team l1:/pro/3gl/CPAN/parrot-current 104 make parrot perl vtable_h.pl cc -DDEBUGGING -Ae -D_HPUX_SOURCE -I/pro/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64-I./include -o parrot.o -c parrot.c cc parrot.o -o parrot /usr/ccs/bin/ld: (Warning) At least one PA 2.0 object file (parrot.o) was detected. The linked output may not run on a PA 1.x system. /usr/ccs/bin/ld: Unsatisfied symbols: main (Not referenced yet! Probably due to -u option) make: *** [parrot] Error 1 Exit 2 l1:/pro/3gl/CPAN/parrot-current 105 -- H.Merijn BrandAmsterdam Perl Mongers (http://amsterdam.pm.org/) using perl-5.6.1, 5.7.2 630 on HP-UX 10.20 11.00, AIX 4.2, AIX 4.3, WinNT 4, Win2K pro WinCE 2.11. Smoking perl CORE: [EMAIL PROTECTED] http:[EMAIL PROTECTED]/ [EMAIL PROTECTED] send smoke reports to: [EMAIL PROTECTED], QA: http://qa.perl.org
HP-UX again
Changed 'make parrot' to 'make'
cc -DDEBUGGING -Ae -D_HPUX_SOURCE -I/pro/local/include -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64-I./include -o interpreter.o -c interpreter.c
cc: interpreter.c, line 160: warning 604: Pointers are not assignment-compatible.
and - for the smokes - please change
--- Makefile.in Sun Dec 16 15:00:00 2001
+++ Makefile.in.new Tue Dec 18 15:04:31 2001
@@ -160,7 +160,7 @@
cd languages $(MAKE) clean cd ..
distclean:
- $(PERL) -MExtUtils::Manifest=filecheck -le
'$$ExtUtils::Manifest::Quiet=1;unlink $$_ for filecheck()'
+ $(PERL) -MExtUtils::Manifest=filecheck -le '$$ExtUtils::Manifest::Quiet=1;$$_
+eq .timestamp||unlink $$_ for filecheck()'
cvsclean:
$(PERL) -MExtUtils::Manifest=filecheck -le '$$ExtUtils::Manifest::Quiet=1; do
{ unlink $$_ unless $$_ =~ m!(?:CVS/|\.cvs)! } for filecheck()'
HP-UX 11.00 --default
:
cc -DDEBUGGING -Ae -D_HPUX_SOURCE -I/pro/local/include -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64-I./include -o interpreter.o -c interpreter.c
cc: interpreter.c, line 160: warning 604: Pointers are not assignment-compatible.
:
Automated smoke report for patch Tue Dec 18 14:00:02 2001 UTC
v0.02 on hpux - 11.00 using cc version B.11.11.02
O = OK
F = Failure(s), extended report at the bottom
? = still running or test results not (yet) available
Build failures during: - = unknown
c = Configure, m = make, t = make test-prep
Configuration
---
O O
O O nv=double
O O iv=int
O O iv=int --define nv=double
O O iv=long
O O iv=long --define nv=double
| |
| +- --debugging
+--- normal
AIX 4.3 --default:
:
xlc -DDEBUGGING -D_ALL_SOURCE -D_ANSI_C_SOURCE -D_POSIX_SOURCE -qmaxmem=16384 -I
/pro/local/include -q32 -D_LARGE_FILES -qlonglong -I./include -o interpreter.o
-c interpreter.c
interpreter.c, line 160.7: 1506-068 (E) Operation between types void* and
void**(*)() is not allowed.
:
:
xlc -DDEBUGGING -D_ALL_SOURCE -D_ANSI_C_SOURCE -D_POSIX_SOURCE -qmaxmem=16384
-I/pro/local/include -q32 -D_LARGE_FILES -qlonglong -I../include -o perlint.o -c
perlint.c
perlint.c, line 566.9: 1506-196 (E) Initialization between types void(*)(struct
Parrot_Interp*,struct PMC*,long,long) and void(*)(struct Parrot_Interp*,struct
PMC*,long) is not allowed.
perlint.c, line 571.9: 1506-196 (E) Initialization between types void(*)(struct
Parrot_Interp*,struct PMC*,double,long) and void(*)(struct Parrot_Interp*,struct
PMC*,long) is not allowed.
perlint.c, line 577.9: 1506-196 (E) Initialization between types void(*)(struct
Parrot_Interp*,struct PMC*,struct {...}*,long) and void(*)(struct
Parrot_Interp*,struct PMC*,long) is not allowed.
perl pmc2c.pl perlnum.pmc
xlc -DDEBUGGING -D_ALL_SOURCE -D_ANSI_C_SOURCE -D_POSIX_SOURCE -qmaxmem=16384
-I/pro/local/include -q32 -D_LARGE_FILES -qlonglong -I../include -o perlnum.o -c
perlnum.c
perlnum.c, line 483.9: 1506-196 (E) Initialization between types double(*)(struct
Parrot_Interp*,struct PMC*,long) and double(*)(struct Parrot_Interp*,struct PMC*)
is not allowed.
perlnum.c, line 485.9: 1506-196 (E) Initialization between types struct
{...}*(*)(struct Parrot_Interp*,struct PMC*,long) and struct {...}*(*)(struct
Parrot_Interp*,struct PMC*) is not allowed.
perl pmc2c.pl perlstring.pmc
xlc -DDEBUGGING -D_ALL_SOURCE -D_ANSI_C_SOURCE -D_POSIX_SOURCE -qmaxmem=16384
-I/pro/local/include -q32 -D_LARGE_FILES -qlonglong -I../include -o perlstring.o -c
perlstring.c
perlstring.c, line 471.9: 1506-196 (E) Initialization between types long(*)(struct
Parrot_Interp*,struct PMC*,long) and long(*)(struct Parrot_Interp*,struct PMC*) is
not allowed.
perlstring.c, line 473.9: 1506-196 (E) Initialization between types
double(*)(struct Parrot_Interp*,struct PMC*,long) and double(*)(struct
Parrot_Interp*,struct PMC*) is not allowed.
perlstring.c, line 475.9: 1506-196 (E) Initialization between types struct
{...}*(*)(struct Parrot_Interp*,struct PMC*,long) and struct {...}*(*)(struct
Parrot_Interp*,struct PMC*) is not allowed.
:
:
i2:/pro/3gl/CPAN/parrot-current 104 make test
perl t/harness
t/op/basic..ok
t/op/bitwiseok
t/op/integerok
t/op/interp.ok
t/op/keyok
t/op/macro..ok
t/op/number.ok 7/28# Failed test (Parrot/Test.pm at line 76)
# got: '5.00
-0.00
2.00
-1.00
1.00
-2.00
'
# expected: '5.00
0.00
2.00
-1.00
1.00
-2.00
'
t/op/number.ok 28/28# Looks like you failed 1 tests of 28.
t/op/number.dubious
Test returned status 1 (wstat 256, 0x100)
DIED. FAILED test 8
Failed 1/28 tests, 96.43% okay
t/op/pmcok, 1/44 skipped: string-int not finished yet
t/op/stacks.ok, 3/16 skipped: various reasons
Parrot Smoke Dec 6 20:00:01 2001 UTC hpux 11.00
I will not post these until status changes in order not to clutter the list. Assume succes on HP-UX 11.00 until a report proves different. Automated smoke report for patch Dec 6 20:00:01 2001 UTC v0.02 on hpux - 11.00 using cc version B.11.11.02 O = OK F = Failure(s), extended report at the bottom ? = still running or test results not (yet) available Build failures during: - = unknown c = Configure, m = make, t = make test-prep Configuration --- O O O O nv=double O O iv=int O O iv=int --define nv=double O O iv=long O O iv=long --define nv=double | | | +- --debugging +--- normal -- H.Merijn BrandAmsterdam Perl Mongers (http://amsterdam.pm.org/) using perl-5.6.1, 5.7.2 630 on HP-UX 10.20 11.00, AIX 4.2, AIX 4.3, WinNT 4, Win2K pro WinCE 2.11. Smoking perl CORE: [EMAIL PROTECTED] http:[EMAIL PROTECTED]/ [EMAIL PROTECTED] send smoke reports to: [EMAIL PROTECTED], QA: http://qa.perl.org
Parrot Smoke Dec 3 20:00:03 2001 UTC hpux 11.00
Automated smoke report for patch Dec 3 20:00:03 2001 UTC v0.02 on hpux - 11.00 using cc version B.11.11.02 O = OK F = Failure(s), extended report at the bottom ? = still running or test results not (yet) available Build failures during: - = unknown c = Configure, m = make, t = make test-prep Configuration --- O O O O nv=double O O iv=int O O iv=int --define nv=double O O iv=long O O iv=long --define nv=double | | | +- --debugging +--- normal -- H.Merijn BrandAmsterdam Perl Mongers (http://amsterdam.pm.org/) using perl-5.6.1, 5.7.2 630 on HP-UX 10.20 11.00, AIX 4.2, AIX 4.3, WinNT 4, Win2K pro WinCE 2.11. Smoking perl CORE: [EMAIL PROTECTED] http:[EMAIL PROTECTED]/ [EMAIL PROTECTED] send smoke reports to: [EMAIL PROTECTED], QA: http://qa.perl.org
Parrot Smoke Dec 2 20:00:02 2001 UTC hpux 11.00
Automated smoke report for patch Dec 2 20:00:02 2001 UTC v0.02 on hpux - 11.00 using cc version B.11.11.02 O = OK F = Failure(s), extended report at the bottom ? = still running or test results not (yet) available Build failures during: - = unknown c = Configure, m = make, t = make test-prep Configuration --- O O O O nv=double O O iv=int O O iv=int --define nv=double O O iv=long O O iv=long --define nv=double | | | +- --debugging +--- normal -- H.Merijn BrandAmsterdam Perl Mongers (http://amsterdam.pm.org/) using perl-5.6.1, 5.7.2 630 on HP-UX 10.20 11.00, AIX 4.2, AIX 4.3, WinNT 4, Win2K pro WinCE 2.11. Smoking perl CORE: [EMAIL PROTECTED] http:[EMAIL PROTECTED]/ [EMAIL PROTECTED] send smoke reports to: [EMAIL PROTECTED], QA: http://qa.perl.org
Parrot Smoke Dec 1 20:00:02 2001 UTC hpux 11.00
Automated smoke report for patch Dec 1 20:00:02 2001 UTC v0.02 on hpux - 11.00 using cc version B.11.11.02 O = OK F = Failure(s), extended report at the bottom ? = still running or test results not (yet) available Build failures during: - = unknown c = Configure, m = make, t = make test-prep Configuration --- O O O O nv=double O O iv=int O O iv=int --define nv=double O O iv=long O O iv=long --define nv=double | | | +- --debugging +--- normal -- H.Merijn BrandAmsterdam Perl Mongers (http://amsterdam.pm.org/) using perl-5.6.1, 5.7.2 630 on HP-UX 10.20 11.00, AIX 4.2, AIX 4.3, WinNT 4, Win2K pro WinCE 2.11. Smoking perl CORE: [EMAIL PROTECTED] http:[EMAIL PROTECTED]/ [EMAIL PROTECTED] send smoke reports to: [EMAIL PROTECTED], QA: http://qa.perl.org
Fw: Parrot Smoke Nov 28 20:00:02 2001 UTC hpux 11.00
--- Original Message --- From:H.M. Brand [EMAIL PROTECTED] To: [EMAIL PROTECTED] Date:Wed, 28 Nov 2001 23:03:45 +0100 (MET) Subject: Parrot Smoke Nov 28 20:00:02 2001 UTC hpux 11.00 Automated smoke report for patch Nov 28 20:00:02 2001 UTC v0.02 on hpux - 11.00 using cc version B.11.11.02 O = OK F = Failure(s), extended report at the bottom ? = still running or test results not (yet) available Build failures during: - = unknown c = Configure, m = make, t = make test-prep Configuration --- O O O O nv=double O O iv=int O O iv=int --define nv=double O O iv=long O O iv=long --define nv=double | | | +- --debugging +--- normal - Original Message Ends
Parrot Smoke Nov 29 20:00:01 2001 UTC hpux 11.00
--- Original Message --- From:H.M. Brand [EMAIL PROTECTED] To: [EMAIL PROTECTED] Date:Thu, 29 Nov 2001 23:02:10 +0100 (MET) Subject: Parrot Smoke Nov 29 20:00:01 2001 UTC hpux 11.00 Automated smoke report for patch Nov 29 20:00:01 2001 UTC v0.02 on hpux - 11.00 using cc version B.11.11.02 O = OK F = Failure(s), extended report at the bottom ? = still running or test results not (yet) available Build failures during: - = unknown c = Configure, m = make, t = make test-prep Configuration --- O O O O nv=double O O iv=int O O iv=int --define nv=double O O iv=long O O iv=long --define nv=double | | | +- --debugging +--- normal - Original Message Ends
Parrot Smoke Nov 28 08:00:01 2001 UTC hpux 11.00
Automated smoke report for patch Nov 28 08:00:01 2001 UTC v0.02 on hpux - 11.00 using cc version B.11.11.02 O = OK F = Failure(s), extended report at the bottom ? = still running or test results not (yet) available Build failures during: - = unknown c = Configure, m = make, t = make test-prep Configuration --- O O O O nv=double O O iv=int O O iv=int --define nv=double O O iv=long O O iv=long --define nv=double | | | +- --debugging +--- normal -- H.Merijn BrandAmsterdam Perl Mongers (http://amsterdam.pm.org/) using perl-5.6.1, 5.7.2 630 on HP-UX 10.20 11.00, AIX 4.2, AIX 4.3, WinNT 4, Win2K pro WinCE 2.11. Smoking perl CORE: [EMAIL PROTECTED] http:[EMAIL PROTECTED]/ [EMAIL PROTECTED] send smoke reports to: [EMAIL PROTECTED], QA: http://qa.perl.org
HP-UX 10.20 status
cc -DDEBUGGING +DAportable -Ae -D_HPUX_SOURCE -I/pro/local/include \ -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I./include \ -o platform.o -c platform.c cpp: platform.c, line 6: error 4036: Can't open include file 'dlfcn.h'. make: *** [platform.o] Error 1 -- H.Merijn BrandAmsterdam Perl Mongers (http://amsterdam.pm.org/) using perl-5.6.1, 5.7.2 630 on HP-UX 10.20 11.00, AIX 4.2, AIX 4.3, WinNT 4, Win2K pro WinCE 2.11. Smoking perl CORE: [EMAIL PROTECTED] http:[EMAIL PROTECTED]/ [EMAIL PROTECTED] send smoke reports to: [EMAIL PROTECTED], QA: http://qa.perl.org
AIX 4.3 status
# perl Configure.pl --default : : Okay, that's finished. I'm now going to write your very own Makefile, config.h, Parrot::Types, and Parrot::Config to disk. Alright, now I'm gonna check some stuff by compiling and running another small C program. This could take a bit... ./include/parrot/vtable.h, line 1: 1506-229 (W) File is empty. ./include/parrot/pmc.h, line 54.33: 1506-275 (S) Unexpected text ',' encountered. C compiler died! at Configure.pl line 347. -- H.Merijn BrandAmsterdam Perl Mongers (http://amsterdam.pm.org/) using perl-5.6.1, 5.7.2 630 on HP-UX 10.20 11.00, AIX 4.2, AIX 4.3, WinNT 4, Win2K pro WinCE 2.11. Smoking perl CORE: [EMAIL PROTECTED] http:[EMAIL PROTECTED]/ [EMAIL PROTECTED] send smoke reports to: [EMAIL PROTECTED], QA: http://qa.perl.org
AIX 4.2 status
*** PLEASE WRITE PORTABLE CODE, NOT ALL THE WORLD USES GCC *** ibm:/pro/3gl/CPAN/parrot-current 102 perl Configure.pl --default Parrot Configure Copyright (C) 2001 Yet Another Society Since you're running this script, you obviously have Perl 5--I'll be pulling some defaults from its configuration. First, I'm gonna check the manifest, to make sure you got a complete Parrot kit. Okay, we found everything. Next you'll need to answer a few questions about your system. Rules are the same as Perl 5's Configure--defaults are in square brackets, and you can hit enter to accept them. Okay. Now I'm gonna probe Perl 5's configuration to see what headers you have around. This could take a bit on slow machines... Alright, now I'm gonna check some stuff by compiling and running a small C program. This could take a bit... Done. Now I'm figuring out what formats to pass to pack() for the various Parrot internal types. Okay, that's finished. I'm now going to write your very own Makefile, config.h, Parrot::Types, and Parrot::Config to disk. Alright, now I'm gonna check some stuff by compiling and running another small C program. This could take a bit... ./include/parrot/vtable.h, line 1: 1506-229 (W) File is empty. ./include/parrot/pmc.h, line 54.33: 1506-046 (S) Syntax error. C compiler died! at Configure.pl line 347. ibm:/pro/3gl/CPAN/parrot-current 103 -- H.Merijn BrandAmsterdam Perl Mongers (http://amsterdam.pm.org/) using perl-5.6.1, 5.7.2 630 on HP-UX 10.20 11.00, AIX 4.2, AIX 4.3, WinNT 4, Win2K pro WinCE 2.11. Smoking perl CORE: [EMAIL PROTECTED] http:[EMAIL PROTECTED]/ [EMAIL PROTECTED] send smoke reports to: [EMAIL PROTECTED], QA: http://qa.perl.org
Re: [PATCH classes/perlnum.pmc] Use C please, not C++.
On Wed 28 Nov 2001 17:43, Michael Maraist [EMAIL PROTECTED] wrote:
While your point is taken, it's hardly considered C++ anymore. Many
C-compilers have adopted many such useful features.
True, but many also have not. Try to program defensive, one might want to
compile it on a cray that has no gcc.
On Wed, 28 Nov 2001, Andy Dougherty wrote:
diff -r -u parrot-current/classes/perlnum.pmc parrot-andy/classes/perlnum.pmc
void set_integer (PMC* value) {
-//SELF-vtable = (Parrot_base_vtables[enum_class_PerlInt]);
+ /* SELF-vtable = (Parrot_base_vtables[enum_class_PerlInt]); */
SELF-cache.num_val = (FLOATVAL)value-vtable-get_integer(INTERP, value);
}
-Michael
--
H.Merijn BrandAmsterdam Perl Mongers (http://amsterdam.pm.org/)
using perl-5.6.1, 5.7.2 630 on HP-UX 10.20 11.00, AIX 4.2, AIX 4.3,
WinNT 4, Win2K pro WinCE 2.11. Smoking perl CORE: [EMAIL PROTECTED]
http:[EMAIL PROTECTED]/ [EMAIL PROTECTED]
send smoke reports to: [EMAIL PROTECTED], QA: http://qa.perl.org
HP-UX 11.00 status update
Since reports were pretty discouraging, just looked into the log again 1. Could you consider *not* throwing away 'mktest.???' on make distclean? for the moment, I've changed the mktest.pl to redirect the test output to the smoke directory, and changed mkovz.pl to get it there. 2. Where has the timestamp gone? rsync gets it, but make distclean throws it away :( 5488 -rw-r--r-- 1 merijn softwr824 Nov 26 09:00 global_setup.c 3. Warnings # perl Configure.pl --default : cc: core_ops.c, line 2361: warning 604: Pointers are not assignment-compatible. cc: core_ops.c, line 2370: warning 604: Pointers are not assignment-compatible. : 4. And now for the good news :) Automated smoke report for patch Nov 27 14:00:02 2001 UTC v0.02 on hpux - 11.00 using cc version B.11.11.02 O = OK F = Failure(s), extended report at the bottom ? = still running or test results not (yet) available Build failures during: - = unknown c = Configure, m = make, t = make test-prep Configuration --- O O O O nv=double O O iv=int O O iv=int --define nv=double O O iv=long O O iv=long --define nv=double | | | +- --debugging +--- normal -- H.Merijn BrandAmsterdam Perl Mongers (http://amsterdam.pm.org/) using perl-5.6.1, 5.7.2 630 on HP-UX 10.20 11.00, AIX 4.2, AIX 4.3, WinNT 4, Win2K pro WinCE 2.11. Smoking perl CORE: [EMAIL PROTECTED] http:[EMAIL PROTECTED]/ [EMAIL PROTECTED] send smoke reports to: [EMAIL PROTECTED], QA: http://qa.perl.org
HP-UX 11.00 back on track again
Automated smoke report for patch Oct 28 20:00:01 2001 UTC v0.02 on hpux using cc version B.11.11.02 O = OK F = Failure(s), extended report at the bottom ? = still running or test results not (yet) available Build failures during: - = unknown c = Configure, m = make, t = make test-prep Configuration --- O O O O nv=double O O iv=int O O iv=int --define nv=double O O iv=long O O iv=long --define nv=double | | | +- --debugging +--- normal -- H.Merijn BrandAmsterdam Perl Mongers (http://www.amsterdam.pm.org/) using perl-5.6.1, 5.7.2 629 on HP-UX 10.20 11.00, AIX 4.2, AIX 4.3, WinNT 4, Win2K pro WinCE 2.11. Smoking perl CORE: [EMAIL PROTECTED] http:[EMAIL PROTECTED]/ [EMAIL PROTECTED] send smoke reports to: [EMAIL PROTECTED], QA: http://qa.perl.org
HP-UX 11.00 still not happy
l1:/pro/3gl/CPAN/parrot-current 102 make distclean perl -MExtUtils::Manifest=filecheck -le 'xtUtils::Manifest::Quiet=1;unlink for filecheck()' Undefined subroutine xtUtils::Manifest::Quiet called at -e line 1. make: *** [distclean] Error 255 l1:/pro/3gl/CPAN/parrot-current 103 rm -f *.o *.a l1:/pro/3gl/CPAN/parrot-current 104 perl Co Config_pm.in Configure.pl l1:/pro/3gl/CPAN/parrot-current 104 perl Configure.pl --default : l1:/pro/3gl/CPAN/parrot-current 105 make test_prog perl vtable_h.pl : cc -DDEBUGGING -Ae -D_HPUX_SOURCE -I/pro/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I./include -o stacks.o -c stacks.c cc: stacks.c, line 105: warning 604: Pointers are not assignment-compatible. : cc -DDEBUGGING -Ae -D_HPUX_SOURCE -I/pro/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I./include -o vtable_ops.o -c vtable_ops.c cc: vtable_ops.c, line 37: error 1534: Illegal to use a function pointer as + operand where an arithmetic type is required. cc: vtable_ops.c, line 37: error 1533: Illegal function call. cc: vtable_ops.c, line 43: error 1534: Illegal to use a function pointer as + operand where an arithmetic type is required. cc: vtable_ops.c, line 43: error 1533: Illegal function call. cc: vtable_ops.c, line 49: error 1534: Illegal to use a function pointer as + operand where an arithmetic type is required. cc: vtable_ops.c, line 49: error 1533: Illegal function call. cc: vtable_ops.c, line 55: error 1534: Illegal to use a function pointer as + operand where an arithmetic type is required. cc: vtable_ops.c, line 55: error 1533: Illegal function call. cc: vtable_ops.c, line 61: error 1534: Illegal to use a function pointer as + operand where an arithmetic type is required. cc: vtable_ops.c, line 61: error 1533: Illegal function call. cc: vtable_ops.c, line 67: error 1534: Illegal to use a function pointer as + operand where an arithmetic type is required. cc: vtable_ops.c, line 67: error 1533: Illegal function call. make: *** [vtable_ops.o] Error 1 l1:/pro/3gl/CPAN/parrot-current 106 cat .timestamp 1003950001 Wed Oct 24 19:00:01 2001 UTC (time of this cvs update) l1:/pro/3gl/CPAN/parrot-current 107 -- H.Merijn BrandAmsterdam Perl Mongers (http://www.amsterdam.pm.org/) using perl-5.6.1, 5.7.2 629 on HP-UX 10.20 11.00, AIX 4.2, AIX 4.3, WinNT 4, Win2K pro WinCE 2.11. Smoking perl CORE: [EMAIL PROTECTED] http:[EMAIL PROTECTED]/ [EMAIL PROTECTED] send smoke reports to: [EMAIL PROTECTED], QA: http://qa.perl.org
Re: Revamping the build system
On Tue 23 Oct 2001 14:51, Bart Lateur [EMAIL PROTECTED] wrote: On Tue, 23 Oct 2001 08:39:29 -0400, John Siracusa wrote: As one of the few rabid Mac users on this list, let me just say that I personally have no problem with classic Mac OS support being totally dropped from Parrot if it'll get stuff out the door sooner :) Classic Mac OS is (somewhat sadly) a dead OS at this point. By the time Parrot is done, Apple will probably be shipping hardware that won't even *boot* classic Mac OS outside of a virtual machine in OS X. I disagree. OS X is but slowly catching on. You may drop 68k support if you want, but please don't drop MacOS 8.x/9.x for PPC. Those Macs aren't dead yet, and most of them will never be upgraded to OS X. FWIW we've got a fully functional fully productional Mac OS7 running here. Not that I have any plans of running parrot and or perl on that machine, nor do I have any plans in upgrading *any* software on that box. All upgrades for any Mac software we'd /like/ to upgrade are minimal requirements Mac OS 8, so we're out of luck there. But I am not happy of having to use a proprietary mechanism for building things. -- H.Merijn BrandAmsterdam Perl Mongers (http://www.amsterdam.pm.org/) using perl-5.6.1, 5.7.2 629 on HP-UX 10.20 11.00, AIX 4.2, AIX 4.3, WinNT 4, Win2K pro WinCE 2.11. Smoking perl CORE: [EMAIL PROTECTED] http:[EMAIL PROTECTED]/ [EMAIL PROTECTED] send smoke reports to: [EMAIL PROTECTED], QA: http://qa.perl.org
Smoking
Last success was Automated smoke report for patch Oct 20 19:00:01 2001 UTC v0.02 on hpux using cc version B.11.11.02 O = OK F = Failure(s), extended report at the bottom ? = still running or test results not (yet) available Build failures during: - = unknown c = Configure, m = make, t = make test-prep Configuration --- O O O O nv=double O O iv=int O O iv=int --define nv=double O O iv=long O O iv=long --define nv=double | | | +- --debugging +--- normal After that it was a no-go. FYI: l1:/pro/3gl/CPAN/parrot-current 102 make distclean ; rm -f *.[oa] perl -MExtUtils::Manifest=filecheck -le 'xtUtils::Manifest::Quiet=1;unlink for filecheck()' Undefined subroutine xtUtils::Manifest::Quiet called at -e line 1. make: *** [distclean] Error 255 l1:/pro/3gl/CPAN/parrot-current 103 Maybe change xtUtils to ExtUtils will help l1:/pro/3gl/CPAN/parrot-current 103 perl Configure.pl --default : (no warnings or errors) l1:/pro/3gl/CPAN/parrot-current 104 make test_prog : cc -DDEBUGGING -Ae -D_HPUX_SOURCE -I/pro/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I./include -o vtable_ops.o -c vtable_ops.c cc: vtable_ops.c, line 37: error 1534: Illegal to use a function pointer as + operand where an arithmetic type is required. cc: vtable_ops.c, line 37: error 1533: Illegal function call. cc: vtable_ops.c, line 43: error 1534: Illegal to use a function pointer as + operand where an arithmetic type is required. cc: vtable_ops.c, line 43: error 1533: Illegal function call. cc: vtable_ops.c, line 49: error 1534: Illegal to use a function pointer as + operand where an arithmetic type is required. cc: vtable_ops.c, line 49: error 1533: Illegal function call. cc: vtable_ops.c, line 55: error 1534: Illegal to use a function pointer as + operand where an arithmetic type is required. cc: vtable_ops.c, line 55: error 1533: Illegal function call. cc: vtable_ops.c, line 61: error 1534: Illegal to use a function pointer as + operand where an arithmetic type is required. cc: vtable_ops.c, line 61: error 1533: Illegal function call. cc: vtable_ops.c, line 67: error 1534: Illegal to use a function pointer as + operand where an arithmetic type is required. cc: vtable_ops.c, line 67: error 1533: Illegal function call. make: *** [vtable_ops.o] Error 1 l1:/pro/3gl/CPAN/parrot-current 105 HTH -- H.Merijn BrandAmsterdam Perl Mongers (http://www.amsterdam.pm.org/) using perl-5.6.1, 5.7.2 629 on HP-UX 10.20 11.00, AIX 4.2, AIX 4.3, WinNT 4, Win2K pro WinCE 2.11. Smoking perl CORE: [EMAIL PROTECTED] http:[EMAIL PROTECTED]/ [EMAIL PROTECTED] send smoke reports to: [EMAIL PROTECTED], QA: http://qa.perl.org
Smokes
Should anything be changed? -- H.Merijn BrandAmsterdam Perl Mongers (http://www.amsterdam.pm.org/) using perl-5.6.1, 5.7.2 629 on HP-UX 10.20 11.00, AIX 4.2, AIX 4.3, WinNT 4, Win2K pro WinCE 2.11. Smoking perl CORE: [EMAIL PROTECTED] http:[EMAIL PROTECTED]/ [EMAIL PROTECTED] send smoke reports to: [EMAIL PROTECTED], QA: http://qa.perl.org ---BeginMessage--- Automated smoke report for patch Oct 14 19:00:01 2001 UTC v0.02 on hpux using cc version B.11.11.02 O = OK F = Failure(s), extended report at the bottom ? = still running or test results not (yet) available Build failures during: - = unknown c = Configure, m = make, t = make test-prep Configuration --- - - - - nv=double - - iv=int - - iv=int --define nv=double - - iv=long - ? iv=long --define nv=double | | | +- --debugging +--- normal ---End Message--- ---BeginMessage--- Automated smoke report for patch Oct 13 13:00:05 2001 UTC v0.02 on hpux using cc version B.11.11.02 O = OK F = Failure(s), extended report at the bottom ? = still running or test results not (yet) available Build failures during: - = unknown c = Configure, m = make, t = make test-prep Configuration --- - - - - nv=double - - iv=int - - iv=int --define nv=double - - iv=long - ? iv=long --define nv=double | | | +- --debugging +--- normal ---End Message--- ---BeginMessage--- Automated smoke report for patch Oct 12 19:00:02 2001 UTC v0.02 on hpux using cc version B.11.11.02 O = OK F = Failure(s), extended report at the bottom ? = still running or test results not (yet) available Build failures during: - = unknown c = Configure, m = make, t = make test-prep Configuration --- - - - - nv=double - - iv=int - - iv=int --define nv=double - - iv=long - ? iv=long --define nv=double | | | +- --debugging +--- normal ---End Message--- ---BeginMessage--- Automated smoke report for patch Oct 11 19:00:02 2001 UTC v0.02 on hpux using cc version B.11.11.02 O = OK F = Failure(s), extended report at the bottom ? = still running or test results not (yet) available Build failures during: - = unknown c = Configure, m = make, t = make test-prep Configuration --- - - - - nv=double - - iv=int - - iv=int --define nv=double - - iv=long - ? iv=long --define nv=double | | | +- --debugging +--- normal ---End Message--- ---BeginMessage--- Automated smoke report for patch Oct 10 13:00:01 2001 UTC v0.02 on hpux using cc version B.11.11.02 O = OK F = Failure(s), extended report at the bottom ? = still running or test results not (yet) available Build failures during: - = unknown c = Configure, m = make, t = make test-prep Configuration --- O O O O nv=double O O iv=int O O iv=int --define nv=double O O iv=long O O iv=long --define nv=double | | | +- --debugging +--- normal ---End Message---
Parrot Smoke Oct 10 13:00:01 2001 UTC hpux 11.00
This is the first. Be prepared for daily reports for more systems :) Automated smoke report for patch Oct 10 13:00:01 2001 UTC v0.02 on hpux using cc version B.11.11.02 O = OK F = Failure(s), extended report at the bottom ? = still running or test results not (yet) available Build failures during: - = unknown c = Configure, m = make, t = make test-prep Configuration --- O O O O nv=double O O iv=int O O iv=int --define nv=double O O iv=long O O iv=long --define nv=double | | | +- --debugging +--- normal
Re: Parrot 0.0.2
On Wed 03 Oct 2001 16:55, Simon Cozens [EMAIL PROTECTED] wrote: Any objections to a release today? How's Cygwin and Win32 looking? HP-UX 11.00 w/ HP ANSI C -DDEBUGGING -Ae -D_HPUX_SOURCE -I/pro/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I./include l1:/pro/3gl/CPAN/parrot 112 make test perl t/harness t/op/basic..ok, 1/5 skipped: label constants unimplemented in assembler t/op/bitwiseok t/op/integerok t/op/number.ok t/op/stacks.ok, 3/9 skipped: various reasons t/op/string.ok, 1/10 skipped: TODO: printing empty string reg segfaults t/op/time...ok t/op/trans..ok All tests successful, 5 subtests skipped. Files=8, Tests=99, 32 wallclock secs (22.42 cusr + 4.59 csys = 27.01 CPU) l1:/pro/3gl/CPAN/parrot 113 -- H.Merijn BrandAmsterdam Perl Mongers (http://www.amsterdam.pm.org/) using perl-5.6.1, 5.7.1 629 on HP-UX 10.20 11.00, AIX 4.2, AIX 4.3, WinNT 4, Win2K pro WinCE 2.11. Smoking perl CORE: [EMAIL PROTECTED] http:[EMAIL PROTECTED]/ [EMAIL PROTECTED] send smoke reports to: [EMAIL PROTECTED], QA: http://qa.perl.org
Re: Tru64 core dumps
On Wed 26 Sep 2001 19:00, Andy Dougherty [EMAIL PROTECTED] wrote:
On Wed, 26 Sep 2001, Brent Dax wrote:
Configure Man To The Rescue! (Trumpets sound, then stop abruptly.)
Now, how do I figure out if we're on a 64-bit system? :^)
ivsize, nvsize, ptrsize, and opcode_t_size (as yet uncomputed, but will be
needed) come to mind. A '64-bit' system is an imprecise term. Many
systems can have multiple personalities, depending upon compiler flags and
other odd incantations.
from the gcc tests in hints/hpux.sh I once fiddled up this code:
echo 'int main(){long l;printf(%d\\n,sizeof(l));}'try.c
$cc -o try $ccflags $ldflags try.c
if [ `try` = 8 ]; then
cat EOM 4
*** This version of gcc uses 64 bit longs. -Duse64bitall is
*** implicitly set to enable continuation
EOM
use64bitall=$define
gcc_64native=yes
Might that be of any help?
--
H.Merijn BrandAmsterdam Perl Mongers (http://www.amsterdam.pm.org/)
using perl-5.6.1, 5.7.1 629 on HP-UX 10.20 11.00, AIX 4.2, AIX 4.3,
WinNT 4, Win2K pro WinCE 2.11. Smoking perl CORE: [EMAIL PROTECTED]
http:[EMAIL PROTECTED]/ [EMAIL PROTECTED]
send smoke reports to: [EMAIL PROTECTED], QA: http://qa.perl.org
Re: Parrot Smoke Sep 21 07:00:01 2001 UTC dec_osf 4.0 (fwd)
On Fri 21 Sep 2001 11:45, Mattia Barbon [EMAIL PROTECTED] wrote: It is gcc 2.95.2, not 2.8.1 *SMACK* to anyone kept the perl scripts compatible with perl 5.004_04 Regards Mattia P.S.: Suggstions about how to make report lins shorter *VERY* welcome Start with stripping '--define' and '--defaults' from the report Now for a different question. What reports would the parrot team be more interested in? [ ] The complex matrix for four systems multiple compilers based on bleadperl like I post on p5p, filtered like Mattia does in this smoke [ ] Just 6 reports completely based on Mattia's smoke based on perl5.6.1 -- H.Merijn BrandAmsterdam Perl Mongers (http://www.amsterdam.pm.org/) using perl-5.6.1, 5.7.1 629 on HP-UX 10.20 11.00, AIX 4.2, AIX 4.3, WinNT 4, Win2K pro WinCE 2.11. Smoking perl CORE: [EMAIL PROTECTED] http:[EMAIL PROTECTED]/ [EMAIL PROTECTED] send smoke reports to: [EMAIL PROTECTED], QA: http://qa.perl.org
Re: Feature Freeze
On Thu 20 Sep 2001 15:49, Simon Cozens [EMAIL PROTECTED] wrote: On Thu, Sep 20, 2001 at 09:00:20AM +0100, Simon Cozens wrote: So, if you're running on one of the core platforms, please check out a *clean* CVS copy, try and build and post the output of make test. FWIW, here's the current state of Tru64: Failed TestStat Wstat Total Fail Failed List of Failed --- t/op/integer.t4 1024264 15.38% 1 3 21 23 t/op/number.t21 537623 21 91.30% 1-19 21 23 t/op/trans.t 18 460818 18 100.00% 1-18 4 subtests skipped. Failed 3/5 test scripts, 40.00% okay. 43/74 subtests failed, 41.89% okay. I did let it run for some time to get a more complete picture :) Here's the results from the Dutch HP-UX 11.00 jury running bleadperl for Parrot snap 20 Sep 2001 09:00 Configuration: -Dusedevel -Uuseperlio === ../perl t/harness t/op/basic..ok, 1/2 skipped: label constants unimplemented in assembler t/op/integerok t/op/number.Confused test output: test 2 answered after test 6 Test output counter mismatch [test 7] Confused test output: test 2 answered after test 7 Test output counter mismatch [test 8] Confused test output: test 2 answered after test 8 Test output counter mismatch [test 9] Confused test output: test 2 answered after test 9 Test output counter mismatch [test 10] Confused test output: test 2 answered after test 10 Test output counter mismatch [test 11] Confused test output: test 2 answered after test 11 Test output counter mismatch [test 12] Confused test output: test 2 answered after test 12 Test output counter mismatch [test 13] Confused test output: test 2 answered after test 13 Test output counter mismatch [test 14] Confused test output: test 2 answered after test 14 Test output counter mismatch [test 15] Confused test output: test 2 answered after test 15 Test output counter mismatch [test 16] Confused test output: test 2 answered after test 16 Test output counter mismatch [test 17] Confused test output: test 2 answered after test 17 Test output counter mismatch [test 18] Confused test output: test 2 answered after test 18 Test output counter mismatch [test 19] dubious Test returned status 21 (wstat 5376, 0x1500) DIED. FAILED tests 1-19, 21, 23 Failed 21/23 tests, 8.70% okay (-2 skipped tests: 0 okay, 0.00%) t/op/string.ok, 1/5 skipped: I'm unable to write it! t/op/trans..dubious Test returned status 2 (wstat 512, 0x200) DIED. FAILED tests 13, 18 Failed 2/18 tests, 88.89% okay Failed Test Stat Wstat Total Fail Failed List of Failed --- t/op/number.t 21 537623 142 617.39% 1-19 21 23 t/op/trans.t 2 512182 11.11% 13 18 4 subtests skipped. For all next configurations I manually removed the line noise ... Configuration: -Dusedevel -Uuseperlio === t/op/basic..ok, 1/2 skipped: label constants unimplemented in assembler t/op/integerok t/op/number. DIED. FAILED tests 1-19, 21, 23 t/op/string.ok, 1/5 skipped: I'm unable to write it! t/op/trans.. DIED. FAILED tests 13, 18 Failed Test Stat Wstat Total Fail Failed List of Failed --- t/op/number.t 21 537623 142 617.39% 1-19 21 23 t/op/trans.t 2 512182 11.11% 13 18 4 subtests skipped. Configuration: -DDEBUGGING -Dusedevel -Uuseperlio === t/op/basic..ok, 1/2 skipped: label constants unimplemented in assembler t/op/integerok t/op/number. DIED. FAILED tests 1-19, 21, 23 t/op/string.ok, 1/5 skipped: I'm unable to write it! t/op/trans.. DIED. FAILED tests 13, 18 Failed Test Stat Wstat Total Fail Failed List of Failed --- t/op/number.t 21 537623 142 617.39% 1-19 21 23 t/op/trans.t 2 512182 11.11% 13 18 4 subtests skipped. Configuration: -DDEBUGGING -Dusedevel -Uuseperlio === t/op/basic..ok, 1/2 skipped: label constants unimplemented in assembler t/op/integerok t/op/number. DIED. FAILED tests 1-19, 21, 23 t/op/string.ok, 1/5 skipped: I'm unable to write it! t/op/trans.. DIED. FAILED tests 13, 18 Failed Test Stat Wstat Total Fail Failed List of Failed --- t/op/number.t 21 537623 142 617.39% 1-19 21 23 t/op/trans.t 2 512182 11.11% 13 18 4 subtests skipped. Configuration: -Dusedevel -Duseperlio
Re: The core platforms list
On Wed 19 Sep 2001 11:15, H.Merijn Brand [EMAIL PROTECTED] wrote:
On Tue 18 Sep 2001 20:43, Dan Sugalski [EMAIL PROTECTED] wrote:
Okay, folks, the following platforms are considered core for the parrot
interpreter. That means we need to run on all of them for any release of
the interpreter to be considerd OK. They are:
Linux (x86)
CygWin
Win32
Tru64
OpenVMS (Alpha)
Solaris (Sparc)
FreeBSD (x86)
If a platform's not here it's not because we don't want to run on it,
rather it's because we can't guarantee the manpower to make it right. (If
we can, then new platforms can and will come on board)
So remember, all the world is not *X*, for any value of X you might have...
And, maybe even more important, not all the world has gcc!
in build_interp_starter.pl I find:
--8---
#define DO_OP(w,x,y,z) do { \\
x = (void *)z-opcode_funcs; \\
(void *)y = x[*w]; \\
w = (y)(w,z); \\
} while (0);
EOI
--8---
(cast)foo = bar; syntax is *not* supported in most non-GNU C compilers:
cc -DDEBUGGING -Ae -D_HPUX_SOURCE -I/pro/local/include -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 -I.. -I./include -g -o interpreter.o -c interpreter.c
cc: interpreter.c, line 44: warning 524: Cast (non-lvalue) appears on left-hand side
of assignment.
cc: interpreter.c, line 44: error 1549: Modifiable lvalue required for assignment
operator.
(Almost the same applies to AIX)
Please fix ASAP, so I can send useful test reports ;)
If the nightly builds start OK, I could add a daily report for
HP-UX 11.00 HPc/gcc 32/64 threading/non-threading
HP-UX 10.20 HPc 32threading/non-threading
AIX 4.3.3 vac/gcc 32/64 threading/non-threading
AIX 4.2.1 xlc 32threading/non-threading
If that's what it takes to get it on the list.
--
H.Merijn BrandAmsterdam Perl Mongers (http://www.amsterdam.pm.org/)
using perl-5.6.1, 5.7.1 629 on HP-UX 10.20 11.00, AIX 4.2, AIX 4.3,
WinNT 4, Win2K pro WinCE 2.11. Smoking perl CORE: [EMAIL PROTECTED]
http:[EMAIL PROTECTED]/ [EMAIL PROTECTED]
send smoke reports to: [EMAIL PROTECTED], QA: http://qa.perl.org
--
H.Merijn BrandAmsterdam Perl Mongers (http://www.amsterdam.pm.org/)
using perl-5.6.1, 5.7.1 629 on HP-UX 10.20 11.00, AIX 4.2, AIX 4.3,
WinNT 4, Win2K pro WinCE 2.11. Smoking perl CORE: [EMAIL PROTECTED]
http:[EMAIL PROTECTED]/ [EMAIL PROTECTED]
send smoke reports to: [EMAIL PROTECTED], QA: http://qa.perl.org
Re: The core platforms list
On Wed 19 Sep 2001 13:10, H.Merijn Brand [EMAIL PROTECTED] wrote: And, maybe even more important, not all the world has gcc! and bytecode.c l1:/pro/3gl/CPAN/parrot 136 make test_prog cc -DDEBUGGING -Ae -D_HPUX_SOURCE -I/pro/local/include -D_LARGEFILE_SOURCE -D_FI LE_OFFSET_BITS=64 -I.. -I./include -g -o bytecode.o -c bytecode.c cc: bytecode.c, line 53: warning 603: Cast is not lvalue; ++ requires lvalue. cc: bytecode.c, line 53: error 1560: Modifiable lvalue required with operator ++. which comes from #define GRAB_IV(x) *((IV*)*x)++ OK, switching to gcc, just because I'm curious ;) l1:/pro/3gl/CPAN/parrot 149 make test_prog perl make_op_header.pl opcode_table op.h gcc -DDEBUGGING -D_HPUX_SOURCE -I/pro/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I.. -I./include -o test_main.o -c test_main.c gcc -DDEBUGGING -D_HPUX_SOURCE -I/pro/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I.. -I./include -o global_setup.o -c global_setup.c perl build_interp_starter.pl gcc -DDEBUGGING -D_HPUX_SOURCE -I/pro/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I.. -I./include -o interpreter.o -c interpreter.c gcc -DDEBUGGING -D_HPUX_SOURCE -I/pro/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I.. -I./include -o parrot.o -c parrot.c gcc -DDEBUGGING -D_HPUX_SOURCE -I/pro/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I.. -I./include -o register.o -c register.c perl process_opfunc.pl basic_opcodes.ops gcc -DDEBUGGING -D_HPUX_SOURCE -I/pro/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I.. -I./include -o basic_opcodes.o -c basic_opcodes.c gcc -DDEBUGGING -D_HPUX_SOURCE -I/pro/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I.. -I./include -o memory.o -c memory.c gcc -DDEBUGGING -D_HPUX_SOURCE -I/pro/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I.. -I./include -o bytecode.o -c bytecode.c gcc -DDEBUGGING -D_HPUX_SOURCE -I/pro/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I.. -I./include -o string.o -c string.c gcc -DDEBUGGING -D_HPUX_SOURCE -I/pro/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I.. -I./include -o strnative.o -c strnative.c gcc -lnsl -lnm -lndbm -lgdbm -ldb -ldld -lm -lc -lndir -lcrypt -lsec -o test_prog global_setup.o interpreter.o parrot.o register.o basic_opcodes.o memory.o bytecode.o string.o strnative.o test_main.o l1:/pro/3gl/CPAN/parrot 150 make test perl t/harness Can't open perl script t/harness: No such file or directory make: *** [test] Error 2 l1:/pro/3gl/CPAN/parrot 151 test_prog Warning: Bytecode does not include opcode table fingerprint! l1:/pro/3gl/CPAN/parrot 152 MANIFEST? (using most recent parrot-nightly) -- H.Merijn BrandAmsterdam Perl Mongers (http://www.amsterdam.pm.org/) using perl-5.6.1, 5.7.1 629 on HP-UX 10.20 11.00, AIX 4.2, AIX 4.3, WinNT 4, Win2K pro WinCE 2.11. Smoking perl CORE: [EMAIL PROTECTED] http:[EMAIL PROTECTED]/ [EMAIL PROTECTED] send smoke reports to: [EMAIL PROTECTED], QA: http://qa.perl.org
Re: The core platforms list
On Wed 19 Sep 2001 16:43, Dan Sugalski [EMAIL PROTECTED] wrote: At 11:15 AM 9/19/2001 +0200, H.Merijn Brand wrote: If the nightly builds start OK, I could add a daily report for HP-UX 11.00 HPc/gcc 32/64 threading/non-threading HP-UX 10.20 HPc 32threading/non-threading AIX 4.3.3 vac/gcc 32/64 threading/non-threading AIX 4.2.1 xlc 32threading/non-threading If that's what it takes to get it on the list. The daily reports are cool, but it takes more than those to get on the list. We also need someone who can fix the breakage. Once we have that... :) I cannot promise anything, but when the 'make test' results drip in, one might never know how enthousiatic I might become ;) -- H.Merijn BrandAmsterdam Perl Mongers (http://www.amsterdam.pm.org/) using perl-5.6.1, 5.7.1 629 on HP-UX 10.20 11.00, AIX 4.2, AIX 4.3, WinNT 4, Win2K pro WinCE 2.11. Smoking perl CORE: [EMAIL PROTECTED] http:[EMAIL PROTECTED]/ [EMAIL PROTECTED] send smoke reports to: [EMAIL PROTECTED], QA: http://qa.perl.org
HP-UX first test results
HP-UX 11.00, HPc B.11.11.23709.GP, perl-5.7.2@12053 DEBUGGING USE_64_BIT_INT USE_64_BIT_ALL USE_LARGE_FILES -- H.Merijn BrandAmsterdam Perl Mongers (http://www.amsterdam.pm.org/) using perl-5.6.1, 5.7.1 629 on HP-UX 10.20 11.00, AIX 4.2, AIX 4.3, WinNT 4, Win2K pro WinCE 2.11. Smoking perl CORE: [EMAIL PROTECTED] http:[EMAIL PROTECTED]/ [EMAIL PROTECTED] send smoke reports to: [EMAIL PROTECTED], QA: http://qa.perl.org parrot.log.gz
Re: HP-UX first test results
On Wed 19 Sep 2001 18:53, Simon Cozens [EMAIL PROTECTED] wrote: On Wed, Sep 19, 2001 at 06:37:22PM +0200, H. Merijn Brand wrote: HP-UX 11.00, HPc B.11.11.23709.GP, perl-5.7.2@12053 DEBUGGING USE_64_BIT_INT USE_64_BIT_ALL USE_LARGE_FILES Wow, that one sucked. Betcha it's a problem with pack() and IV size. Beware! I just embedded it in my bleadperl smoke, so it'll be tested about 256 times every day as of tonight for the snapshot available at 22:54 local dutch time. -- H.Merijn BrandAmsterdam Perl Mongers (http://www.amsterdam.pm.org/) using perl-5.6.1, 5.7.1 629 on HP-UX 10.20 11.00, AIX 4.2, AIX 4.3, WinNT 4, Win2K pro WinCE 2.11. Smoking perl CORE: [EMAIL PROTECTED] http:[EMAIL PROTECTED]/ [EMAIL PROTECTED] send smoke reports to: [EMAIL PROTECTED], QA: http://qa.perl.org
Re: cvs snapshots
On Tue 18 Sep 2001 10:52, Mattia Barbon [EMAIL PROTECTED] wrote: On Tue, 18 Sep 2001, H.Merijn Brand wrote: On Mon 17 Sep 2001 23:08, Ask Bjoern Hansen [EMAIL PROTECTED] wrote: oops, I forgot to tell anyone. I made CVS export and tar up a snapshot every 6 hours. It is available at http://cvs.perl.org/snapshots/parrot/ Any chance on rsync? If so, I might set up another smoke suite to bother you with reports :) I wantd it too ( just waited for the Win32 changes to be integrated int the perl one, to do a thing at a time ), but I can start sooner, of course If Mattia keeps the test suite in shape, I /will/ try to initiate a smoke. At first this sounds simple, but when the base conf uses the perl conf that is used for the perl that is called on configure.pl, I will either have to change some of the flags used (for 64bit env's) or rebuilt perl for each parrot smoke. Which in fact would be fun to integrate into the bleadperl smoke :) that is, test parrot for every bleadperl conf tested. H, think, think, think ... Now you can do perl Configure.pl --defaults --define ccflags=... --define ld=cc --define cc=gcc --define libs=-lfoo for each and every flag, and they will ovrride the perl ones ( in fact I use this to compile a MinGW parrot using ActivePerl ) And yes, I was thinking of smoke when I submitted that patch... WRT smoking, I can made a Parrot smoking suite modifying the perl one, since I have lots of time ( it's nice to be a student :-) ) Consider it your's :) I will try to *integrate* it in my hybrid perl5 smoke and test parrot for every bleadperl configuration. Yummie, sounds like fun. Now only I have to enable the Unix host to connect to cvs.perl.org (everything is closed), but I managed for ftp.linux.activestate.com, and I'll manage again! -- H.Merijn BrandAmsterdam Perl Mongers (http://www.amsterdam.pm.org/) using perl-5.6.1, 5.7.1 629 on HP-UX 10.20 11.00, AIX 4.2, AIX 4.3, WinNT 4, Win2K pro WinCE 2.11. Smoking perl CORE: [EMAIL PROTECTED] http:[EMAIL PROTECTED]/ [EMAIL PROTECTED] send smoke reports to: [EMAIL PROTECTED], QA: http://qa.perl.org
Re: cvs snapshots
On Tue 18 Sep 2001 00:54, Ask Bjoern Hansen [EMAIL PROTECTED] wrote: On Tue, 18 Sep 2001, H.Merijn Brand wrote: On Mon 17 Sep 2001 23:08, Ask Bjoern Hansen [EMAIL PROTECTED] wrote: oops, I forgot to tell anyone. I made CVS export and tar up a snapshot every 6 hours. It is available at http://cvs.perl.org/snapshots/parrot/ Any chance on rsync? If so, I might set up another smoke suite to bother you with reports :) rsync -av cvs.perl.org::parrot-HEAD parrot it's only updated every 6th hour. Maybe I'll get time to get it to update more often (but not create a snapshot) tonight. From all my machines I get i2:/l1/pro/3gl/CPAN/parrot 104 rsync -avz rsync://cvs.perl.org::parrot-HEAD/ . failed to connect to cvs.perl.org - Can't assign requested address i2:/l1/pro/3gl/CPAN/parrot 105 rsync -avz rsync://216.246.96.150::parrot-HEAD/ . failed to connect to 216.246.96.150 - Can't assign requested address i2:/l1/pro/3gl/CPAN/parrot 106 (And this machine has (temporary) no restrictions to the outside world) ActiveSync rsyncs fine using rsync -avz rsync://ftp.linux.activestate.com/perl-current/ . -- H.Merijn BrandAmsterdam Perl Mongers (http://www.amsterdam.pm.org/) using perl-5.6.1, 5.7.1 629 on HP-UX 10.20 11.00, AIX 4.2, AIX 4.3, WinNT 4, Win2K pro WinCE 2.11. Smoking perl CORE: [EMAIL PROTECTED] http:[EMAIL PROTECTED]/ [EMAIL PROTECTED] send smoke reports to: [EMAIL PROTECTED], QA: http://qa.perl.org
parrot-nightly
I've waited till either Configure or make would do something sensible, and I'm also aware that parrot-nightly isn't stable. Does perl6-internals value input like this (on a regular basis) or not. Either way, is there a point in time that parrot is released as pseodo-stable snapshots like Jarkko does with perl5? l1:/pro/3gl/CPAN/parrot-nightly 106 make perl Configure.pl Parrot Configure Copyright (C) 2001 Yet Another Society Since you're running this script, you obviously have Perl 5--I'll be pulling some defaults from its configuration. First, I'm gonna check the manifest, to make sure you got a complete Parrot kit. Okay, we found everything. Next you'll need to answer a few questions about your system. Rules are the same as Perl 5's Configure--defaults are in square brackets, and you can hit enter to accept them. What C compiler do you want to use? [cc] How about your linker? [ld] What flags would you like passed to your C compiler? [ -DDEBUGGING -Ae -D_HPUX_S OURCE -I/pro/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I.. -I./ include] Which libraries would you like your C compiler to include? [-lnsl -lnm -lndbm -l gdbm -ldb -ldld -lm -lc -lndir -lcrypt -lsec] How big would you like integers to be? [long] And your floats? [double] Okay. Now I'm gonna probe Perl 5's configuration to see what headers you have around. This could take a bit on slow machines... Okay, that's finished. I'm now going to write your very own Makefile, config.h, and Parrot::Config to disk. Okay, we're done! You can now use `make test_prog' (or your platform's equivalent to `make') to build your Parrot. Happy Hacking, The Parrot Team perl make_op_header.pl opcode_table op.h Can't locate Parrot/Opcode.pm in @INC (@INC contains: /pro/lib/perl5/5.6.1/PA-RI SC2.0 /pro/lib/perl5/5.6.1 /pro/lib/perl5/site_perl/5.6.1/PA-RISC2.0 /pro/lib/pe rl5/site_perl/5.6.1 /pro/lib/perl5/site_perl .) at make_op_header.pl line 6. BEGIN failed--compilation aborted at make_op_header.pl line 6. make: *** [op.h] Error 2 l1:/pro/3gl/CPAN/parrot-nightly 107 -- H.Merijn BrandAmsterdam Perl Mongers (http://www.amsterdam.pm.org/) using perl-5.6.1, 5.7.1 629 on HP-UX 10.20 11.00, AIX 4.2, AIX 4.3, WinNT 4, Win2K pro WinCE 2.11. Smoking perl CORE: [EMAIL PROTECTED] http:[EMAIL PROTECTED]/ [EMAIL PROTECTED] send smoke reports to: [EMAIL PROTECTED], QA: http://qa.perl.org
Re: parrot-nightly
On Mon 17 Sep 2001 16:16, Simon Cozens [EMAIL PROTECTED] wrote: That could be because these aren't in the MANIFEST, so didn't get included in the parrot-nightly tarball. I'll fix up the MANIFEST and try another tarball so that it builds here. In fact, try downloading it now. Okay, that's finished. I'm now going to write your very own Makefile, config.h, and Parrot::Config to disk. Okay, we're done! You can now use `make test_prog' (or your platform's equivalent to `make') to build your Parrot. Happy Hacking, The Parrot Team l1:/pro/3gl/CPAN/parrot 108 make test_prog perl make_op_header.pl opcode_table op.h Can't locate Digest/MD5.pm in @INC (@INC contains: /pro/lib/perl5/5.6.1/PA-RISC2.0 /pro/lib/perl5/5.6.1 /pro/lib/perl5/site_perl/5.6.1/PA-RISC2.0 /pro/lib/perl5/site_perl/5.6.1 /pro/lib/perl5/site_perl .) at Parrot/Opcode.pm line 5. BEGIN failed--compilation aborted at Parrot/Opcode.pm line 5. Compilation failed in require at make_op_header.pl line 6. BEGIN failed--compilation aborted at make_op_header.pl line 6. make: *** [op.h] Error 2 l1:/pro/3gl/CPAN/parrot 109 (Should I use bleadperl instead ?-/ blead has MD5 in by default, 5.6 and earlier do not) -- H.Merijn BrandAmsterdam Perl Mongers (http://www.amsterdam.pm.org/) using perl-5.6.1, 5.7.1 629 on HP-UX 10.20 11.00, AIX 4.2, AIX 4.3, WinNT 4, Win2K pro WinCE 2.11. Smoking perl CORE: [EMAIL PROTECTED] http:[EMAIL PROTECTED]/ [EMAIL PROTECTED] send smoke reports to: [EMAIL PROTECTED], QA: http://qa.perl.org
Re: parrot-nightly
On Mon 17 Sep 2001 16:43, Simon Cozens [EMAIL PROTECTED] wrote: On Mon, Sep 17, 2001 at 04:46:30PM +0200, H. Merijn Brand wrote: Can't locate Digest/MD5.pm in @INC (@INC contains: /pro/lib/perl5/5.6.1/PA-RISC2.0 /pro/lib/perl5/5.6.1 /pro/lib/perl5/site_perl/5.6.1/PA-RISC2.0 /pro/lib/perl5/site_perl/5.6.1 /pro/lib/perl5/site_perl .) at Parrot/Opcode.pm line 5. BEGIN failed--compilation aborted at Parrot/Opcode.pm line 5. Compilation failed in require at make_op_header.pl line 6. BEGIN failed--compilation aborted at make_op_header.pl line 6. make: *** [op.h] Error 2 l1:/pro/3gl/CPAN/parrot 109 (Should I use bleadperl instead ?-/ blead has MD5 in by default, 5.6 and earlier do not) Or you could install Digest::MD5. Done. :) I'm not terribly amused by the dependency on it, but I guess that for release versions of Parrot, the opcode header and other autogenerated things will be generated before shipping; much like we do with embed.pl in Perl 5. No problems with that. Just something that should be checked in advance, just like a require in Makefile.PL -- H.Merijn BrandAmsterdam Perl Mongers (http://www.amsterdam.pm.org/) using perl-5.6.1, 5.7.1 629 on HP-UX 10.20 11.00, AIX 4.2, AIX 4.3, WinNT 4, Win2K pro WinCE 2.11. Smoking perl CORE: [EMAIL PROTECTED] http:[EMAIL PROTECTED]/ [EMAIL PROTECTED] send smoke reports to: [EMAIL PROTECTED], QA: http://qa.perl.org
Re: Parrot coredumps on Solaris 8
On Wed 12 Sep 2001 13:23, Nicholas Clark [EMAIL PROTECTED] wrote: Can we usefully smoke parrots yet? Or is this something that someone (Schwern?) is working on? [in that as all the world is not a vax^Wx86 it would be useful to smoke on obscure architectures that SIGBUS on unaligned integer pointers, have structure padding, etc] If someone will set it up, count me in as smoker ;) -- H.Merijn BrandAmsterdam Perl Mongers (http://www.amsterdam.pm.org/) using perl-5.6.1, 5.7.1 629 on HP-UX 10.20 11.00, AIX 4.2, AIX 4.3, WinNT 4, Win2K pro WinCE 2.11. Smoking perl CORE: [EMAIL PROTECTED] http:[EMAIL PROTECTED]/ [EMAIL PROTECTED] send smoke reports to: [EMAIL PROTECTED], QA: http://qa.perl.org
Re: Final draft: Conventions and Guidelines for Perl Source Code
On Tue 14 Aug 2001 00:55, Espen Harlinn [EMAIL PROTECTED] wrote: Pardon me for butting in at this late stage :-) Since the purpose of coding conventions and guidelines is to make code more readable to the majority of developers, wouldn't it make sence to settle on something that can be processed by a utility like gnu indent ??? This way developers could use a coding style they are comfortable with (or close to), and run it through indent with the right set of options and it would be conformant with the upcomming guide lines. It's just a thought ... patches don't run very well through gnu indent ... -- H.Merijn BrandAmsterdam Perl Mongers (http://www.amsterdam.pm.org/) using perl-5.6.1, 5.7.1 623 on HP-UX 10.20 11.00, AIX 4.2, AIX 4.3, WinNT 4, Win2K pro WinCE 2.11 often with Tk800.022 /| DBD-Unify ftp://ftp.funet.fi/pub/languages/perl/CPAN/authors/id/H/HM/HMBRAND/
Re: PDD 2nd go: Conventions and Guidelines for Perl Source Code
On Tue 29 May 2001 19:25, Dave Mitchell [EMAIL PROTECTED] wrote: =item * KR style for indenting control constructs: ie the closing C} should line up with the opening Cif etc. =item * When a conditional spans multiple lines, the opening brace must line up with the if or while, or be at the end-of-line otherwise. I certainly will not change existing code that's written like this, but - since IMHO this is *poor* GNU coding style - I will submit /new/ code snippets formatted my own way: the right way. It's then up to the pumpking to accept or reject it. I'm happy this document does not apply to shell scripts and perl scripts. -- H.Merijn BrandAmsterdam Perl Mongers (http://www.amsterdam.pm.org/) using perl-5.6.1, 5.7.1 626 on HP-UX 10.20 11.00, AIX 4.2, AIX 4.3, WinNT 4, Win2K pro WinCE 2.11 often with Tk800.022 /| DBD-Unify ftp://ftp.funet.fi/pub/languages/perl/CPAN/authors/id/H/HM/HMBRAND/
Re: PDD 2nd go: Conventions and Guidelines for Perl Source Code
On Tue 29 May 2001 19:25, Dave Mitchell [EMAIL PROTECTED] wrote: =head2 Portability Related to extensibility is portability. Perl runs on many, many platforms, and will no doubt be ported to ever more bizarre and obscure ones over time. You should never assume an operating system, processor architecture, endian-ness, word size, or whatever. In particular, don't fall into the any of the following common traps: TBC ... Any suggestions welcome !!! + gcc vs. native compilers + builtin's vs. functions + system updates on include files once (long ago) `repaired' by the gcc installation + what gcc allows isn't always accepted by other compilers (e.g. functions within functions) -- H.Merijn BrandAmsterdam Perl Mongers (http://www.amsterdam.pm.org/) using perl-5.6.1, 5.7.1 626 on HP-UX 10.20 11.00, AIX 4.2, AIX 4.3, WinNT 4, Win2K pro WinCE 2.11 often with Tk800.022 /| DBD-Unify ftp://ftp.funet.fi/pub/languages/perl/CPAN/authors/id/H/HM/HMBRAND/
Re: PDD 2nd go: Conventions and Guidelines for Perl Source Code
On Wed 30 May 2001 16:12, Dave Mitchell [EMAIL PROTECTED] wrote:
KR style for indenting control constructs: ie the closing C} should
line up with the opening Cif etc.
=item *
When a conditional spans multiple lines, the opening brace must line up
with the if or while, or be at the end-of-line otherwise.
I certainly will not change existing code that's written like this, but -
since
IMHO this is *poor* GNU coding style - I will submit /new/ code snippets
formatted my own way: the right way. It's then up to the pumpking to accept or
reject it.
The above two are essentially just rehashes of what's already in
Porting/patching.pod, and seems to reflect existing practice (loosely
speaking).
What do you regard as the 'right' way?
Just to check you're not being mislead by poor wording, the above is
supposed to propose
if (...) {
...
}
if (func (arg)) {
:
}
and
if (...
.
.)
{
}
if (...
...
...) {
:
}
But I know I'm rather alone on this, though I'm not just someone saying: Cause
that looks nice. I have several reasons for dong so and can defend my stance.
--
H.Merijn BrandAmsterdam Perl Mongers (http://www.amsterdam.pm.org/)
using perl-5.6.1, 5.7.1 626 on HP-UX 10.20 11.00, AIX 4.2, AIX 4.3,
WinNT 4, Win2K pro WinCE 2.11 often with Tk800.022 /| DBD-Unify
ftp://ftp.funet.fi/pub/languages/perl/CPAN/authors/id/H/HM/HMBRAND/
Re: PDD 2nd go: Conventions and Guidelines for Perl Source Code
On Wed 30 May 2001 16:29, Graham Barr [EMAIL PROTECTED] wrote: On Wed, May 30, 2001 at 04:23:58PM +0200, H.Merijn Brand wrote: On Wed 30 May 2001 16:12, Dave Mitchell [EMAIL PROTECTED] wrote: ::: But I know I'm rather alone on this, though I'm not just someone saying: Cause that looks nice. I have several reasons for dong so and can defend my stance. Maybe and I am not going to get into a discussion of which is best, but the community has decided to follow the perl5 style (I say that as you seem to be the only one objecting). So saying that you will disregard the preference of the community and do what you like is being less than helpful IMO. As being a past pumpking I know how much work there is involved, and the last thing they want to be doing is spending time reformatting other people code. So please play nicely and at least try to work with others. Review my patches over the last two years, and you'll see I am. But if noone objects, one might get the impression that all agree. Well, I don't, but I not only /have to/ work with others, I also *want* to work with others and do not want to quarrel about a space or two. Let's get the ball rolling ... I've also been involved with patches to GNU programs, and I presume many of you also have. I've also talked to people that *refuse* to submit their code to GNU, cause they make you commit to their horrible format. Point made. Ignore me ... -- H.Merijn BrandAmsterdam Perl Mongers (http://www.amsterdam.pm.org/) using perl-5.6.1, 5.7.1 626 on HP-UX 10.20 11.00, AIX 4.2, AIX 4.3, WinNT 4, Win2K pro WinCE 2.11 often with Tk800.022 /| DBD-Unify ftp://ftp.funet.fi/pub/languages/perl/CPAN/authors/id/H/HM/HMBRAND/
Re: PDD 2nd go: Conventions and Guidelines for Perl Source Code
On Wed 30 May 2001 16:37, Dan Sugalski [EMAIL PROTECTED] wrote: At 04:23 PM 5/30/2001 +0200, H.Merijn Brand wrote: But I know I'm rather alone on this, though I'm not just someone saying: Cause that looks nice. I have several reasons for dong so and can defend my stance. Just to head off potential formatting/code style issues... (And this is *not* directed at anyone in particular) I realize that no matter what style we choose, there will be a good crop of people who won't be thrilled with it. (For the record, we can count me as one, if that makes anyone feel any better :) That's inevitable. Maintaining a consistent style gives a big enough benefit that it's worth the potential discomfort it might cause individuals. AMEN -- H.Merijn BrandAmsterdam Perl Mongers (http://www.amsterdam.pm.org/) using perl-5.6.1, 5.7.1 626 on HP-UX 10.20 11.00, AIX 4.2, AIX 4.3, WinNT 4, Win2K pro WinCE 2.11 often with Tk800.022 /| DBD-Unify ftp://ftp.funet.fi/pub/languages/perl/CPAN/authors/id/H/HM/HMBRAND/
Re: Rare Salt-Water Camel May Be Separate Species
On Wed, 7 Feb 2001 09:17:30 -0500, Joshua N Pritikin [EMAIL PROTECTED] wrote: http://www.nytimes.com/2001/02/07/science/07reuters-camel.html Which is of no use if you don't have a subscriber ID (and do not want to have one) to th NYT, since it is quite useless in europe ... -- H.Merijn Brand Amsterdam Perl Mongers (http://www.amsterdam.pm.org/) using perl-5.005.03, 5.6.0, 5.6.1, 5.7.1 623 on HP-UX 10.20 11.00, AIX 4.2 AIX 4.3, WinNT 4.0 SP-6a, and Win2000pro often with Tk800.022 /| DBD-Unify ftp://ftp.funet.fi/pub/languages/perl/CPAN/authors/id/H/HM/HMBRAND/
Re: Rare Salt-Water Camel May Be Separate Species
On Wed, 7 Feb 2001 15:05:55 +, Simon Cozens [EMAIL PROTECTED] wrote: On Wed, Feb 07, 2001 at 03:33:39PM +0100, H . Merijn Brand wrote: On Wed, 7 Feb 2001 09:17:30 -0500, Joshua N Pritikin [EMAIL PROTECTED] wrote: http://www.nytimes.com/2001/02/07/science/07reuters-camel.html Which is of no use if you don't have a subscriber ID (and do not want to have one) to th NYT, since it is quite useless in europe ... http://news.bbc.co.uk/hi/english/sci/tech/newsid_1156000/1156212.stm :-)) Thanks -- H.Merijn Brand Amsterdam Perl Mongers (http://www.amsterdam.pm.org/) using perl-5.005.03, 5.6.0, 5.6.1, 5.7.1 623 on HP-UX 10.20 11.00, AIX 4.2 AIX 4.3, WinNT 4.0 SP-6a, and Win2000pro often with Tk800.022 /| DBD-Unify ftp://ftp.funet.fi/pub/languages/perl/CPAN/authors/id/H/HM/HMBRAND/
Re: Thought for the day
On Wed, 31 Jan 2001 12:05:46 -0600, Jarkko Hietaniemi [EMAIL PROTECTED] wrote: On Wed, Jan 31, 2001 at 05:55:13PM +, Simon Cozens wrote: Never over-design. Never think "Hmm, maybe somebody would find this useful". Start from what you know people _have_ to have, and try to make that set smaller. When you can make it no smaller, you've reached one point. That's a good point to start from - use that for some real implementation. - Linus Torvalds I've always shaken my head in disbelief when people measure/brag about programming prowess by the number of lines of code written. A true programmer is able to delete lines and still achieve the same functionality while simultaneously making the code shorter and simpler and therefore easier to understand and maintain. i.e. using perl Old RPT script : 1500+ lines perl equivalent: 50 lines with more functionality This is *not* a joke. -- H.Merijn Brand Amsterdam Perl Mongers (http://www.amsterdam.pm.org/) using perl-5.005.03, 5.6.0, 5.6.1, 5.7.1 623 on HP-UX 10.20 11.00, AIX 4.2 AIX 4.3, WinNT 4.0 SP-6a, and Win2000pro often with Tk800.022 /| DBD-Unify ftp://ftp.funet.fi/pub/languages/perl/CPAN/authors/id/H/HM/HMBRAND/
Re: Perl6 Prject Plan / Roadmap
On Sat, 05 Aug 2000 12:54:52 -0400, Dan Sugalski [EMAIL PROTECTED] wrote: At 06:04 PM 8/5/00 +0200, H.Merijn Brand wrote: In the roadmap, there's lot of actions and shamelines as spoken of in the camel herders association meeting. What was also talked about there, was an early release of perl6 to the active CPAN authors, so they would be able to try and implement the new language for their modules. I cannot find this in the timeline's You'll get it at the same time as everyone else, since it'll be out as soon as possible in general. (Assuming you don't mind working with alpha code...) The plan is for an alpha by next TPC. How alpha is, as always, an open question, given that's almost a year off. I know, it's clearly in the timeline. I'm not worried about CPAN authors not getting to what they need, but as mentioned in Monterey, It's also a reassurance to the rest of the world that the CPAN modules are not forgotten. The second thing that should be considered is that a lot of important/heavily used modules depend on other modules (i.e. all DBD's depend on DBI). I just think this should be mentioned in the timeline. -- H.Merijn Brand Amsterdam Perl Mongers (http://www.amsterdam.pm.org/) using perl5.005.03, 5.6.0 516 on HP-UX 10.20, HP-UX 11.00, AIX 4.2, AIX 4.3, DEC OSF/1 4.0 and WinNT 4.0 SP-6a, often with Tk800.022 and/or DBD-Unify ftp://ftp.funet.fi/pub/languages/perl/CPAN/authors/id/H/HM/HMBRAND/
