January 2019 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] naming convention for pharo-vm/lib/pharo/* directory?

by Alistair Grant

Hi Dale, On Fri, 25 Jan 2019 at 22:10, Dale Henrichs <dale.henrichs(a)gemtalksystems.com> wrote: > > Thanks, Nicolas (and Sven), > > VM search path is what I am looking for (UFFI external modules) and I am curious whether or not this path `pharo-vm/lib/pharo/5.0-201806281256` is constant or variable for the various Pharo versions or does it vary based on the vm version/build number ... pharo6.0 and pharo.1 appear to have the same path ... haven't looked at Pharo7.0 ... and hopefully the path is the same for mac and unix or does it vary ... I don't have a mac to readily test on:) > > The bash script that copies my unix/mac .so/.dylib files will be run immediately after the image and vm have been downloaded so I won't be running the image itself (unless I have to). Currently, the download, installation and build of the pharo client for GemStone is built by a bash script... > > I'm going to assume for now that the gci libraries will be shoveled into the pharo-vm/lib/5.0-* directory until someone gives me a more definitive answer... pharo-vm/lib/5.0-* will probably work for any VM that is distributed through files.pharo.org, but may not be true for custom built VMs, e.g.: Installed via zero-conf: $ vm/pharo --version | grep plugin plugin path: /home/alistair/pharo7/pharo64.36/vm/pharo-vm/lib/pharo/5.0-201901051900 [default: /home/alistair/pharo7/pharo64.36/vm/pharo-vm/lib/pharo/5.0-201901051900/] vs built locally: $ vm.01/pharo --version | grep plugin plugin path: vm.01/lib/pharo/5.0-201901040101 [default: /home/alistair/pharo7/pharo64.36/vm.01/lib/pharo/5.0-201901040101/] Parsing the output of pharo --version is probably the best bet. HTH, Alistair

Jan. 28, 2019

Re: [Pharo-dev] Build problems

by Alistair Grant

Hi Stef, The "unbound variable" error has been fixed in https://github.com/pharo-project/pharo/pull/2368 (at least no one has complained in the last 8 hours :-)). Cheers, Alistair On Sun, 27 Jan 2019 at 20:35, ducasse <stepharo(a)netcourrier.com> wrote: > > Hi > > There are several problems with the build: > > First > > > [32] load : Refactoring2-Transformations-Tests-tonel.1 > > > [32] postload : baseline [BaselineOfIDE] >> postload:package: > > > [32] load : Deprecated70-tonel.1 > > > [32] postload : baseline [BaselineOfPharo] >> postload:package: > > > [32] + /builds/workspace/uest_and_branch_Pipeline_PR-2362/32/bootstrap-cache/vmtarget/pharo --headless Pharo7.0-PR-32bit-67f8280.image --no-default-preferences eval --save 'FFIMethodRegistry resetAll. PharoSourcesCondenser condenseNewSources. Smalltalk garbageCollect' > > > [32] pthread_setschedparam failed: Operation not permitted > > > [32] This VM uses a separate heartbeat thread to update its internal clock > > > [32] and handle events. For best operation, this thread should run at a > > > second > > > [32] + . /builds/workspace/uest_and_branch_Pipeline_PR-2362/32/bootstrap/scripts/envversion.sh > > > [32] + set_version_variables > > > [32] /builds/workspace/uest_and_branch_Pipeline_PR-2362/32/bootstrap/scripts/envversion.sh: line 89: BOOTSTRAP_REPOSITORY: unbound variable > > > [Pipeline] [32] } > > > [Pipeline] [32] // dir > > > [Pipeline] [32] } > > > [Pipeline] [32] // stage > > > [Pipeline] [32] archiveArtifacts > > > [32] Archiving artifacts > > > [32] Recording fingerprints > > > [Pipeline] [32] cleanWs > > > [32] [WS-CLEANUP] Deleting project workspace... > > > [32] [WS-CLEANUP] Deferred wipeout is used... > > > [32] [WS-CLEANUP] done > > > [Pipeline] [32] } > >

Jan. 28, 2019

Slowdown in writing code (to changes?) in 7 vs 6

by stephan

Writing code in this way seems to be about 2.4 times slower in Pharo 7 vs Pharo 6. I also tried with smaller numbers, and there I noticed a rather high number of calls to File>>basicOpenForWrite:. With 4*4*4 methods, 768, and 5*5*5 1502. |organizer aToZ| organizer := RPackageOrganizer default. aToZ := 'ABCDEFGHIJKLMNOPQRSTUVWXYZ'. [ aToZ do: [ :ch | |packageName package| packageName := 'Package', ch asString. package := organizer createPackageNamed: packageName. aToZ do: [ :classCh | |cls| cls := Object subclass: (ch asString, 'Class', classCh asString) asSymbol instanceVariableNames: '' classVariableNames: '' poolDictionaries: '' package: packageName. package addClassDefinition: cls. aToZ do: [ :m | cls compile: m asString asLowercase, String cr, ' ^self' ] ] ] ] timeProfile (221 s vs 93) Do I need all those calls to #basicOpenForWrite? Stephan

Jan. 28, 2019