1 |
On Sun, Apr 9, 2017 at 7:06 PM, <thelma@×××××××××××.com> wrote: |
2 |
> On 04/09/2017 09:55 AM, Alexander Kapshuk wrote: |
3 |
>> On Sun, Apr 9, 2017 at 6:49 PM, <thelma@×××××××××××.com> wrote: |
4 |
>>> I've installed: net-misc/nxclient-3.5.0.7 on x86 and it compiled without errors, but when I try to run it I get an error: |
5 |
>>> |
6 |
>>> nxclient |
7 |
>>> /usr/bin/nxclient: line 8: /usr/NX/bin/nxclient: cannot execute binary file: Exec format error |
8 |
>>> /usr/bin/nxclient: line 8: /usr/NX/bin/nxclient: Success |
9 |
>>> |
10 |
>>> In a remote location all my boxes are Gentoo except one Win10 (Home Edition). |
11 |
>>> I have a hard time connecting to it. |
12 |
>>> X2Go has only client for Win10 but in order for x2go to connect to Win10, it would have to run X2Go-server isn't it? |
13 |
>>> |
14 |
>>> Win10 has Remote Desktop for connecting to other computers, but you can't remote desktop to Windows 10 Home itself. That requires Windows 10 Pro. |
15 |
>>> |
16 |
>>> What are my alternatives? |
17 |
>>> |
18 |
>>> -- |
19 |
>>> Thelma |
20 |
>>> |
21 |
>> |
22 |
>> What's the output of 'readelf -h /path/to/nxclient'? |
23 |
>> |
24 |
>> |
25 |
> readelf -h /usr/NX/bin/nxclient |
26 |
> ELF Header: |
27 |
> Magic: 7f 45 4c 46 02 01 01 00 00 00 00 00 00 00 00 00 |
28 |
> Class: ELF64 |
29 |
> Data: 2's complement, little endian |
30 |
> Version: 1 (current) |
31 |
> OS/ABI: UNIX - System V |
32 |
> ABI Version: 0 |
33 |
> Type: EXEC (Executable file) |
34 |
> Machine: Advanced Micro Devices X86-64 |
35 |
> Version: 0x1 |
36 |
> Entry point address: 0x4207e0 |
37 |
> Start of program headers: 64 (bytes into file) |
38 |
> Start of section headers: 6314232 (bytes into file) |
39 |
> Flags: 0x0 |
40 |
> Size of this header: 64 (bytes) |
41 |
> Size of program headers: 56 (bytes) |
42 |
> Number of program headers: 8 |
43 |
> Size of section headers: 64 (bytes) |
44 |
> Number of section headers: 29 |
45 |
> Section header string table index: 28 |
46 |
> |
47 |
> -- |
48 |
> Thelma |
49 |
> |
50 |
|
51 |
OK. It's an x86-64 binary. That explains the error message you got |
52 |
when attempting to run it on your x86 machine. |
53 |
How did that happen, I wonder? |
54 |
|
55 |
Just to be 100% sure, can you please supply the output of the commands below? |
56 |
uname -m |
57 |
gcc -v 2>&1 | grep ^Target |
58 |
emerge --info |