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
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 h
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
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
# 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/i
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
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 = m
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 = m
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 = m
--- 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
--- 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
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 tha
*** 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 configurat
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 Brand
# 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/vtab
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 = m
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
--- Original Message ---
From:"H.M. Brand" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Date:Sun, 11 Nov 2001 22:57:12 +0100 (MET)
Subject: Parrot Smoke Nov 11 20:00:01 2001 UTC hpux 11.00
Automated smoke report for patch Nov 11 20:00:01 2001
Automated smoke report for patch Nov 8 20:00:00 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 =
Automated smoke report for patch Oct 30 20:02:18 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 =
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 =
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
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 = Config
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
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
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
Bui
On Wed 03 Oct 2001 16:55, Simon Cozens <[EMAIL PROTECTED]> wrote:
> Any objections to a release today? How's Cygwin and Win32 looking?
AIX 4.3.3, vac 5.0.2.1
I had to manually add the -L/... from my config's ldflags to find the required
libs. After that:
i2:/pro/3gl/CPAN/parrot 108 > make test
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
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
On Fri 21 Sep 2001 12:04, "H.Merijn Brand" <[EMAIL PROTECTED]> wrote:
> 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.: Suggst
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
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 c
On Thu 20 Sep 2001 16:55, Andy Dougherty <[EMAIL PROTECTED]> wrote:
> On Thu, 20 Sep 2001, Philip Kendall wrote:
>
> > What version of Perl are we requiring to bootstrap Parrot? At the
> > moment, things fail with 5.005 because:
> >
> > 2) The use of `!' to pack() in the assembler.
>
> Oops. M
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, tha
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.1
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
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..
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
> > t
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
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
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
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.
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, th
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 d
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
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
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
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
On Wed 30 May 2001 16:12, Dave Mitchell <[EMAIL PROTECTED]> wrote:
> > > "K&R" style for indenting control constructs: ie the closing C<}> should
> > > line up with the opening C etc.
> > >
> > > =item *
> > >
> > > When a conditional spans multiple lines, the opening brace must line up
> > > wi
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, pr
On Tue 29 May 2001 19:25, Dave Mitchell <[EMAIL PROTECTED]> wrote:
> =item *
>
> "K&R" style for indenting control constructs: ie the closing C<}> should
> line up with the opening C etc.
>
> =item *
>
> When a conditional spans multiple lines, the opening brace must line up
> with the "if" or
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/0
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 Bran
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
> >
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
55 matches
Mail list logo
