April 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] [update 3.0] #30041

by Damien Cassou

On Tue, Apr 16, 2013 at 1:59 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > Opal is still not default compiler why not? Don't you think Opal will improve much faster if everyone uses it? -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

April 16, 2013

Re: [Pharo-project] [regression reporter]regression occurred

by Marcus Denker

On Apr 16, 2013, at 2:08 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > oops... those are a lot of regressions :) This should not happen: This means that somehow Opal is taken as the compiler. (The tests are not compatible between the two, we are going through them one by one, either porting or fixingâ¦ but it takes while). If they fail this mean that the wrong compiler is used when running the tests. > > On Apr 16, 2013, at 2:06 PM, no-reply(a)ci.inria.fr wrote: > >> https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/./label=li… >> >> 71 regressions found. >> CompilerTests.ClosureCompilerTest.testBlockDoitDecompilation >> CompilerTests.ClosureCompilerTest.testDecompiledDoitMethodTempNames >> CompilerTests.ClosureCompilerTest.testSourceRangeAccessForClosureBytecodeInjectInto >> CompilerTests.ClosureCompilerTest.testSourceRangeAccessForClosureLongFormBytecodeInjectInto >> CompilerTests.ClosureCompilerTest.testSourceRangeAccessForInjectInto >> CompilerTests.CompilerExceptionsTest.testAmbiguousSelector >> CompilerTests.CompilerExceptionsTest.testUndeclaredVariable >> CompilerTests.CompilerExceptionsTest.testUndefinedVariable >> CompilerTests.CompilerExceptionsTest.testUnknownSelector >> CompilerTests.CompilerExceptionsTest.testUnusedVariable >> CompilerTests.CompilerNotifyingTest.testATempShadowingAnotherTemp >> CompilerTests.CompilerNotifyingTest.testAlltogether >> CompilerTests.CompilerNotifyingTest.testAssignmentOfSelf >> CompilerTests.CompilerNotifyingTest.testCascadeInASuperSend >> CompilerTests.CompilerNotifyingTest.testDigitTooLargeForARadix >> CompilerTests.CompilerNotifyingTest.testEmptyCaseStatement >> CompilerTests.CompilerNotifyingTest.testExpectedExpressionInBraceArray >> CompilerTests.CompilerNotifyingTest.testExtraneousStatementAfterAReturnInABlock >> CompilerTests.CompilerNotifyingTest.testInvalidRadix >> CompilerTests.CompilerNotifyingTest.testLiteralCharacterMissing >> ... >> > >

April 16, 2013

