Questions and Answers :
Unix/Linux :
On AMD64 - Unrecoverable error - process exited with code 127 (0x7f)
Message board moderation
Author | Message |
---|---|
![]() ![]() Send message Joined: 3 Apr 99 Posts: 65 Credit: 857,951 RAC: 0 ![]() |
Running Debian Unstable Pure AMD64 on an Althon64 3200. I suspect that I need to complile a seti client for AMD64, which I've flailed at for a couple of days. If so, a cry for help with that will be my next post : But, just to confirm - I've downloaded several different BOINC clients - the "standard" x86, optimized XP, optimized AMD64, etc. All start up OK, download a seti client (if necessary) and WUs. Then, the fun begins: [...] 2005-03-12 17:15:59 [SETI@home] Starting result 07ja05aa.26430.23249.348568.155_1 using setiathome version 4.02 2005-03-12 17:15:59 [SETI@home] Unrecoverable error for result 07ja05aa.26430.23249.348568.155_1 (process exited with code 127 (0x7f)) 2005-03-12 17:15:59 [SETI@home] Unrecoverable error for result 07ja05aa.26430.23249.348568.155_1 (process exited with code 127 (0x7f)) 2005-03-12 17:15:59 [SETI@home] Computation for result 07ja05aa.26430.23249.348568.155 finished [...] This is because the seti client can't work on AMD64, right? Thanks for any help. |
simplify / aki Send message Joined: 30 May 99 Posts: 61 Credit: 2,801,095 RAC: 0 ![]() |
"setiathome_4.02_i686-pc-linux-gnu: error while loading shared libraries: libz.so.1: cannot open shared object file: No such file or directory" i think the package you need is called amd64-libs http://rpmseek.com/rpm/amd64-libs_1.1_i386.html?hl=com&cs=libz.so.1:FN:0:0:0:0:1790826 ![]() |
![]() ![]() Send message Joined: 3 Apr 99 Posts: 65 Credit: 857,951 RAC: 0 ![]() |
> "setiathome_4.02_i686-pc-linux-gnu: error while loading shared libraries: > libz.so.1: cannot open shared object file: No such file or directory" > > i think the package you need is called amd64-libs > > > http://rpmseek.com/rpm/amd64-libs_1.1_i386.html?hl=com&cs=libz.so.1:FN:0:0:0:0:1790826 Hi again, Aki :) This is a Pure64 system (64-bit kernel and packages), so it doesn't have a amd64-libs - the libs (libstdc++, etc.) are all 64-bit. There is an IA32-libs package, which is installed. There are no nightly tarballs and the CVS sources don't come with a pre-built configure or Makefile script. The seem to need autoconf and automake, and I'm without a clue about that stuff... - Larry. |
simplify / aki Send message Joined: 30 May 99 Posts: 61 Credit: 2,801,095 RAC: 0 ![]() |
amd64-libs was wrong rpm -q -l zlib /usr/lib/libz.so.1 /usr/lib/libz.so.1.2.1.2 /usr/share/doc/zlib-1.2.1.2 /usr/share/doc/zlib-1.2.1.2/README the file libz.so.1 is included in the package zlib ![]() |
![]() ![]() Send message Joined: 3 Apr 99 Posts: 65 Credit: 857,951 RAC: 0 ![]() |
> amd64-libs was wrong > > > rpm -q -l zlib > > /usr/lib/libz.so.1 > /usr/lib/libz.so.1.2.1.2 > /usr/share/doc/zlib-1.2.1.2 > /usr/share/doc/zlib-1.2.1.2/README > > > the file libz.so.1 is included in the package zlib > You were close the first time, Aki! For Debian, the "native" library is in the package zlib1g-dev. The AMD64-from-i386 version is in the AMD64-libs-dev package. But I had the native version installed at the time. Thanks, though, Aki |
©2025 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.