On 22 Jun 2013, at 20:24, Robert Wolfe wrote:
> On 06/22/2013 09:38 AM, Jonas Maebe wrote:
>> And
>> file `which fpc`
>
> [robert@shell ~]$ file 'which fpc'
> which fpc: cannot open `which fpc' (No such file or directory)
FWIW, it should have been
file `which fpc`
not
file 'which fpc'
When I redid the command another way, I got this:
[robert@shell ~]$ file /usr/bin/fpc
/usr/bin/fpc: ELF 64-bit LSB executable, x86-64, version 1 (SYSV),
statically linked, for GNU/Linux 2.4.0, stripped
Okay, smack me hard in the head now...
[robert@shell ~]$ uname -a
Linux shell.rivernet.us 2
[robert@shell ~]$ file 'which fpc'
which fpc: cannot open `which fpc' (No such file or directory)
On 06/22/2013 09:38 AM, Jonas Maebe wrote:
On 22 Jun 2013, at 16:33, Robert Wolfe wrote:
On 06/22/2013 08:50 AM, Jonas Maebe wrote:
On 22 Jun 2013, at 15:46, Robert Wolfe wrote:
[robert@shell
On 22 Jun 2013, at 16:33, Robert Wolfe wrote:
> On 06/22/2013 08:50 AM, Jonas Maebe wrote:
>> On 22 Jun 2013, at 15:46, Robert Wolfe wrote:
>>
>>> [robert@shell bin]$ fpc
>>> bash: /usr/bin/fpc: cannot execute binary file
>>> [robert@shell bin]$ fp
>>> bash: /usr/bin/fp: cannot execute binary fi
On 06/22/2013 08:50 AM, Jonas Maebe wrote:
On 22 Jun 2013, at 15:46, Robert Wolfe wrote:
Hi all! Just installed this and am getting the following message whenever I go
to try to run any of the binaries that are included in the package (fp, ppcx64,
etc):
[robert@shell bin]$ fpc
bash: /usr/bi
On 22 Jun 2013, at 15:46, Robert Wolfe wrote:
> Hi all! Just installed this and am getting the following message whenever I
> go to try to run any of the binaries that are included in the package (fp,
> ppcx64, etc):
>
> [robert@shell bin]$ fpc
> bash: /usr/bin/fpc: cannot execute binary file
