Halloween release
Melvin Smith
We should be able to reach some sort of minor milestone to
justify it I'm sure.
-Melvin
Leopold Toetsch
Too much in flux currently, though not only one milestone seem to be
near.
> -Melvin
leo
Dan Sugalski
Oct 31, the screaming pumkin release? :) Sounds good -- lets see where we
stand on Monday and go from there.
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
d...@sidhe.org have teddy bears and even
teddy bears get drunk
Leopold Toetsch
> On Wed, 22 Oct 2003, Melvin Smith wrote:
>> I propose a Halloween release. Nothing fancy, just something fun. :)
>> We should be able to reach some sort of minor milestone to
>> justify it I'm sure.
> Oct 31, the screaming pumkin release? :) Sounds good -- lets see where we
> stand on Monday and go from there.
Seems to be Monday today. How are the plans? I've collected a rough list
of changes[1] from 0.0.11 til end of last week, looks quite impressive.
> Dan
leo
[1]
- The Big Move: Parrot source and build files rearanged into sub dirs
- Build imcc as parrot
- Objects more finished
- Delegate vtable methods to bytecode
- Binary multi-method dispatching
- Call bytecode from C
- Extension interface
- Dynamic opcode libraries
- PCC argument flattening
- Experimental network socket interface code and opcodes
- Fix assigned opcode numbers
- Ncurses, postgres, and pcre interface librarys
- More NCI signatures
- Experimental struct handling
- Many new tests and fixes
Dan Sugalski
> I can get the null register access exception support patched in.
And I think I'll have working conditional logic for Forth in, possibly
with access to Parrot's calling conventions. (life.forth has an
interesting ring to it... :)
Dan
Andy Dougherty
> On Wed, 22 Oct 2003, Melvin Smith wrote:
>
> > I propose a Halloween release. Nothing fancy, just something fun. :)
> > We should be able to reach some sort of minor milestone to
> > justify it I'm sure.
>
> Oct 31, the screaming pumkin release? :) Sounds good -- lets see where we
> stand on Monday and go from there.
Well on Solaris, I found a few problems. They don't stand in the way of
"something fun", but they do need fixing.
1. MANIFEST error. imcc/unit.h was missing.
2. Configure.pl warning:
Determining some signal stuff... (sigaction) (setitimer) done.
Determining if your C library has setenv / unsetenv...Use of uninitialized value in string ne at (eval 21) line 91, <IN> chunk 10.
(no) done.
Generating config.h...done.
3. Fatal error in Makefile.
make: Fatal error in reader: Makefile, line 650: Unmatched `)' on line
The problem is the Parrot/Config.pm variable gc_c. Here's what it's set
to:
'gc_c' => '1000 3100 2004 2000 1000SRC)/resources$(O): $(GENERAL_H_FILES) $(SRC)/resources.c
I don't know why it has '1000 3100 2004 2000 1000SRC)' instead of the
expected $(SRC). Anybody have any ideas?
I've fixed that by hand and have started running 'make' and
'make test'. I'll next have a chance to look at the output tomorrow.
--
Andy Dougherty doug...@lafayette.edu
Dan Sugalski
> On Thu, 23 Oct 2003, Dan Sugalski wrote:
>
> > On Wed, 22 Oct 2003, Melvin Smith wrote:
> >
> > > I propose a Halloween release. Nothing fancy, just something fun. :)
> > > We should be able to reach some sort of minor milestone to
> > > justify it I'm sure.
> >
> > Oct 31, the screaming pumkin release? :) Sounds good -- lets see where we
> > stand on Monday and go from there.
>
> Well on Solaris, I found a few problems. They don't stand in the way of
> "something fun", but they do need fixing.
>
> 1. MANIFEST error. imcc/unit.h was missing.
Seems to be fixed.
> 2. Configure.pl warning:
>
> Determining if your C library has setenv / unsetenv...Use of uninitialized value in string ne at (eval 21) line 91, <IN> chunk 10.
> (no) done.
I think this might have something to do with #3:
> 3. Fatal error in Makefile.
> make: Fatal error in reader: Makefile, line 650: Unmatched `)' on line
I missed backwhacking a $ in a heredoc. Fixed and committed.
Andy Dougherty
> On Mon, 27 Oct 2003, Andy Dougherty wrote:
>
> > On Thu, 23 Oct 2003, Dan Sugalski wrote:
> >
> > Determining if your C library has setenv / unsetenv...Use of uninitialized value in string ne at (eval 21) line 91, <IN> chunk 10.
> > (no) done.
>
> I think this might have something to do with #3:
Turns out not. What's partly confusing is buffering. Since stdio and
stderr are buffered differently, it turns out that the error did not
appear near the thing that was triggering it.
Specifically, the problem is ${inline} in config/gen/feature_h/feature_h.in
if (${inline} ne '') {
# . . .
}
but config/auto/inline.pl does
if ($test) {
Configure::Data->set(
inline => $test
);
}
i.e., there is no 'else' clause.
I think the best fix is simply to unconditionally set inline:
diff -r -u parrot-current/config/auto/inline.pl parrot-andy/config/auto/inline.pl
--- parrot-current/config/auto/inline.pl Fri Oct 24 04:40:44 2003
+++ parrot-andy/config/auto/inline.pl Mon Oct 27 16:51:46 2003
@@ -41,9 +41,7 @@
}
}
- if ($test) {
- Configure::Data->set(
- inline => $test
- );
- }
+ Configure::Data->set(
+ inline => $test
+ );
}
Tracking this would have been easier with the following patch:
--- parrot-current/Configure.pl Thu Sep 25 19:00:25 2003
+++ parrot-andy/Configure.pl Mon Oct 27 16:52:58 2003
@@ -16,6 +16,8 @@
use Parrot::BuildUtil;
use Parrot::Configure::RunSteps;
+$| = 1;
+
$parrot_version = parrot_version();
@parrot_version = parrot_version();
--
Andy Dougherty doug...@lafayette.edu
Leopold Toetsch
> Specifically, the problem is ${inline} in config/gen/feature_h/feature_h.in
Applied, thanks,
leo