ah, that’s because headless mode is a fake headless (we will arrive to a real headless soon, but not yet). what actually happens is that VM is creating the window but not showing it… that’s why it needs it :S
Esteban > On 20 Aug 2015, at 15:08, Sven Van Caekenberghe <s...@stfx.eu> wrote: > > >> On 20 Aug 2015, at 15:05, Esteban Lorenzano <esteba...@gmail.com> wrote: >> >> most probably you are missing: >> >> sudo apt-get -qq install libfreetype6:i386 > > Yes, of course, but isn't that an X11 library that will pull in all of X11 > and friends on a server that does not need a GUI ? I run all my servers pure > command line, out of principle. > > Why would a headless server even have to access a font ? > >> cheers, >> Esteban >> >>> On 20 Aug 2015, at 15:00, Sven Van Caekenberghe <s...@stfx.eu> wrote: >>> >>> Anyone ? >>> >>>> On 12 Aug 2015, at 17:36, Sven Van Caekenberghe <s...@stfx.eu> wrote: >>>> >>>> Today I did a new pharo install (get.pharo.org/40+vm) on a server (ubuntu >>>> 12.04.3 LTS, 64-bit with 32-bit libs). All went fine, as usual, but I was >>>> confused about the following: >>>> >>>> $ ./st-exec.st run-t3-proxies start t3-proxies >>>> Executing ./st-exec.st run-t3-proxies start t3-proxies >>>> Working directory /home/t3/pharo/t3-proxies >>>> Starting run-t3-proxies in background >>>> /home/t3/pharo/t3-proxies/../bin/pharo-vm/pharo --nodisplay >>>> /home/t3/pharo/t3-proxies/t3-proxies.image >>>> /home/t3/pharo/t3-proxies/run-t3-proxies.st >>>> >>>> ioLoadModule(/home/t3/pharo/bin/pharo-vm/libFT2Plugin.so): >>>> libfreetype.so.6: cannot open shared object file: No such file or directory >>>> >>>> Why is freetype needed/accessed for a headless image (that otherwise runs >>>> happily) ? >>>> >>>> Other operations (building, saving, ..) do not produce the error/warning. >>>> >>>> Sven >>>> >>> >>> >> > >
