Hi Ian!
(moved to vm-dev)
Ian Piumarta ian.piumarta@hp.com wrote:
On Mar 15, 2005, at 13:23, goran.krampe@bluefish.se wrote:
And it is a bit frustrating, AFAIK it still isn't in there (getImageName). So the unix HEAD isn't compiling with the current VMMaker
It's compiling fine with the VMMaker shipped with 3.7-5898-full.
Ehum, cough. Ok, now the fog clears. :) I didn't notice VMMaker is already included in 3.7, so I opened up SMLoader in a 5989-full, selected VMMaker and installed it. Oops, bad move.
That will install the latest, which evidently is a beta for 3.8, but in this case unfortunately marked as being for 3.7 (so SM will not complain), though even if it tripped me up, that may be considered fine - since it does after all *work* in 3.7.
I apologize for my utter VM-n00b-stupidity and still humbly conclude that a little page somewhere explaining how to do this properly would at least have helped me - and obviously all the other people stumbling on this getImageName stuff - evidently they must all have been falling in the same trap. :)
I know Ian has pretty detailed and good descriptions, but I think what is lacking here is a more condensed howto that indeed includes this stuff about VMMaker (haven't tested this, but I guess you see what I mean):
- Get the full image for the official *current release*. - Use the VMMaker installed in that image, or install the latest version *for that release* (not newer). The trunk of the support code is meant to build with the *released* VMMaker, not with the latest available. - Check out trunk like this: yaddayadda - Create configure script by doing: cd <somewhere>/squeak/platforms/unix/config ./configure && make - Start VMMaker and set platforms path to "<somewhere>/squeak/trunk/platforms" and src path to "<somewhere>/squeak/trunk/src" (which you need to create) - Then create directory <somewhere>/squeak/trunk/build
After that this should repeatedly build you a VM: - Use VMMaker: Clean out source (the button) Make all plugins internal (or start with none) Generate all - cd to <somewhere>/squeak/trunk/build and build it: rm -rf * && ../platforms/unix/config/configure && make
And to install, you can do make install etc. See Makefile for other targets like for example only compiling plugins etc.
regards, Göran
PS. Ian, did you try with automake 1.8 or 1.9?
PSS. Still think a little page explaining the most important details about the VM work process would be helpful. I don't think many people are aware that Ian wants patches in the form of full files sent by email for example.
I apologize for my utter VM-n00b-stupidity and still humbly conclude that a little page somewhere explaining how to do this properly would at least have helped me - and obviously all the other people stumbling on this getImageName stuff - evidently they must all have been falling in the same trap. :)
More likely, they have been using a basic image (3.7 or 3.8). Which reminds me: With the current SM, is there actually a way of marking releases in a way that users will automatically get "their" version?
I know Ian has pretty detailed and good descriptions, but I think what is lacking here is a more condensed howto that indeed includes this stuff about VMMaker (haven't tested this, but I guess you see what I mean):
http://squeak.hpl.hp.com/unix/devel.html http://squeak.hpl.hp.com/unix/platforms/unix/doc/HowToBuildFromSource.html/i...
Both seem quite applicable in this regard.
PSS. Still think a little page explaining the most important details about the VM work process would be helpful. I don't think many people are aware that Ian wants patches in the form of full files sent by email for example.
Well, if they care to read they might now ;-)
Cheers, - Andreas
Hi!
Andreas Raab andreas.raab@gmx.de wrote:
I apologize for my utter VM-n00b-stupidity and still humbly conclude that a little page somewhere explaining how to do this properly would at least have helped me - and obviously all the other people stumbling on this getImageName stuff - evidently they must all have been falling in the same trap. :)
More likely, they have been using a basic image (3.7 or 3.8). Which
Yeah, I did that too at first. ;)
reminds me: With the current SM, is there actually a way of marking releases in a way that users will automatically get "their" version?
Yes, I assume you mean "their" as in "for their Squeak version". When you do "install" on a package (not a specific release) it will try to find the latest published release for your Squeak version (looking at the categories).
And it will typically ask a bunch of questions if there are no published ones, or if there is no version for your Squeak version etc, etc. So no, not as good as full dependencies - but it helps.
I know Ian has pretty detailed and good descriptions, but I think what is lacking here is a more condensed howto that indeed includes this stuff about VMMaker (haven't tested this, but I guess you see what I mean):
http://squeak.hpl.hp.com/unix/devel.html http://squeak.hpl.hp.com/unix/platforms/unix/doc/HowToBuildFromSource.html/i...
Both seem quite applicable in this regard.
These were the docs I was indeed referring to. But when I looked at them I didn't find much info about VMMaker. And yes, I did try the preloaded VMMaker image, but that is a 3.6 image, so that isn't really the "HEAD" of VM development. And also it failed with:
vm/vm.a(sqVirtualMachine.o)(.text+0x483): In function `sqGetInterpreterProxy': /home/gokr/svn/squeak/trunk/platforms/Cross/vm/sqVirtualMachine.c:315: undefined reference to `isArray' vm/vm.a(sqVirtualMachine.o)(.text+0x48e):/home/gokr/svn/squeak/trunk/pla tforms/Cross/vm/sqVirtualMachine.c:316: undefined reference to `forceInterruptCheck' collect2: ld returned 1 exit status make: *** [squeak] Error 1
...but I guess it would work if I checked out 3.6 from Svn using some tag or so.
PSS. Still think a little page explaining the most important details about the VM work process would be helpful. I don't think many people are aware that Ian wants patches in the form of full files sent by email for example.
Well, if they care to read they might now ;-)
Cheers,
- Andreas
cheers, Göran
PS. Also note that the current trunk for unix is based on a 3.7-beta image (5868), which can be seen flashing by during the configure phase. Ian and I discovered this a day or two ago and Ian used language "not appropriate" for this forum :) :), it is a mistake, but I am not sure if it has any known bad consequences.
vm-dev@lists.squeakfoundation.org
-
Andreas Raab -
goran.krampe＠bluefish.se