[Pharo-dev] SystemVersion>>highestUpdate causes FFISharedPool class>>initialize to fail
guillermopolito at gmail.com
Tue Aug 22 11:55:22 EDT 2017
I don't think so... Build number only works from the CI. This means
that if you build your image in your machine you'll have no build
number and then this piece of code will not work neither. Thus maybe
we need to find a separate solution for it?
On 8/22/17, Alistair Grant <akgrant0710 at gmail.com> wrote:
> Hi Everyone,
> I'm attempting to update to the latest Pharo7 image (918efe2, 32 bit),
> but am getting an error while loading OSsubprocess.
> The error occurs in FFISharedPool class>>initialize:
> self flag: #removeIt.
> "This IF will be eliminated soon...only here temporary"
> (SystemVersion current highestUpdate >= 50558)
> ifTrue: [
> SessionManager default registerToolClassNamed: self name
> ifFalse: [
> Smalltalk addToStartUpList: self.
> because #highestUpdate is nil.
> The top of the stack is:
> UndefinedObject(Object)>>doesNotUnderstand: #'>='
> FFISharedPool class>>initialize
> [ :each | each postloadOver: (self obsoletionFor: each) ] in
> MCPackageLoader>>basicLoadDefinitions in Block: [ :each | each postloadOver:
> (self obsoletionFor: ...etc...
> Based on the method above, it looks like highestUpdate used to be set
> based on the image number, and has presumably broken during the move to
> Pharo 7 and git.
> Earlier Pharo 7 images had it set to 0, which doesn't sound right.
> Since a build number was recently introduced (fogbugz 20321), should the
> highestUpdate be set to 70000+buildNumber?
> E.g. this image has an identifier of:
> Pharo 7.0
> Build information:
> So highestUpdate would be 70056.
French National Center for Scientific Research - *http://www.cnrs.fr*
*Web:* *http://guillep.github.io* <http://guillep.github.io>
*Phone: *+33 06 52 70 66 13
More information about the Pharo-dev