HI Fernando, It was a bug fix. And we hadn't at that time access to the Alien repo for saving it. Currently, we have a metacello config and it refers the alien repo.
Noury On 29 sept. 2010, at 15:20, Fernando olivero wrote: > A question to the Ocean developers, why do have a particular Alien-Core > package in the ocean repo? ( Alien-Core-LucFabresse.64.mcz ) > > Are there some fixes that could be included in the official package? Please > let me know so i can integrate them. > > I'm asking because i'm cleaning a bit the Alien mess, ( see previous mail) , > and would like to have a single working official Alien. > > Thanks, > Fernando > > On Sep 29, 2010, at 12:56 PM, Fernando olivero wrote: > >> This Error prevents from using Alien in the lastest Pharo image. >> >> I will try to fix this today. >> >> Also i will remove the ConfigurationOfAlien from the Alien repository, >> because the version in MetacelloRepository should be used instead. >> So there are no future misunderstandings >> >> >> Thanks to Eliot, and using his precompiled Vms for all platforms Alien >> would be available now! >> (if the mentioned bug were fixed). >> >> >> Fernando >> >> >> On Sep 28, 2010, at 12:05 PM, Igor Stasenko wrote: >> >>> On 28 September 2010 11:51, Henrik Johansen >>> <[email protected]> wrote: >>>> On Sep 28, 2010, at 10:34 16AM, Alberto Bacchelli wrote: >>>> >>>>> On 9/27/10 8:13 PM, Eliot Miranda wrote: >>>>>> >>>>>> >>>>>> 2010/9/27 Fernando >>>>>> olivero<[email protected]<mailto:[email protected]>> >>>>>> Does the prebuilt CogVM for linux include Alien support? >>>>>> http://www.mirandabanda.org/files/Cog/VM/VM.r2313/ >>>>>> >>>>>> Only of the data manipulation and callout parts, not the callback parts. >>>>>> I'm trying to find time to work on integrating the Alien callback >>>>>> machinery with the FFI. >>>>>> >>>>>> best >>>>>> Eliot >>>>> >>>>> We had a problem after installing Alien, >>>>> when running the tests. >>>>> >>>>> The following does not understand >>>>> >>>>> MessageNotUnderstood: Array>>createMethod:header:methodClass: >>>>> >>>>> sent by >>>>> CompileMethod >>>>> class>>newBytes:trailerBytes:nArgs:nTemps:nStack:nLits:primitive: >>>>> >>>>> It appears to be cog related, is it? >>>>> >>>>> Thank you, >>>>> Alberto >>>> >>>> No, it's Method-trailer related. >>>> >>>> IIRC, the convention used to be to pass the empty trailer bytes #(0 0 0 >>>> 0), find the offending sender and change it to pass CompiledMethodTrailer >>>> empty instead. >>>> >>> >>> Right. A more compatible way is to use SomeClass defaultMethodTrailer >>> Where SomeClass should be a class, where you installing this method. >>> >>> >>>> Cheers, >>>> Henry >>>> >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> [email protected] >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>> >>> >>> >>> >>> -- >>> Best regards, >>> Igor Stasenko AKA sig. >>> >>> _______________________________________________ >>> 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 > > > _______________________________________________ > 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
