Re: Almost, but not quite, there

2003-10-24 Thread Dan Sugalski 
On Thu, 23 Oct 2003, Simon Glover wrote:


 On Thu, 23 Oct 2003, Dan Sugalski wrote:

  At 4:43 PM -0400 10/23/03, Dan Sugalski wrote:
  And I could certainly do with some help at this point.
  
  Parrot is *almost* put back together. There's some weird linking problem
  that's keeping parrot from working out as it should, and I've not been
  able to track it down. If anyone feels like syncing up and giving it a
  shot, I'd not mind it at all.
 
  And now we're fine, and even test good with the JIT. Woohoo!
 
  Time to thump it some and see what I missed.

  Well, I've just stumbled across one problem: if you run Configure
  with --ask, then it won't accept its own default list of ops files.
  The problem is this bit of config/inter/ops.pl:

I applied a variant that should be a bit more robust for cross-platform
use. Thanks for the catch.

Dan

--it's like this---
Dan Sugalski  even samurai
[EMAIL PROTECTED] have teddy bears and even
  teddy bears get drunk

Almost, but not quite, there

2003-10-23 Thread Dan Sugalski 
And I could certainly do with some help at this point.

Parrot is *almost* put back together. There's some weird linking problem
that's keeping parrot from working out as it should, and I've not been
able to track it down. If anyone feels like syncing up and giving it a
shot, I'd not mind it at all.

Dan

--it's like this---
Dan Sugalski  even samurai
[EMAIL PROTECTED] have teddy bears and even
  teddy bears get drunk

Re: Almost, but not quite, there

2003-10-23 Thread Dan Sugalski 
At 4:43 PM -0400 10/23/03, Dan Sugalski wrote:
And I could certainly do with some help at this point.

Parrot is *almost* put back together. There's some weird linking problem
that's keeping parrot from working out as it should, and I've not been
able to track it down. If anyone feels like syncing up and giving it a
shot, I'd not mind it at all.
And now we're fine, and even test good with the JIT. Woohoo!

Time to thump it some and see what I missed.
--
Dan
--it's like this---
Dan Sugalski  even samurai
[EMAIL PROTECTED] have teddy bears and even
  teddy bears get drunk

Re: Almost, but not quite, there

2003-10-23 Thread Simon Glover 

On Thu, 23 Oct 2003, Dan Sugalski wrote:

 At 4:43 PM -0400 10/23/03, Dan Sugalski wrote:
 And I could certainly do with some help at this point.
 
 Parrot is *almost* put back together. There's some weird linking problem
 that's keeping parrot from working out as it should, and I've not been
 able to track it down. If anyone feels like syncing up and giving it a
 shot, I'd not mind it at all.
 
 And now we're fine, and even test good with the JIT. Woohoo!
 
 Time to thump it some and see what I missed.

 Well, I've just stumbled across one problem: if you run Configure
 with --ask, then it won't accept its own default list of ops files.
 The problem is this bit of config/inter/ops.pl:

 {
  $ops=prompt('Which opcode files would you like?', $ops);
  
  if($ops !~ m{^\s*core\.ops}) {
print core.ops must be the first selection.\n;
redo;
  }
}
  }  

 Configure lists ops/core.ops as the first in the list of default ops
 files, but this doesn't match the regex. The patch below fixes this
 on Unix, but probably isn't portable to Win32; I imagine there's a
 better way to fix it.

 Simon

Index: config/inter/ops.pl
===
RCS file: /cvs/public/parrot/config/inter/ops.pl,v
retrieving revision 1.2
diff -u -r1.2 ops.pl
--- config/inter/ops.pl 23 Oct 2003 19:21:30 -  1.2
+++ config/inter/ops.pl 23 Oct 2003 22:19:39 -
@@ -34,7 +34,7 @@
 {
   $ops=prompt('Which opcode files would you like?', $ops);
   
-  if($ops !~ m{^\s*core\.ops}) {
+  if($ops !~ m{^ops/\s*core\.ops}) {
 print core.ops must be the first selection.\n;
 redo;
   }