Le 16/6/15 15:25, Matthieu Lacaton a écrit :
Alright, thank you :)

I just find the 64bits / 32bits libraries-juggling annoying sometimes :(

oh yes!!!!
We hope to get a solution by december.

Stef


2015-06-16 15:12 GMT+02:00 Esteban Lorenzano <[email protected] <mailto:[email protected]>>:


    On 16 Jun 2015, at 13:47, Matthieu Lacaton
    <[email protected] <mailto:[email protected]>>
    wrote:

    Alright, thanks :)

    By the way, on a side note, when downloading the VM for windows,
    a libcairo-2.dll is provided but when using zeroconf on linux the
    cairo library is not provided with the VM. Is it intended ?
    Because the VM then checks in the system but if you only have 64
    bits libraries you need to install 32 bits ones.

    yes, this is intended.
    in linux you have to install cairo by your own.
    I suppose is because we thought it was easier for linux users (and
    we suppose most of them already have it in their systems).
    No idea if we were wrong :)

    Esteban


    2015-06-16 13:12 GMT+02:00 Esteban Lorenzano <[email protected]
    <mailto:[email protected]>>:

        Hi,

        There are some problems with the rpath we are trying to
        solve… in the mean time, best solution is to affect the
        LD_LIBRARY_PATH :(

        Esteban

        On 16 Jun 2015, at 11:47, Matthieu Lacaton
        <[email protected]
        <mailto:[email protected]>> wrote:

        Hello,

        I am currently using Archlinux and I don't have the SDL2
        library loaded into my system.
        Yesterday I downloaded the latest Pharo 5 vm and image
        thanks to the zeroconf scripts.

        When I tried to call "OSSDL2Driver hasPlugin" the return was
        "false" with the following message console :

            ioLoadModule(.../pharo-vm/libSDL2DisplayPlugin.so):
            libSDL2-2.0.so.0: cannot open shared object file: No
            such file or directory


        The library itself (libSDL2-2.0.so.0) is located in the
        pharo-vm folder, however it seems that the vm is looking for
        it somewhere else because after copying the file in
        /usr/lib32/ the VM was able to find it correctly.

        I was wondering : shouldn't the vm only rely on the SDL2
        library inside pharo-vm folder ?

        Thanks,

        Matthieu





Reply via email to