On 5/15/21 1:05 PM, Bald Eagle wrote:
> William F Pokorny <ano### [at] anonymousorg> wrote:
> 
>> Let's start the debugging with the commands above.
> 
> 
>> Bill P.
> 
> bald@Alienware ~/povray38/scenes/objects $ which povr
> /home/bald/bin/povr
> 
> bald@Alienware ~/povray38/scenes/objects $ echo $PATH
>
/home/bald/bin:/home/bald/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local
> /games:/snap/bin
> 
> bald@Alienware ~/povray38/scenes/objects $ /home/bald/bin/povr --version
> 
> bald@Alienware ~/povray38/scenes/objects $ ls -lt /home/bald/bin/povr
> lrwxrwxrwx 1 bald bald 50 May 14 15:37 /home/bald/bin/povr ->
> /home/povray/povray-3.8.0-x.povr_b0bcf6c0/bin/povr
> 
> 
Thanks.

OK, so it looks like you established a symbolic link from

/home/povray/povray-3.8.0-x.povr_b0bcf6c0/bin/povr

to:

/home/bald/bin/povr

There isnt' a bin directory shipped with
povray-3.8.0-x.povr_b0bcf6c0 so guessing you created it and the povr 
script/command within the directory?

---
I've spent some time trying to reproduce the null result and I can 
indeed do it if the file:

/home/povray/povray-3.8.0-x.povr_b0bcf6c0/bin/povr

is empty, but, the read and execute bits are set true. The command then 
just does nothing. So, a guess would be the file is empty - or just does 
nothing.

To run the in-place compiled code, that link target file should contain 
something like:

#!/bin/sh

#...

COMPILEDIR=/tmp/povray-3.8.0-x.povr_b0bcf6c0
unset POVINI
export POVINC=${COMPILEDIR}/include
${COMPILEDIR}/unix/povray $@

#...

---
Something else which could be tried if you think the contents of the 
file look OK, is to point your bin directory link at say the 'ls' 
command. My 'which ls' returns /bin/ls. So

ln -fs /bin/ls /home/bald/bin/povr

Then run again:

/home/bald/bin/povr --version

It should be it returns the ls command version. This would be a sanity 
test that nothing otherwise off with system sym links or something.

Bill P.

Post a reply to this message