[Pharo-project] Posible bug
Hi All! Im trying to get Cog interpreter using ConfigurationOfCog Gofer it squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfCog'; load. ((Smalltalk at: #ConfigurationOfCog) project version: '1.5') load. SystemVersion current version 'Pharo2.0a' Smalltalk vm version ( 'CoInterpreter VMMaker-oscog-EstebanLorenzano.158 uuid: 82eded98-68af-4c80-a472-4f6de293adcf May 1 2012, StackToRegisterMappingCogit VMMaker-oscog-EstebanLorenzano.158 uuid: 82eded98-68af-4c80-a472-4f6de293adcf May 1 2012, https://git.gitorious.org/cogvm/blessed.git Commit: 6aa3fd0f1188078d3167dec1a53031a61b97b688 Date: Tue May 1 20:28:14 2012 +0200 By: Esteban Lorenzano <estebanlm@gmail.com>' ) when is compiling (ok, at pharo 1.4 too.. maybe is the vm) methods and loading VMMaker it spawn a 'warning' window and image get freezed. Is a bug? a mistake?
Is working @ pharo 1.4. Just needed 2' more :P 2012/5/22 Santiago Bragagnolo <santiagobragagnolo@gmail.com>
Hi All!
Im trying to get Cog interpreter using ConfigurationOfCog
Gofer it squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfCog'; load.
((Smalltalk at: #ConfigurationOfCog) project version: '1.5') load.
SystemVersion current version 'Pharo2.0a'
Smalltalk vm version ( 'CoInterpreter VMMaker-oscog-EstebanLorenzano.158 uuid: 82eded98-68af-4c80-a472-4f6de293adcf May 1 2012, StackToRegisterMappingCogit VMMaker-oscog-EstebanLorenzano.158 uuid: 82eded98-68af-4c80-a472-4f6de293adcf May 1 2012, https://git.gitorious.org/cogvm/blessed.git Commit: 6aa3fd0f1188078d3167dec1a53031a61b97b688 Date: Tue May 1 20:28:14 2012 +0200 By: Esteban Lorenzano <estebanlm@gmail.com>' )
when is compiling (ok, at pharo 1.4 too.. maybe is the vm) methods and loading VMMaker it spawn a 'warning' window and image get freezed. Is a bug? a mistake?
On 23 May 2012 02:33, Santiago Bragagnolo <santiagobragagnolo@gmail.com> wrote:
Is working @ pharo 1.4. Just needed 2' more :P
2012/5/22 Santiago Bragagnolo <santiagobragagnolo@gmail.com>
Hi All!
 Im trying to get Cog interpreter using ConfigurationOfCog
Gofer it squeaksource: 'MetacelloRepository'; Â Â Â package: 'ConfigurationOfCog'; Â Â Â load.
((Smalltalk at: #ConfigurationOfCog) project version: '1.5') load.
this version is pretty old. Please use more recent versions (in my image it is 4.7).. of course if you use most recent vm platform sources. you can also check the codegen-scripts/LoadVMMaker.st script file which contains a version of VMMaker suitable for building with platform source code you using.
SystemVersion current version 'Pharo2.0a'
Smalltalk vm version (  'CoInterpreter VMMaker-oscog-EstebanLorenzano.158 uuid: 82eded98-68af-4c80-a472-4f6de293adcf May 1 2012, StackToRegisterMappingCogit VMMaker-oscog-EstebanLorenzano.158 uuid: 82eded98-68af-4c80-a472-4f6de293adcf May 1 2012, https://git.gitorious.org/cogvm/blessed.git Commit: 6aa3fd0f1188078d3167dec1a53031a61b97b688 Date: Tue May 1 20:28:14 2012 +0200 By: Esteban Lorenzano <estebanlm@gmail.com>' )
when is compiling (ok, at pharo 1.4 too.. maybe is the vm) methods and loading VMMaker it spawn a 'warning' window and image get freezed. Is a bug? a mistake?
-- Best regards, Igor Stasenko.
Mariano, can you please change your blog and replace '1.5' with 'how the hell i know' (big bold red letters) because it is dozen time, when people blindly copy pasting the code, and it of course doesn't works :) -- Best regards, Igor Stasenko.
:$ clearly 'blindly'. very thanks. 2012/5/22 Igor Stasenko <siguctua@gmail.com>
Mariano, can you please change your blog and replace '1.5' with 'how the hell i know' (big bold red letters)
because it is dozen time, when people blindly copy pasting the code, and it of course doesn't works :)
-- Best regards, Igor Stasenko.
Igor Stasenko wrote
Mariano, can you please change your blog and replace '1.5' with 'how the hell i know' (big bold red letters)
Why not just instruct them to download the sources & vmmaker image from Jenkins blessed? Then they will always be compatible and only susceptible to changes in the vmmaker api... -- View this message in context: http://forum.world.st/Posible-bug-tp4631484p4631500.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
On 23 May 2012 06:51, Sean P. DeNigris <sean@clipperadams.com> wrote:
Igor Stasenko wrote
Mariano, can you please change your blog and replace '1.5' with 'how the hell i know' (big bold red letters)
Why not just instruct them to download the sources & vmmaker image from Jenkins blessed? Then they will always be compatible and only susceptible to changes in the vmmaker api...
because then it will be not from scratch. of course i using image(s) vmmaker built by jenkins, where all stuff already preloaded. but it important bit of knowledge, which people should know how things rolling.
-- View this message in context: http://forum.world.st/Posible-bug-tp4631484p4631500.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
-- Best regards, Igor Stasenko.
yeah... problem is that way they are just "compile monkeys", repeating the work jenkins already do. I'd want people to be able to learn and contribute... best, Esteban On May 23, 2012, at 9:05 AM, Igor Stasenko wrote:
On 23 May 2012 06:51, Sean P. DeNigris <sean@clipperadams.com> wrote:
Igor Stasenko wrote
Mariano, can you please change your blog and replace '1.5' with 'how the hell i know' (big bold red letters)
Why not just instruct them to download the sources & vmmaker image from Jenkins blessed? Then they will always be compatible and only susceptible to changes in the vmmaker api...
because then it will be not from scratch. of course i using image(s) vmmaker built by jenkins, where all stuff already preloaded. but it important bit of knowledge, which people should know how things rolling.
-- View this message in context: http://forum.world.st/Posible-bug-tp4631484p4631500.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
-- Best regards, Igor Stasenko.
On Wed, May 23, 2012 at 9:32 AM, Esteban Lorenzano <estebanlm@gmail.com>wrote:
yeah... problem is that way they are just "compile monkeys", repeating the work jenkins already do. I'd want people to be able to learn and contribute...
+99999
best, Esteban
On May 23, 2012, at 9:05 AM, Igor Stasenko wrote:
On 23 May 2012 06:51, Sean P. DeNigris <sean@clipperadams.com> wrote:
Igor Stasenko wrote
Mariano, can you please change your blog and replace '1.5' with 'how the hell i know' (big bold red letters)
Why not just instruct them to download the sources & vmmaker image from Jenkins blessed? Then they will always be compatible and only
susceptible to
changes in the vmmaker api...
because then it will be not from scratch. of course i using image(s) vmmaker built by jenkins, where all stuff already preloaded. but it important bit of knowledge, which people should know how things rolling.
-- View this message in context: http://forum.world.st/Posible-bug-tp4631484p4631500.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
-- Best regards, Igor Stasenko.
-- Mariano http://marianopeck.wordpress.com
Igor Stasenko wrote
because then it will be not from scratch. of course i using image(s) vmmaker built by jenkins, where all stuff already preloaded. but it important bit of knowledge, which people should know how things rolling.
Okay, I got it. Would it be a good compromise to point them to the Jenkins script that syncs the config with the current image? Is it LoadVMMaker.st? Maybe this (or whatever information you would need to compile from scratch that changes over time) could be added as an artifact to the Cog-VM on Jenkins (or as another job, like "Build VM from Scratch"). This way, anyone could go to the last successful build and see which versions of Pharo, ConfigurationOfXxx, git, etc. were used and get the same result. -- View this message in context: http://forum.world.st/Posible-bug-tp4631484p4631601.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
check the HOWTOBUILD file in the git repository + there is an image.sh script in the /image folder of the git repo I think the git repo should be the place to keep track of such documentation! On 2012-05-23, at 18:29, Sean P. DeNigris wrote:
Igor Stasenko wrote
because then it will be not from scratch. of course i using image(s) vmmaker built by jenkins, where all stuff already preloaded. but it important bit of knowledge, which people should know how things rolling.
Okay, I got it. Would it be a good compromise to point them to the Jenkins script that syncs the config with the current image? Is it LoadVMMaker.st? Maybe this (or whatever information you would need to compile from scratch that changes over time) could be added as an artifact to the Cog-VM on Jenkins (or as another job, like "Build VM from Scratch"). This way, anyone could go to the last successful build and see which versions of Pharo, ConfigurationOfXxx, git, etc. were used and get the same result.
-- View this message in context: http://forum.world.st/Posible-bug-tp4631484p4631601.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
Camillo Bruni-3 wrote
check the HOWTOBUILD file in the git repository + there is an image.sh script in the /image folder of the git repo
I think the git repo should be the place to keep track of such documentation!
I don't know enough about the process - will that guarantee a working build? Right now, Jenkins "Cog Git Tracker" is failing (not because of the sources this time). If there was something broken, using the versions of image/ConfigurationOfXxx, sources, etc. from Jenkins' last successful build would guarantee success anyway. Sean -- View this message in context: http://forum.world.st/Posible-bug-tp4631484p4631744.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
On Wed, May 23, 2012 at 4:33 AM, Igor Stasenko <siguctua@gmail.com> wrote:
Mariano, can you please change your blog and replace '1.5' with 'how the hell i know' (big bold red letters)
Actualy, that post is a receipie that you have to follow step by step EXACTLY what I do. That way you are 99% probably you will be able to build the VM. If Santiago followed my blog, he did it wrong, but I didn't use Pharo 1.4. Anyway, what you say is explained in the second part: http://marianopeck.wordpress.com/2011/04/16/building-the-vm-second-part/ BTW, I just added a link to that from the first part.
because it is dozen time, when people blindly copy pasting the code, and it of course doesn't works :)
Yes it does. Perfectly. But you have to follow all the instructions. The only way to have a reproducible build is to have explicit versions of everything. And that's what I did and that's why people can build a VM even 1 year later. All you need to do is to follow the steps. Once you are a VM hacker then you can experiment with the bleedingEdge.
-- Best regards, Igor Stasenko.
-- Mariano http://marianopeck.wordpress.com
On 23 May 2012 10:10, Mariano Martinez Peck <marianopeck@gmail.com> wrote:
On Wed, May 23, 2012 at 4:33 AM, Igor Stasenko <siguctua@gmail.com> wrote:
Mariano, can you please change your blog and replace '1.5' with 'how the hell i know' (big bold red letters)
Actualy, that post is a receipie that you have to follow step by step EXACTLY what I do. That way you are 99% probably you will be able to build the VM. If Santiago followed my blog, he did it wrong, but I didn't use Pharo 1.4. Anyway, what you say is explained in the second part: http://marianopeck.wordpress.com/2011/04/16/building-the-vm-second-part/
BTW, I just added a link to that from the first part.
because it is dozen time, when people blindly copy pasting the code, and it of course doesn't works :)
Yes it does. Perfectly. But you have to follow all the instructions. The only way to have a reproducible build is to have explicit versions of everything. And that's what I did and that's why people can build a VM even 1 year later. All you need to do is to follow the steps. Once you are a VM hacker then you can experiment with the bleedingEdge.
I agree with all you say. And this was our goal - be able to reproduce built. But do you think everyone here is so patient to do all steps and don't try to outsmart boring doc and jump over stages? :) At least , leave the message somewhere .. bold and red "Notice for impatient: DO NOT copy-paste this code snippet, if you want to build most recent VM, this code is NOT for it" -- Best regards, Igor Stasenko.
participants (6)
-
Camillo Bruni -
Esteban Lorenzano -
Igor Stasenko -
Mariano Martinez Peck -
Santiago Bragagnolo -
Sean P. DeNigris