Hi Dave, OSProcess accessor osppModuleVersionString ==> '4.0.1'
I get the same result with the Mac 4.2.2beta1U VM. Adrian On Nov 18, 2009, at 14:33 , David T. Lewis wrote: > On Wed, Nov 18, 2009 at 09:51:24AM +0100, Adrian Lienhard wrote: >> Hi Dave, >> >> Just to make sure I'm looking at the right code: The latest version >> (for Pharo) are in the projects OSProcess and CommandShell on >> SqueakSource.com? > > Yes, these are the correct versions to use. > >> MC complains about missing classes when loading; I >> just ignored them (probably they are not relevant as they seem >> related >> to the GUI). > > These are the MVC user interface classes for CommandShell, and it is > safe to ignore them. The tests do not required these classes. > >> >> Running all tests crashes the Mac VM. > > I have seen crashes on my Linux VM also (testing with an earlier Pharo > image), although it was not happening yesterday when I was testing. > Presumably there is inadequate parameter checking in one or more of > the OSPP primitives, and whatever is going wrong in the tests has > exposed this. > >> >> But even the simple test of chdir fails: >> >> (UnixProcessAccessorTestCase selector: #testChDir) debug >> >> It does not seem to invoke any Pharo-specific code. So I wonder if I >> miss something trivial. UnixOSProcessPlugin.bundle exists in my VM's >> Contents/Resources/ directory. > > I do not have a Mac to test with. I would think that the fact that you > have gotten the VM to crash is an indication that you have located the > plugin bundle though ;) Just to double check, try doing this in a > workspace: > > OSProcess accessor osppModuleVersionString ==> '4.3.3' > > The #osppModuleVersionString method will make a call to the plugin > without doing much else, so that is a way to verify that you have > loaded the bundle. Also, if the version is not fairly close to the > latest (4.3.3) it might be an issue. > > On OS X, I don't think that you have the AioPlugin or > XDisplayControlPlugin > available, so some of the tests will fail as a result of this. I > don't have time right now, but I'll try removing these plugins from > my system and see what happens. But it should be a few simple test > failures, not the kind of problem you are seeing. > > (As a side note, I use a Linux PC, and John and I originally got > OSProcess working on Mac entirely through email with a bit of > help from a couple other Mac users. Talk about a lengthy > edit-compile-test-debug development cycle! But it was a good > challenge and quite gratifying when we got it all working.). > > Thanks, > Dave > > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
