on /build.linux32x86/pharo.cog.spur/build I run ./mvm and get
make[3]: *** No rule to make target '/usr/lib/i386-linux-gnu/libssl.so', needed by 'libgit2.so.0.25.1'. Stop.
I worked around it by running sudo ln -s /lib/i386-linux-gnu/libssl.so.1.0.0 /usr/lib/i386-linux-gnu/libssl.so but shouldn't be necessary as libssl is downloaded and built by the script.
The same happens with libcrypto
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/210
Seems to be something strange with the B3DAcceleratorPlugin on 32-bit macos. The pharo libB3DAcceleratorPlugin.dylib fails to link missing:
createOpenGLTextureLayerHandle
destroyOpenGLTextureLayerHandle
getMainWindowOpenGLContext
setOpenGLTextureLayerContent
The Squeak one links, but apparently against Metal, which isn't going to work since Metal is 64-bit only (or so I've been told).
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/385
Building from the latest sources on the Cog branch, I see the attached image when loading various images using various OSX builds. I have tried the 64-bit Pharo, Squeak and newspeak builds with their associated images. I see some variation of the attached image below. If I rollback the source to the 201901172323 tag, I am able to build and load an image and see the window as expected.
<img width="811" alt="Screen Shot 2019-04-23 at 6 47 51 PM" src="https://user-images.githubusercontent.com/32800969/56627814-3fea6280-65fc-1…">
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/392
A problem with FFI is that if a callout segfaults, all of memory
including that of the Image is suspect, and execution of the Image terminates.
Occasionally I hunt around hoping to find technology to mitigate that problem.
Maybe this time in I found something... Memory Protection Keys [1]
Perhaps these could ensure Image memory safe when an FFI callout segfaults.
IIUC the main problem with protecting Image memory on every FFI callout
is the time it would take update the flags on every page of Image memory.
Would being able to change the protection of a massive number of pages
with one syscall make it feasible to wrap them around FFI callouts?
This may be useful at least where the FFI use is more about reuse of
existing functionality than about performance.
Or at least useful while someone is learning/experimenting with FFI for
the first time or while becoming familiar with some external library.
Further info at [2] & [3].
cheers -ben
[1] https://lwn.net/Articles/643797/
[2] http://man7.org/linux/man-pages/man7/pkeys.7.html
[3] https://lwn.net/Articles/689395/
Hi,
Sorry for causing some unintended Spam. I just noticed that on the
OpenSmalltalk VM .travis.yml there are some notification lines:
notifications:
slack:
secure: ...
notifications:
email:
- vm-dev(a)lists.squeakfoundation.org
Currently I am fixing the CMake based build system for the minheadless VM
for a client. So far I managed to the produce the same kind of results as
the normal build system on my local machines for both Linux and Mac. I
managed to include the build dependencies for Pharo on the cmake based
system. Currently, I am now fixing this VM for Travis CI by using my local
account. To avoid this Spam, now I am commenting these lines.
After I get this VM variant building for both, Squeak and Pharo on Travis
and on appveyor, I will submit a proper pull request.
For the curious people, for now I am pushing my changes here:
https://github.com/ronsaldo/opensmalltalk-vm/tree/feature/minheadless-ci
Best regards,
Ronie