On Sun, Mar 01, 2009 at 03:32:46PM -0600, Chris Dolan wrote:
On Feb 26, 2009, at 3:06 PM, Moritz Lenz wrote:
But after that please do a 'make clean; perl Configure.pl' to make
sure
that the fallout of the previous build don't affect the new one.
Time to update tools/rebase-rakudo.pl!
Not
On Feb 26, 2009, at 3:06 PM, Moritz Lenz wrote:
But after that please do a 'make clean; perl Configure.pl' to make
sure
that the fallout of the previous build don't affect the new one.
Time to update tools/rebase-rakudo.pl!
Chris
I have rakudo built under my parrot directory. I updated and rebuilt
parrot, then updated and rebuilt rakudo, but rakudo won
~/parrot $ svn up
(lots of files update)
~/parrot $ gmake
(parrot re-builds OK)
~/parrot $ cd languages/rakudo/
~/parrot/languages/rakudo $ git pull
(files update)
On Thu, Feb 26, 2009 at 11:53:21AM -0800, yary wrote:
I have rakudo built under my parrot directory. I updated and rebuilt
parrot, then updated and rebuilt rakudo, but rakudo won
A longer announcement should be hitting the list later today,
but for now the recommended build sequence for rakudo
OK, I'll try some/all of the suggestions. I have a few comments-
On Thu, Feb 26, 2009 at 12:06 PM, Patrick R. Michaud pmich...@pobox.com wrote:
...
A longer announcement should be hitting the list later today,
but for now the recommended build sequence for rakudo is:
$ git clone
On Thu, Feb 26, 2009 at 10:06:53PM +0100, Moritz Lenz wrote:
But after that please do a 'make clean; perl Configure.pl' to make sure
that the fallout of the previous build don't affect the new one.
I've been thinking that Configure.pl should force a 'make clean'
to avoid the problem altogether.