[Pharo-project] [regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/./label=ma… 71 regressions found. CompilerTests.ClosureCompilerTest.testBlockDoitDecompilation CompilerTests.ClosureCompilerTest.testDecompiledDoitMethodTempNames CompilerTests.ClosureCompilerTest.testSourceRangeAccessForClosureBytecodeInjectInto CompilerTests.ClosureCompilerTest.testSourceRangeAccessForClosureLongFormBytecodeInjectInto CompilerTests.ClosureCompilerTest.testSourceRangeAccessForInjectInto CompilerTests.CompilerExceptionsTest.testAmbiguousSelector CompilerTests.CompilerExceptionsTest.testUndeclaredVariable CompilerTests.CompilerExceptionsTest.testUndefinedVariable CompilerTests.CompilerExceptionsTest.testUnknownSelector CompilerTests.CompilerExceptionsTest.testUnusedVariable CompilerTests.CompilerNotifyingTest.testATempShadowingAnotherTemp CompilerTests.CompilerNotifyingTest.testAlltogether CompilerTests.CompilerNotifyingTest.testAssignmentOfSelf CompilerTests.CompilerNotifyingTest.testCascadeInASuperSend CompilerTests.CompilerNotifyingTest.testDigitTooLargeForARadix CompilerTests.CompilerNotifyingTest.testEmptyCaseStatement CompilerTests.CompilerNotifyingTest.testExpectedExpressionInBraceArray CompilerTests.CompilerNotifyingTest.testExtraneousStatementAfterAReturnInABlock CompilerTests.CompilerNotifyingTest.testInvalidRadix CompilerTests.CompilerNotifyingTest.testLiteralCharacterMissing ...

April 16, 2013

[Pharo-project] [regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/./label=wi… 71 regressions found. CompilerTests.ClosureCompilerTest.testBlockDoitDecompilation CompilerTests.ClosureCompilerTest.testDecompiledDoitMethodTempNames CompilerTests.ClosureCompilerTest.testSourceRangeAccessForClosureBytecodeInjectInto CompilerTests.ClosureCompilerTest.testSourceRangeAccessForClosureLongFormBytecodeInjectInto CompilerTests.ClosureCompilerTest.testSourceRangeAccessForInjectInto CompilerTests.CompilerExceptionsTest.testAmbiguousSelector CompilerTests.CompilerExceptionsTest.testUndeclaredVariable CompilerTests.CompilerExceptionsTest.testUndefinedVariable CompilerTests.CompilerExceptionsTest.testUnknownSelector CompilerTests.CompilerExceptionsTest.testUnusedVariable CompilerTests.CompilerNotifyingTest.testATempShadowingAnotherTemp CompilerTests.CompilerNotifyingTest.testAlltogether CompilerTests.CompilerNotifyingTest.testAssignmentOfSelf CompilerTests.CompilerNotifyingTest.testCascadeInASuperSend CompilerTests.CompilerNotifyingTest.testDigitTooLargeForARadix CompilerTests.CompilerNotifyingTest.testEmptyCaseStatement CompilerTests.CompilerNotifyingTest.testExpectedExpressionInBraceArray CompilerTests.CompilerNotifyingTest.testExtraneousStatementAfterAReturnInABlock CompilerTests.CompilerNotifyingTest.testInvalidRadix CompilerTests.CompilerNotifyingTest.testLiteralCharacterMissing ...

April 16, 2013

Re: [Pharo-project] [regression reporter]regression occurred

by Esteban Lorenzano

oops... those are a lot of regressions :) On Apr 16, 2013, at 2:06 PM, no-reply(a)ci.inria.fr wrote: > https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/./label=li… > > 71 regressions found. > CompilerTests.ClosureCompilerTest.testBlockDoitDecompilation > CompilerTests.ClosureCompilerTest.testDecompiledDoitMethodTempNames > CompilerTests.ClosureCompilerTest.testSourceRangeAccessForClosureBytecodeInjectInto > CompilerTests.ClosureCompilerTest.testSourceRangeAccessForClosureLongFormBytecodeInjectInto > CompilerTests.ClosureCompilerTest.testSourceRangeAccessForInjectInto > CompilerTests.CompilerExceptionsTest.testAmbiguousSelector > CompilerTests.CompilerExceptionsTest.testUndeclaredVariable > CompilerTests.CompilerExceptionsTest.testUndefinedVariable > CompilerTests.CompilerExceptionsTest.testUnknownSelector > CompilerTests.CompilerExceptionsTest.testUnusedVariable > CompilerTests.CompilerNotifyingTest.testATempShadowingAnotherTemp > CompilerTests.CompilerNotifyingTest.testAlltogether > CompilerTests.CompilerNotifyingTest.testAssignmentOfSelf > CompilerTests.CompilerNotifyingTest.testCascadeInASuperSend > CompilerTests.CompilerNotifyingTest.testDigitTooLargeForARadix > CompilerTests.CompilerNotifyingTest.testEmptyCaseStatement > CompilerTests.CompilerNotifyingTest.testExpectedExpressionInBraceArray > CompilerTests.CompilerNotifyingTest.testExtraneousStatementAfterAReturnInABlock > CompilerTests.CompilerNotifyingTest.testInvalidRadix > CompilerTests.CompilerNotifyingTest.testLiteralCharacterMissing > ... >

April 16, 2013

[Pharo-project] [regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/./label=li… 71 regressions found. CompilerTests.ClosureCompilerTest.testBlockDoitDecompilation CompilerTests.ClosureCompilerTest.testDecompiledDoitMethodTempNames CompilerTests.ClosureCompilerTest.testSourceRangeAccessForClosureBytecodeInjectInto CompilerTests.ClosureCompilerTest.testSourceRangeAccessForClosureLongFormBytecodeInjectInto CompilerTests.ClosureCompilerTest.testSourceRangeAccessForInjectInto CompilerTests.CompilerExceptionsTest.testAmbiguousSelector CompilerTests.CompilerExceptionsTest.testUndeclaredVariable CompilerTests.CompilerExceptionsTest.testUndefinedVariable CompilerTests.CompilerExceptionsTest.testUnknownSelector CompilerTests.CompilerExceptionsTest.testUnusedVariable CompilerTests.CompilerNotifyingTest.testATempShadowingAnotherTemp CompilerTests.CompilerNotifyingTest.testAlltogether CompilerTests.CompilerNotifyingTest.testAssignmentOfSelf CompilerTests.CompilerNotifyingTest.testCascadeInASuperSend CompilerTests.CompilerNotifyingTest.testDigitTooLargeForARadix CompilerTests.CompilerNotifyingTest.testEmptyCaseStatement CompilerTests.CompilerNotifyingTest.testExpectedExpressionInBraceArray CompilerTests.CompilerNotifyingTest.testExtraneousStatementAfterAReturnInABlock CompilerTests.CompilerNotifyingTest.testInvalidRadix CompilerTests.CompilerNotifyingTest.testLiteralCharacterMissing ...

April 16, 2013

Re: [Pharo-project] Understanding Athens

by Pavel Krivanek

On Tue, Apr 16, 2013 at 1:23 PM, kilon <thekilon(a)yahoo.co.uk> wrote: > Doru , I am using Pharo 2.0 from the main website , also it does not matter > because cairo libraries are looked outside the pharo folder. > > If you open system browser and go to the CairoLibraryLoader>>getLibraryPath > (class side) you will see it tries to find cairo libs in > '/usr/lib/libcairo.so' . On the other hand there are cairo libs included > for > the windows version inside the pharo folder. Its kinda wierd that they are > not included for macos and linux. > > Pavel , you mid sharing how you installed 32 bit cairo, because I googled > it > and I could not find anything on the subject. Thanks. > for Fedora it is: $ yum install cairo.i686 PharoVM itself needs several i686 libraries, this loads next about 30 of them. I had to change the library path in CairoLibraryLoader class>>#getLibraryPath to /usr/lib/libcairo.so.2 > Oh and if anyone can answer my stackoverflow questions i will be more than > grateful. I am prepared to contribute to > Athens as much as I can and even port mophic to it BUT i need first to > understrand what is going on. I have read > Cairo documentation and now all i need is to decypher athens so be prepared > for a bombarment of questions. > > > > -- > View this message in context: > http://forum.world.st/Understanding-Athens-tp4681820p4681847.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > >

April 16, 2013

[Pharo-project] [update 3.0] #30041

by Esteban Lorenzano

30041 ----- 10028 Integrate Opal https://pharo.fogbugz.com/f/cases/10028 WARNING: ======== 1) Opal is still not default compiler, it is there to allow us to improve it and put it on shape 2) Please, help on it by providing bug reports, etc. :)

April 16, 2013

Re: [Pharo-project] Understanding Athens

by Norbert Hartl

If you go for ppa you have two options. Compile everything when building the package or just packaging binaries. So have to set either Build-Depends: libcairo2-dev or/and Depends: libcairo2 in the debian/control file. The architecture you build your stuff for is i386. With the modern multi-arch support you can install e.g. a i386 version in an amd64 environment. Much better than to force a 64bit shell for a 32bit executable. Norbert Am 16.04.2013 um 13:40 schrieb Igor Stasenko <siguctua(a)gmail.com>: > P.S. i also asked Damien to look for the ways how we can tell system > that installation depends on cairo-32 bit package (for ppa distro). > > On 16 April 2013 13:35, Igor Stasenko <siguctua(a)gmail.com> wrote: >> On 16 April 2013 13:23, kilon <thekilon(a)yahoo.co.uk> wrote: >>> Doru , I am using Pharo 2.0 from the main website , also it does not matter >>> because cairo libraries are looked outside the pharo folder. >>> >>> If you open system browser and go to the CairoLibraryLoader>>getLibraryPath >>> (class side) you will see it tries to find cairo libs in >>> '/usr/lib/libcairo.so' . On the other hand there are cairo libs included for >>> the windows version inside the pharo folder. Its kinda wierd that they are >>> not included for macos and linux. >>> >> For mac and windows we bundle VM together with cairo library. >> For linux, since they have a standardized way of installing third-party libs, >> you're on your own. >> >> Yes, it would be nice if we can get a precise instructions how to >> install 32-bit libs >> so other people can use them. >> >>> Pavel , you mid sharing how you installed 32 bit cairo, because I googled it >>> and I could not find anything on the subject. Thanks. >>> >>> Oh and if anyone can answer my stackoverflow questions i will be more than >>> grateful. I am prepared to contribute to >>> Athens as much as I can and even port mophic to it BUT i need first to >>> understrand what is going on. >> >> Sure, I will check and try to answer them. >> >>> I have read >>> Cairo documentation and now all i need is to decypher athens so be prepared >>> for a bombarment of questions. >>> >> You're welcome. >> >>> >>> >>> -- >>> View this message in context: http://forum.world.st/Understanding-Athens-tp4681820p4681847.html >>> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >>> >> >> >> >> -- >> Best regards, >> Igor Stasenko. > > > > -- > Best regards, > Igor Stasenko. >

April 16, 2013

Re: [Pharo-project] Understanding Athens

by Igor Stasenko

P.S. i also asked Damien to look for the ways how we can tell system that installation depends on cairo-32 bit package (for ppa distro). On 16 April 2013 13:35, Igor Stasenko <siguctua(a)gmail.com> wrote: > On 16 April 2013 13:23, kilon <thekilon(a)yahoo.co.uk> wrote: >> Doru , I am using Pharo 2.0 from the main website , also it does not matter >> because cairo libraries are looked outside the pharo folder. >> >> If you open system browser and go to the CairoLibraryLoader>>getLibraryPath >> (class side) you will see it tries to find cairo libs in >> '/usr/lib/libcairo.so' . On the other hand there are cairo libs included for >> the windows version inside the pharo folder. Its kinda wierd that they are >> not included for macos and linux. >> > For mac and windows we bundle VM together with cairo library. > For linux, since they have a standardized way of installing third-party libs, > you're on your own. > > Yes, it would be nice if we can get a precise instructions how to > install 32-bit libs > so other people can use them. > >> Pavel , you mid sharing how you installed 32 bit cairo, because I googled it >> and I could not find anything on the subject. Thanks. >> >> Oh and if anyone can answer my stackoverflow questions i will be more than >> grateful. I am prepared to contribute to >> Athens as much as I can and even port mophic to it BUT i need first to >> understrand what is going on. > > Sure, I will check and try to answer them. > >> I have read >> Cairo documentation and now all i need is to decypher athens so be prepared >> for a bombarment of questions. >> > You're welcome. > >> >> >> -- >> View this message in context: http://forum.world.st/Understanding-Athens-tp4681820p4681847.html >> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >> > > > > -- > Best regards, > Igor Stasenko. -- Best regards, Igor Stasenko.

April 16, 2013