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

Re: [Pharo-project] Osmocom Smalltalk packages available/ (mobile) communication packages for Pharo

by stephane ducasse

thanks norbert. I contacted him. Stef On Feb 25, 2013, at 10:47 AM, Norbert Hartl <norbert(a)hartl.name> wrote: > It is > > holger(a)freyther.de > > Norbert > > Am 24.02.2013 um 11:47 schrieb stephane ducasse <stephane.ducasse(a)free.fr>: > >> I would be nice to know if they can propose a dual licensing GPL / MIT. >> But I could not find a way to contact the author. >> >> Sef >> >>> Found this on the web: >>> >>> http://smalltalk.gnu.org/blog/zecke/making-my-osmocom-smalltalk-packages-av… >>> >> >> > >

Feb. 25, 2013

Re: [Pharo-project] Osmocom Smalltalk packages available/ (mobile) communication packages for Pharo

by Norbert Hartl

It is holger(a)freyther.de Norbert Am 24.02.2013 um 11:47 schrieb stephane ducasse <stephane.ducasse(a)free.fr>: > I would be nice to know if they can propose a dual licensing GPL / MIT. > But I could not find a way to contact the author. > > Sef > >> Found this on the web: >> >> http://smalltalk.gnu.org/blog/zecke/making-my-osmocom-smalltalk-packages-av… >> > >

Feb. 25, 2013

[Pharo-project] [JOB][Research] 16 month Postdoc "Architectural Design Exploration"

by Marcus Denker

Architectural Design Exploration ================================ About Inria and the job ----------------------- Inria, with its academic, institutional and industrial partners, is commited to major research and innovation projects in the field of computational sciences. The institute disseminates across France thanks to its eight research centres. The Inria Lille - Nord Europe research centre, inaugurated in 2008, employs 357 people, including 250 scientists, in its seventeen research teams. Recognised for its significant contribution to the social and economic development of the Nord - Pas-de-Calais region, the Inria Lille - Nord Europe research centre promotes a policy of close cooperation with major businesses and small enterprises. By encouraging synergies between researchers and industrial partners, Inria contributes to the transfer of skills and expertise in computational technologies and provides access to top-level European and international research in order to support innovation and businesses, particularly in the region of Lille. Whether designing innovative software for business or logistics, modelling living cells or fusion plasma, or developing medical simulators or interfaces to facilitate human-computer interaction, our research opens up new possibilities that can revolutionise common practice and contribute to a better understanding of the natural phenomena which surround us. The postdoc is hosted by Team-Project RMoD. The goal of RMoD is to support remodularization of object-oriented applications. This objective is tackled from two complementary perspectives: reengineering and modularity constructs for programming languages. In the reengineering perspective we will propose new analyses to understand and restructure existing large applications (specialized package metrics, adapted visualizations, layer identification) on top of Moose [Duca08a], [Bhat12b]. http://rmod.lille.inria.fr/web/ Mission -------- Changes in the architecture may occur during the entire lifecycle of a system. Some of them might only affect local parts of a system, while others have more systemic impact. In general, we distinguish three types of approaches for handling change systematically, listed in an order of increasing severity: - Refactoring. They correspond to improvements and concern only certain components and connectors. They do not alter the offered functionality of the system. - Renovating. Sometimes, parts of the architecture are in such a bad condition that refactoring cannot work anymore. In such contexts, renovating the architecture â by restoring its fundamental principles or refreshing essential components â may be the better choice. Renovating also deals with only parts of the system. - Re-architecting. When an architecture is subject to significant changes, refactoring or renovating may not suffice. This might be the case if for example the technology platform is to be replaced by a new one, if there is a large change in business scope, or if the architecture is in such a bad shape that errors keep emerging. In such cases, re-architecting is required. The re-architecting process usually analyzes the existing architecture (e.g., using a SWOT analysis) and results in a new architecture by: a) reusing those components worthwhile to keep, b) modifying some of the existing components (refactoring) and c) re-building the rest of the components (renovating).[Ieee13] Because software engineers do not have a full understanding of the complete source code, each kind of changes may solve some problems (e.g. reduce some cycle between package), while creating new problems (e.g. creating new cycles). In this situation it would be profitable to have a tool that allows to test a possible new configuration (refactored, renovated or re-architectured) of the source code to see if the abstract property one wishes to improve, first actually improved, and second, did not improve at the expense of another equally important one. For this several alternatives new configurations have to be considered. In the RMoD team, we developed Orion [Lava10b], a tool that uses models as abstract representations of the program and enables the definition of several possible alternative versions of this program. Each version differentiates from the others by a set of refactoring operations. Currently, once an adequate version is selected, the user has to manually perform the operations on the code. Job offer description ---------------------- In this postdoc, we would like to enhance Orion in order to automatically generate code or modify the existing one once a version is chosen. Thus, it would be possible to study various alternatives of possible refactoring or restructuring of an existing program, using metrics [Abde12a], [Mord12b] or some other means [Hema12] to check the improvement in the "quality" of the code, and then ask the tool to perform the changes of the selected final solution onto the source code. The used metamodel enables a representation where code details are abstracted. A new metamodel for example AST metamodel, representing code will be introduced and the links between the two models will have to be maintained. Skills and profile -------------------- The candidate should : - hold a PhD degree in Computer Science - be fluent in English (French is an advantage but not required) - be knowledgeable in the domains of Software Engineering, maintenance, code analysis - have good programming skills in Smalltalk or be able to acquire them in a short amount of time Benefits --------- - Possibility of French courses - Help for housing - Participation for transportation - Scientific Resident card and help for husband/wife visa Additional information ----------------------- - Duration : 16 months - Salary: 2 620,84 â¬ gross/month - Monthly salary after taxes : around 2 138â¬ (medical insurance included). - Before applying, please contact the scientist advisor: nicolas.anquetil(a)inria.fr - For the first selections, please apply before March 2013, 22nd Security and defense procedure ------------------------------- In the interests of protecting its scientific and technological assets, Inria is a restricted-access establishment. Consequently, it follows special regulations for welcoming any person who wishes to work with the institute. The final acceptance of each candidate thus depends on applying this security and defense procedure. More information: http://rmod.lille.inria.fr/web/pier/blog/2013-02-22-2

