On 2013-01-24 3:54 PM, Bert Freudenberg wrote:
On 24.01.2013, at 12:49, Ken Causey ken@kencausey.com wrote:
On 01/24/2013 02:39 PM, Chris Cunnington wrote:
On 2013-01-24 3:18 PM, Ken Causey wrote:
On 01/24/2013 12:10 PM, Chris Cunnington wrote:
http://box3.squeak.org:8624 http://box3.squeak.org:8624/error
This is the next iteration of the squeak.org image. It's getting closer to completion, I think. There is a nascent error message.
(If anyone is wondering about attribution for that image, I looked at the site it came from [1] and I do not see how it is supposed to be attributed. AFAICT, the maker has not indicated who they are or how they want to be attributed.).
The image is running on box3, not box4, because I get this lovely error:
chriscunnington@squeak-box4:~$ ioLoadModule(/home/chriscunnington/coglinux/lib/squeak/4.0-2640/libcrypto.so):
/home/chriscunnington/coglinux/lib/squeak/4.0-2640/libcrypto.so: wrong ELF class: ELFCLASS64
Something 32 is not playing well with something 64. Perhaps I need to install a 32-bit version of libcrypto.so on box4?
It's already installed
/usr/lib32/libcrypto.so
Did you try using the classic Squeak VM? /usr/local/bin/squeak
OK, it sounds like I only need to change the symlink [1] to /usr/lib32/libcrypto.so. That'll probably do it.
Chris
[1] chriscunnington@squeak-box4:~/coglinux/lib/squeak/4.0-2640$ file libcrypto.so libcrypto.so: symbolic link to `/usr/lib/libcrypto.so.0.9.8'
In a word, 'NO!' That would break any and all 64bit software that relies on libcrypto.
Ken
Well, if this is a link inside the squeak dir then it would be fine. Question is why that symlink is needed at all though.
- Bert -
It's needed because Altitude needs access to libcrypto.
Chris