> On 3 Nov 2016, at 15:37, Marcus Denker <
[hidden email]> wrote:
>
> Hello,
>
> it seems that a 64bit slave was installed without 32bit support. As
>
> sudo aptitude install ia32-libs
>
> did not work (no aptitude), and “apt-get” did not know ia32-libs,
This is how I normally do it
https://github.com/svenvc/pharo-server-tools/blob/master/ubuntu-32bit-support-on-64bit.shAlthough maybe more is needed (it is enough for mine applications).
> I decided to shut down the slave for now.
OK, Thanks.
> Marcus
>
>> On 31 Oct 2016, at 23:28, Sven Van Caekenberghe <
[hidden email]> wrote:
>>
>> It already got reported twice, there are issues for it, but so far no luck (i.e. no actual resolution).
>>
>> I would guess that before the linux os of the CI slaves ran in 32-bit, while now it got upgraded to 64-bit.
>>
>> CC-ing pharo-dev
>>
>>> On 28 Oct 2016, at 14:12, Johan Brichau <
[hidden email]> wrote:
>>>
>>> Does anybody have any idea why this is failing:
>>>
>>>> /pharo: line 11: <
https://ci.inria.fr/pharo-contribution/job/Grease/PHARO=40,VERSION=stable,VM=vm/ws/pharo-vm/pharo>: No such file or directory
>>>
>>> Did not look at it yet, but it seems like something changed on de CI server??
>>>
>>> Johan_______________________________________________
>>> seaside-dev mailing list
>>>
[hidden email]
>>>
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev>>
>>
>
Locked