Feb. 25, 2013

[Pharo-project] [update 2.0] #20568

by Marcus Denker

20568 ----- Issue 7584: [BUG]: attribute 1008 is only for JIT VMs (Part 1) http://code.google.com/p/pharo/issues/detail?id=7584 Issue 7527: SystemOrganization fileOut adds .st twice to the filename http://code.google.com/p/pharo/issues/detail?id=7527 Issue 6773: ChangesBrowser should be 100% Keyboard navigatable http://code.google.com/p/pharo/issues/detail?id=6773 Issue 7561: Debugger step over #halt opens second Debugger http://code.google.com/p/pharo/issues/detail?id=7561 Diff information: http://ss3.gemstone.com/ss/Pharo20/System-Support-MarcusDenker.789.diff http://ss3.gemstone.com/ss/Pharo20/NautilusRefactoring-MarcusDenker.78.diff http://ss3.gemstone.com/ss/Pharo20/Kernel-MarcusDenker.1320.diff

Feb. 25, 2013

Re: [Pharo-project] Pharo in Debian

by phil＠highoctane.be

VM runs already. Now, packaging. but not today nor tomorrow as I am busy w/ client work. 2013/2/25 Damien Cassou <damien.cassou(a)gmail.com>: > On Fri, Feb 22, 2013 at 10:53 AM, phil(a)highoctane.be <phil(a)highoctane.be> wrote: >> Anyway, I now have a fresh Debian 6 up and running, along with SVN. >> Next step, get the VM sources, build for linux, get the VM running. >> Then, package the whole thing. Hopefully doable in beta form for >> april. > > > that would be awesome > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill >

Feb. 25, 2013

Re: [Pharo-project] Pharo in Debian

by Damien Cassou

On Fri, Feb 22, 2013 at 10:53 AM, phil(a)highoctane.be <phil(a)highoctane.be> wrote: > Anyway, I now have a fresh Debian 6 up and running, along with SVN. > Next step, get the VM sources, build for linux, get the VM running. > Then, package the whole thing. Hopefully doable in beta form for > april. that would be awesome -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

Feb. 25, 2013

Re: [Pharo-project] PharoConf Tutorial

by Tudor Girba

I know. This is also why I said we should look for volunteers :) Doru On Feb 24, 2013, at 9:52 PM, stephane ducasse <stephane.ducasse(a)free.fr> wrote: > Doru I could bring our video camera. > The problem is not really to record but to process the files after. > > Stef > > On Feb 24, 2013, at 8:41 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >> We will see if we find volunteers to record. We should be able to find some equipment. >> >> Doru >> >> On Feb 24, 2013, at 7:08 PM, "Sean P. DeNigris" <sean(a)clipperadams.com> wrote: >> >>> MartinW wrote >>>> I would love to watch a video of this tutorial (and the other tutorials at >>>> PharoConf). Will there be one? >>> >>> Yes, please! So important... even if only iPhone videos, the influence of >>> the conference and presentations will be magnified, and all the hard work >>> will reach so many more :) >>> >>> >>> >>> -- >>> View this message in context: http://forum.world.st/PharoConf-Tutorial-tp4671362p4671825.html >>> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >>> >> >> -- >> www.tudorgirba.com >> >> "Obvious things are difficult to teach." >> >> >> >> > > -- www.tudorgirba.com "Every thing should have the right to be different."

Feb. 25, 2013

[Pharo-project] ui

by Pablo R. Digonzelli

hi all , I am looking for a package for ui for pharo. Any suggestions wicha are the good ones ? TIA Ing. Pablo Digonzelli Sofware Solutions IP Soluciones SRL 25 de Mayo 521. Entrepiso A email: pdigonzelli(a)softsargentina.com email: pdigonzelli(a)gmail.com twitter: @pdigonzelli Tel: 0381 4227378 Cel: 0381 155982714

Feb. 25, 2013

Re: [Pharo-project] MNU spec

by Benjamin

What I am supposed to do then ? Ben On Feb 24, 2013, at 6:03 PM, phil(a)highoctane.be wrote: > It was Pharo #20567 >

Feb. 25, 2013

Re: [Pharo-project] Building on Debian 6 amd64: not a walk in the park but works!

by Camillo Bruni

as an immediate response to that issue I started adding new flavors of linux slaves to our build system. Like that we are more certain that the VM will actually work under different circumstances. - debian 6.0.6 64bit - fedora 17 64bit - windows-xp I will spend some more time tomorrow to fully install them (and make sure our installation instructions are up to date). On 2013-02-24, at 22:25, phil(a)highoctane.be wrote: > Camillo, > > The zeronconf version is build with an older GLIBC and fails when > started on deb6 amd64. > > Stef, > > Look at what comes from unzipping the build on files.pharo.org: > > root@devdebian:/home/philippeback/Downloads/pharovm91# ./pharo > ./pharo: /lib32/libc.so.6: version `GLIBC_2.15' not found (required by ./pharo) > root@devdebian:/home/philippeback/Downloads/pharovm91# > > No matter how many lib32 libs are in there. > > Phil > > 2013/2/24 Camillo Bruni <camillobruni(a)gmail.com>: >> >> On 2013-02-24, at 21:25, "phil(a)highoctane.be" <phil(a)highoctane.be> wrote: >> >>> Because I am not interested in just getting C sources, but >>> understanding the VM build process from scratch. >>> >>> Also, because that version fails with the GLIBC level problem (this >>> includes the zeroconf script). >> >> the easiest solution here would be for us to switch to an older ubuntu machine >> and build the VM there with older glibc versions present. Actually might be not >> that bad to see what happens on an older machine :) >> >>> I want to be able to make a debian package for Pharo, so, having Pharo >>> running is step #1. >>> >>> apt-get install pharo >>> >>> Phil >>> >>> 2013/2/24 stephane ducasse <stephane.ducasse(a)free.fr>: >>>> Hi phil >>>> >>>> why do you not use the pharo git version? >>>> >>>> Stef >>>> >>>> On Feb 24, 2013, at 8:21 PM, phil(a)highoctane.be wrote: >>>> >>>>> I've been trying to build pharo on debian 6 amd64 >>>>> >>>>> I've installed: >>>>> >>>>> libc6dev-i386 >>>>> ia32-libs >>>>> >>>>> Then downloaded coglinux from Eliot's site. Launching squeak on the >>>>> generator.image works and sources have been generated with: >>>>> >>>>> PharoVMBuilder build. >>>>> >>>>> Things went smooth for that step. >>>>> >>>>> Then I went to build/ and did a: >>>>> >>>>> cmake . >>>>> >>>>> No problems >>>>> >>>>> then make gave me trouble. >>>>> >>>>> root@devdebian:/home/philippeback/Documents/Smalltalk/2-MyWorkspaces/workspaceVMOSXFromBook/blessed/build# >>>>> cmake . >>>>> -- The C compiler identification is GNU >>>>> -- The CXX compiler identification is GNU >>>>> -- Check for working C compiler: /usr/bin/gcc >>>>> -- Check for working C compiler: /usr/bin/gcc -- works >>>>> -- Detecting C compiler ABI info >>>>> -- Detecting C compiler ABI info - done >>>>> -- Check for working CXX compiler: /usr/bin/c++ >>>>> -- Check for working CXX compiler: /usr/bin/c++ -- works >>>>> -- Detecting CXX compiler ABI info >>>>> -- Detecting CXX compiler ABI info - done >>>>> >>>>> Adding internal plugin: ADPCMCodecPlugin >>>>> Adding internal plugin: AsynchFilePlugin >>>>> Adding internal plugin: B2DPlugin >>>>> Adding internal plugin: BitBltPlugin >>>>> Adding internal plugin: BMPReadWriterPlugin >>>>> Adding internal plugin: CroquetPlugin >>>>> Adding internal plugin: ZipPlugin >>>>> Adding internal plugin: DropPlugin >>>>> Adding internal plugin: DSAPrims >>>>> Adding internal plugin: FFTPlugin >>>>> Adding internal plugin: FileCopyPlugin >>>>> Adding internal plugin: FilePlugin >>>>> Adding internal plugin: FloatArrayPlugin >>>>> Adding internal plugin: FloatMathPlugin >>>>> Adding internal plugin: IA32ABI >>>>> Adding internal plugin: JoystickTabletPlugin >>>>> Adding internal plugin: JPEGReaderPlugin >>>>> Adding internal plugin: JPEGReadWriter2Plugin >>>>> Adding internal plugin: Klatt >>>>> Adding internal plugin: LargeIntegers >>>>> Adding internal plugin: Matrix2x3Plugin >>>>> Adding internal plugin: MIDIPlugin >>>>> Adding internal plugin: MiscPrimitivePlugin >>>>> Adding internal plugin: Mpeg3Plugin >>>>> Adding internal plugin: RePlugin >>>>> Adding internal plugin: SecurityPlugin >>>>> Adding internal plugin: SerialPlugin >>>>> Adding internal plugin: SocketPlugin >>>>> Adding internal plugin: SoundCodecPrims >>>>> Adding internal plugin: SoundPlugin >>>>> Adding internal plugin: StarSqueakPlugin >>>>> Adding internal plugin: SurfacePlugin >>>>> Adding internal plugin: LocalePlugin >>>>> Adding internal plugin: NativeBoostPlugin >>>>> Adding internal plugin: UnixOSProcessPlugin >>>>> Adding external plugin: B3DAcceleratorPlugin >>>>> Adding external plugin: SqueakFFIPrims >>>>> Adding external plugin: InternetConfigPlugin >>>>> Adding external plugin: FT2Plugin >>>>> Adding external plugin: SqueakSSL >>>>> Adding module: vm-display-null >>>>> Adding module: vm-display-X11 >>>>> Adding module: vm-sound-ALSA >>>>> Adding module: vm-sound-null >>>>> -- Configuring done >>>>> -- Generating done >>>>> -- Build files have been written to: >>>>> /home/philippeback/Documents/Smalltalk/2-MyWorkspaces/workspaceVMOSXFromBook/blessed/build >>>>> root@devdebian:/home/philippeback/Documents/Smalltalk/2-MyWorkspaces/workspaceVMOSXFromBook/blessed/build# >>>>> make >>>>> Scanning dependencies of target SqueakSSL >>>>> [ 0%] Building C object >>>>> SqueakSSL/CMakeFiles/SqueakSSL.dir/home/philippeback/Documents/Smalltalk/2-MyWorkspaces/workspaceVMOSXFromBook/blessed/src/plugins/SqueakSSL/SqueakSSL.c.o >>>>> [ 1%] Building C object >>>>> SqueakSSL/CMakeFiles/SqueakSSL.dir/home/philippeback/Documents/Smalltalk/2-MyWorkspaces/workspaceVMOSXFromBook/blessed/platforms/unix/plugins/SqueakSSL/sqUnixOpenSSL.c.o >>>>> Linking C shared library >>>>> /home/philippeback/Documents/Smalltalk/2-MyWorkspaces/workspaceVMOSXFromBook/blessed/results/libSqueakSSL.so >>>>> /usr/bin/ld: skipping incompatible >>>>> /usr/lib/gcc/x86_64-linux-gnu/4.4.5/../../../libssl.so when searching >>>>> for -lssl >>>>> /usr/bin/ld: skipping incompatible >>>>> /usr/lib/gcc/x86_64-linux-gnu/4.4.5/../../../libssl.a when searching >>>>> for -lssl >>>>> /usr/bin/ld: skipping incompatible /usr/lib/libssl.so when searching for -lssl >>>>> /usr/bin/ld: skipping incompatible /usr/lib/libssl.a when searching for -lssl >>>>> /usr/bin/ld: cannot find -lssl >>>>> collect2: ld returned 1 exit status >>>>> make[2]: *** [/home/philippeback/Documents/Smalltalk/2-MyWorkspaces/workspaceVMOSXFromBook/blessed/results/libSqueakSSL.so] >>>>> Error 1 >>>>> make[1]: *** [SqueakSSL/CMakeFiles/SqueakSSL.dir/all] Error 2 >>>>> make: *** [all] Error 2 >>>>> >>>>> >>>>> So, I did a basic: d# ln -s /usr/lib32/libssl.so.0.9.8 /usr/lib32/libssl.so >>>>> >>>>> Which got me further. >>>>> >>>>> The build then failed (some kind of process problem: >>>>> >>>>> >>>>> [ 81%] Building C object >>>>> StarSqueakPlugin/CMakeFiles/StarSqueakPlugin.dir/home/philippeback/Documents/Smalltalk/2-MyWorkspaces/workspaceVMOSXFromBook/blessed/src/plugins/StarSqueakPlugin/StarSqueakPlugin.c.o >>>>> Linking C static library libStarSqueakPlugin.a >>>>> [ 81%] Built target StarSqueakPlugin >>>>> Scanning dependencies of target SurfacePlugin >>>>> [ 82%] Building C object >>>>> SurfacePlugin/CMakeFiles/SurfacePlugin.dir/home/philippeback/Documents/Smalltalk/2-MyWorkspaces/workspaceVMOSXFromBook/blessed/platforms/Cross/plugins/SurfacePlugin/SurfacePlugin.c.o >>>>> Linking C static library libSurfacePlugin.a >>>>> [ 82%] Built target SurfacePlugin >>>>> Scanning dependencies of target LocalePlugin >>>>> [ 83%] Building C object >>>>> LocalePlugin/CMakeFiles/LocalePlugin.dir/home/philippeback/Documents/Smalltalk/2-MyWorkspaces/workspaceVMOSXFromBook/blessed/src/plugins/LocalePlugin/LocalePlugin.c.o >>>>> [ 83%] Building C object >>>>> LocalePlugin/CMakeFiles/LocalePlugin.dir/home/philippeback/Documents/Smalltalk/2-MyWorkspaces/workspaceVMOSXFromBook/blessed/platforms/unix/plugins/LocalePlugin/sqUnixLocale.c.o >>>>> /home/philippeback/Documents/Smalltalk/2-MyWorkspaces/workspaceVMOSXFromBook/blessed/platforms/unix/plugins/LocalePlugin/sqUnixLocale.c: >>>>> In function âsqLocGetCountryIntoâ: >>>>> /home/philippeback/Documents/Smalltalk/2-MyWorkspaces/workspaceVMOSXFromBook/blessed/platforms/unix/plugins/LocalePlugin/sqUnixLocale.c:754: >>>>> warning: initialization discards qualifiers from pointer target type >>>>> /home/philippeback/Documents/Smalltalk/2-MyWorkspaces/workspaceVMOSXFromBook/blessed/platforms/unix/plugins/LocalePlugin/sqUnixLocale.c: >>>>> In function âsqLocGetLanguageIntoâ: >>>>> /home/philippeback/Documents/Smalltalk/2-MyWorkspaces/workspaceVMOSXFromBook/blessed/platforms/unix/plugins/LocalePlugin/sqUnixLocale.c:759: >>>>> warning: initialization discards qualifiers from pointer target type >>>>> Linking C static library libLocalePlugin.a >>>>> [ 83%] Built target LocalePlugin >>>>> Scanning dependencies of target NativeBoostPlugin >>>>> [ 83%] Building C object >>>>> NativeBoostPlugin/CMakeFiles/NativeBoostPlugin.dir/home/philippeback/Documents/Smalltalk/2-MyWorkspaces/workspaceVMOSXFromBook/blessed/src/plugins/NativeBoostPlugin/NativeBoostPlugin.c.o >>>>> /home/philippeback/Documents/Smalltalk/2-MyWorkspaces/workspaceVMOSXFromBook/blessed/src/plugins/NativeBoostPlugin/NativeBoostPlugin.c: >>>>> In function âprimitiveDlopenFnâ: >>>>> /home/philippeback/Documents/Smalltalk/2-MyWorkspaces/workspaceVMOSXFromBook/blessed/src/plugins/NativeBoostPlugin/NativeBoostPlugin.c:166: >>>>> warning: passing argument 1 of âpositive32BitIntegerForâ makes integer >>>>> from pointer without a cast >>>>> /home/philippeback/Documents/Smalltalk/2-MyWorkspaces/workspaceVMOSXFromBook/blessed/src/plugins/NativeBoostPlugin/NativeBoostPlugin.c:90: >>>>> note: expected âsqIntâ but argument is of type âvoid *â >>>>> /home/philippeback/Documents/Smalltalk/2-MyWorkspaces/workspaceVMOSXFromBook/blessed/src/plugins/NativeBoostPlugin/NativeBoostPlugin.c: >>>>> In function âprimitiveDlsymFnâ: >>>>> /home/philippeback/Documents/Smalltalk/2-MyWorkspaces/workspaceVMOSXFromBook/blessed/src/plugins/NativeBoostPlugin/NativeBoostPlugin.c:184: >>>>> warning: passing argument 1 of âpositive32BitIntegerForâ makes integer >>>>> from pointer without a cast >>>>> /home/philippeback/Documents/Smalltalk/2-MyWorkspaces/workspaceVMOSXFromBook/blessed/src/plugins/NativeBoostPlugin/NativeBoostPlugin.c:90: >>>>> note: expected âsqIntâ but argument is of type âvoid *â >>>>> Linking C static library libNativeBoostPlugin.a >>>>> [ 83%] Built target NativeBoostPlugin >>>>> Scanning dependencies of target UnixOSProcessPlugin >>>>> [ 83%] Building C object >>>>> UnixOSProcessPlugin/CMakeFiles/UnixOSProcessPlugin.dir/home/philippeback/Documents/Smalltalk/2-MyWorkspaces/workspaceVMOSXFromBook/blessed/src/plugins/UnixOSProcessPlugin/UnixOSProcessPlugin.c.o >>>>> ^Cmake[2]: *** wait: No child processes. Stop. >>>>> make[2]: *** Waiting for unfinished jobs.... >>>>> make[2]: *** wait: No child processes. Stop. >>>>> make[1]: *** wait: No child processes. Stop. >>>>> make[1]: *** Waiting for unfinished jobs.... >>>>> make[1]: *** wait: No child processes. Stop. >>>>> make: *** wait: No child processes. Stop. >>>>> make: *** Waiting for unfinished jobs.... >>>>> make: *** wait: No child processes. Stop. >>>>> >>>>> >>>>> Restarted make then it proceeded. >>>>> >>>>> Then failed on libfreetype >>>>> >>>>> >>>>> /home/philippeback/Documents/Smalltalk/2-MyWorkspaces/workspaceVMOSXFromBook/blessed/src/plugins/FT2Plugin/FT2Plugin.c:1071: >>>>> warning: assignment discards qualifiers from pointer target type >>>>> Linking C shared library >>>>> /home/philippeback/Documents/Smalltalk/2-MyWorkspaces/workspaceVMOSXFromBook/blessed/results/libFT2Plugin.so >>>>> /usr/bin/ld: skipping incompatible >>>>> /usr/lib/gcc/x86_64-linux-gnu/4.4.5/../../../libfreetype.so when >>>>> searching for -lfreetype >>>>> /usr/bin/ld: skipping incompatible >>>>> /usr/lib/gcc/x86_64-linux-gnu/4.4.5/../../../libfreetype.a when >>>>> searching for -lfreetype >>>>> /usr/bin/ld: skipping incompatible /usr/lib/libfreetype.so when >>>>> searching for -lfreetype >>>>> /usr/bin/ld: skipping incompatible /usr/lib/libfreetype.a when >>>>> searching for -lfreetype >>>>> /usr/bin/ld: cannot find -lfreetype >>>>> collect2: ld returned 1 exit status >>>>> make[2]: *** [/home/philippeback/Documents/Smalltalk/2-MyWorkspaces/workspaceVMOSXFromBook/blessed/results/libFT2Plugin.so] >>>>> Error 1 >>>>> make[1]: *** [FT2Plugin/CMakeFiles/FT2Plugin.dir/all] Error 2 >>>>> make: *** [all] Error 2 >>>>> root@devdebian:/home/philippeback/Documents/Smalltalk/2-MyWorkspaces/workspaceVMOSXFromBook/blessed/build# >>>>> >>>>> Tried this: >>>>> >>>>> ln -s /usr/lib32/libfreetype.so.6 /usr/lib32/libfreetype.so >>>>> >>>>> One step ahead... >>>>> >>>>> Then crash: >>>>> >>>>> >>>>> In file included from >>>>> /home/philippeback/Documents/Smalltalk/2-MyWorkspaces/workspaceVMOSXFromBook/blessed/platforms/unix/vm/sqUnixMain.c:41: >>>>> /home/philippeback/Documents/Smalltalk/2-MyWorkspaces/workspaceVMOSXFromBook/blessed/platforms/Cross/vm/sqSCCSVersion.h:17:54: >>>>> error: vmVersionInfo.h: No such file or directory >>>>> /home/philippeback/Documents/Smalltalk/2-MyWorkspaces/workspaceVMOSXFromBook/blessed/platforms/Cross/vm/sqSCCSVersion.h:20:3: >>>>> error: #error "Revision information not specified" >>>>> In file included from >>>>> /home/philippeback/Documents/Smalltalk/2-MyWorkspaces/workspaceVMOSXFromBook/blessed/platforms/unix/vm/sqUnixMain.c:41: >>>>> /home/philippeback/Documents/Smalltalk/2-MyWorkspaces/workspaceVMOSXFromBook/blessed/platforms/Cross/vm/sqSCCSVersion.h: >>>>> In function âsourceVersionStringâ: >>>>> /home/philippeback/Documents/Smalltalk/2-MyWorkspaces/workspaceVMOSXFromBook/blessed/platforms/Cross/vm/sqSCCSVersion.h:25: >>>>> error: âREVISION_STRINGâ undeclared (first use in this function) >>>>> /home/philippeback/Documents/Smalltalk/2-MyWorkspaces/workspaceVMOSXFromBook/blessed/platforms/Cross/vm/sqSCCSVersion.h:25: >>>>> error: (Each undeclared identifier is reported only once >>>>> /home/philippeback/Documents/Smalltalk/2-MyWorkspaces/workspaceVMOSXFromBook/blessed/platforms/Cross/vm/sqSCCSVersion.h:25: >>>>> error: for each function it appears in.) >>>>> /home/philippeback/Documents/Smalltalk/2-MyWorkspaces/workspaceVMOSXFromBook/blessed/platforms/unix/vm/sqUnixMain.c: >>>>> In function âgetRedzoneSizeâ: >>>>> /home/philippeback/Documents/Smalltalk/2-MyWorkspaces/workspaceVMOSXFromBook/blessed/platforms/unix/vm/sqUnixMain.c:2012: >>>>> warning: assignment from incompatible pointer type >>>>> make[2]: *** [CMakeFiles/pharo.dir/home/philippeback/Documents/Smalltalk/2-MyWorkspaces/workspaceVMOSXFromBook/blessed/platforms/unix/vm/sqUnixMain.c.o] >>>>> Error 1 >>>>> make[1]: *** [CMakeFiles/pharo.dir/all] Error 2 >>>>> make: *** [all] Error 2 >>>>> >>>>> Looks like the vmVersionInfo.h hasn't been generated in the build/ >>>>> folder or something. Mayber it wasn't there. I copied the one I had >>>>> from OSX >>>>> >>>>> Went somewhat further as well.. but not quite. >>>>> >>>>> >>>>> Linking C executable >>>>> /home/philippeback/Documents/Smalltalk/2-MyWorkspaces/workspaceVMOSXFromBook/blessed/results/pharo >>>>> [ 97%] Built target pharo >>>>> Scanning dependencies of target vm-display-null >>>>> [ 98%] Building C object >>>>> vm-display-null/CMakeFiles/vm-display-null.dir/home/philippeback/Documents/Smalltalk/2-MyWorkspaces/workspaceVMOSXFromBook/blessed/platforms/unix/vm-display-null/sqUnixDisplayNull.c.o >>>>> /home/philippeback/Documents/Smalltalk/2-MyWorkspaces/workspaceVMOSXFromBook/blessed/platforms/unix/vm-display-null/sqUnixDisplayNull.c:176: >>>>> warning: initialization from incompatible pointer type >>>>> Linking C shared library >>>>> /home/philippeback/Documents/Smalltalk/2-MyWorkspaces/workspaceVMOSXFromBook/blessed/results/vm-display-null >>>>> [ 98%] Built target vm-display-null >>>>> Scanning dependencies of target vm-display-X11 >>>>> [ 99%] Building C object >>>>> vm-display-X11/CMakeFiles/vm-display-X11.dir/home/philippeback/Documents/Smalltalk/2-MyWorkspaces/workspaceVMOSXFromBook/blessed/platforms/unix/vm-display-X11/sqUnixX11.c.o >>>>> [ 99%] Building C object >>>>> vm-display-X11/CMakeFiles/vm-display-X11.dir/home/philippeback/Documents/Smalltalk/2-MyWorkspaces/workspaceVMOSXFromBook/blessed/platforms/unix/vm-display-X11/sqUnixMozilla.c.o >>>>> Linking C shared library >>>>> /home/philippeback/Documents/Smalltalk/2-MyWorkspaces/workspaceVMOSXFromBook/blessed/results/vm-display-X11 >>>>> /usr/bin/ld: cannot find -lSM >>>>> collect2: ld returned 1 exit status >>>>> make[2]: *** [/home/philippeback/Documents/Smalltalk/2-MyWorkspaces/workspaceVMOSXFromBook/blessed/results/vm-display-X11] >>>>> Error 1 >>>>> make[1]: *** [vm-display-X11/CMakeFiles/vm-display-X11.dir/all] Error 2 >>>>> make: *** [all] Error 2 >>>>> >>>>> >>>>> What's that SM lib? >>>>> >>>>> Yet another symlinking dude.. >>>>> >>>>> ln -s /usr/lib32/libSM.so.6 /usr/lib32/libSM.so >>>>> >>>>> Ha, the beast still resists... >>>>> >>>>> >>>>> [ 98%] Built target vm-display-null >>>>> Linking C shared library >>>>> /home/philippeback/Documents/Smalltalk/2-MyWorkspaces/workspaceVMOSXFromBook/blessed/results/vm-display-X11 >>>>> /usr/bin/ld: cannot find -lICE >>>>> collect2: ld returned 1 exit status >>>>> make[2]: *** [/home/philippeback/Documents/Smalltalk/2-MyWorkspaces/workspaceVMOSXFromBook/blessed/results/vm-display-X11] >>>>> Error 1 >>>>> make[1]: *** [vm-display-X11/CMakeFiles/vm-display-X11.dir/all] Error 2 >>>>> make: *** [all] Error 2 >>>>> >>>>> So.... >>>>> >>>>> ln -s /usr/lib32/libICE.so.6 /usr/lib32/libICE.so >>>>> >>>>> same for GL >>>>> >>>>> >>>>> ln -s /usr/lib32/libGL.so.1 /usr/lib32/libGL.so >>>>> >>>>> and X11 (I am getting tired...) >>>>> >>>>> ln -s /usr/lib32/libX11.so.6 /usr/lib32/libX11.so >>>>> >>>>> Looks like we are done. Not sure but... >>>>> >>>>> root@devdebian:/home/philippeback/Documents/Smalltalk/2-MyWorkspaces/workspaceVMOSXFromBook/blessed/build# >>>>> make >>>>> [ 1%] Built target SqueakSSL >>>>> [ 1%] Built target DSAPrims >>>>> [ 2%] Built target FFTPlugin >>>>> [ 3%] Built target FileCopyPlugin >>>>> [ 5%] Built target FilePlugin >>>>> [ 5%] Built target BMPReadWriterPlugin >>>>> [ 6%] Built target ZipPlugin >>>>> [ 7%] Built target DropPlugin >>>>> [ 8%] Built target CroquetPlugin >>>>> [ 8%] Built target ADPCMCodecPlugin >>>>> [ 9%] Built target BitBltPlugin >>>>> [ 9%] Built target B2DPlugin >>>>> [ 10%] Built target AsynchFilePlugin >>>>> [ 10%] Built target FloatArrayPlugin >>>>> [ 11%] Built target IA32ABI >>>>> [ 29%] Built target FloatMathPlugin >>>>> [ 30%] Built target JoystickTabletPlugin >>>>> [ 30%] Built target JPEGReaderPlugin >>>>> [ 55%] Built target JPEGReadWriter2Plugin >>>>> [ 56%] Built target Klatt >>>>> [ 56%] Built target LargeIntegers >>>>> [ 57%] Built target Matrix2x3Plugin >>>>> [ 58%] Built target MIDIPlugin >>>>> [ 58%] Built target MiscPrimitivePlugin >>>>> [ 73%] Built target Mpeg3Plugin >>>>> [ 76%] Built target RePlugin >>>>> [ 77%] Built target SecurityPlugin >>>>> [ 78%] Built target SerialPlugin >>>>> [ 79%] Built target SocketPlugin >>>>> [ 80%] Built target SoundCodecPrims >>>>> [ 81%] Built target SoundPlugin >>>>> [ 81%] Built target StarSqueakPlugin >>>>> [ 82%] Built target SurfacePlugin >>>>> [ 83%] Built target LocalePlugin >>>>> [ 83%] Built target NativeBoostPlugin >>>>> [ 83%] Built target UnixOSProcessPlugin >>>>> [ 85%] Built target B3DAcceleratorPlugin >>>>> [ 87%] Built target SqueakFFIPrims >>>>> [ 88%] Built target InternetConfigPlugin >>>>> [ 88%] Built target FT2Plugin >>>>> [ 97%] Built target pharo >>>>> [ 98%] Built target vm-display-null >>>>> [ 99%] Built target vm-display-X11 >>>>> [ 99%] Built target vm-sound-ALSA >>>>> [100%] Built target vm-sound-null >>>>> >>>>> A little go: >>>>> >>>>> root@devdebian:/home/philippeback/Documents/Smalltalk/2-MyWorkspaces/workspaceVMOSXFromBook/blessed/results# >>>>> ./pharo >>>>> Could not open the pharo image file `pharo.image'. >>>>> >>>>> There are three ways to open a pharo image file. You can: >>>>> 1. Put copies of the default image and changes files in this directory. >>>>> 2. Put the name of the image file on the command line when you >>>>> run pharo (use the `-help' option for more information). >>>>> 3. Set the environment variable PHARO_IMAGE to the name of the image >>>>> that you want to use by default. >>>>> >>>>> For more information, type: `man pharo' (without the quote characters). >>>>> >>>>> Yes! >>>>> >>>>> And then, >>>>> >>>>> >>>>> root@devdebian:/home/philippeback/Documents/Smalltalk/2-MyWorkspaces/workspaceVMOSXFromBook/blessed/image# >>>>> ../results/pharo generator.image >>>>> >>>>> Working! Screenshot as proof. >>>>> >>>>> But the image complains that the VM is too old. I don't know where it >>>>> goes to look after that, vmVersionInfo.h for sure. >>>>> >>>>> But it works well. >>>>> >>>>> Now, the next step would be doing the packaging. >>>>> >>>>> Phil >>>>> <Capture dâÃ©cran 2013-02-24 Ã 20.20.10.png> >>>> >>>> >>> >> >> >

Feb. 25, 2013