Well, that was just it. I installed sixpack and this proceeded OK, with the
executable being installed in /usr/local/bin. This is in my path. I then
tried running it but I kept getting "no such file or directory". I then did
a "which bib" (the sixpack app) and it was correctly identified as being in
/usr/local/bin. I checked it's perms and they were correct. I changed to
the /usr/local/bin directory and tried to run it from there, "./bib" and this
gave the same message about no such file... I also checked to make sure the
file was the correct size and it was.
The file was in /usr/local/bin, it was executable, it had correct perms,
/usr/local/bin is in my path, and the file was not found. Finally, I tried
reinstalling it and, for whatever reason (fortunately) it worked this time
round.
This has happened with a few other non-rpms too. I do not recall having this
happen with any rpms but I may be mistaken. The other thing is, some of the
tarballs I installed were the exact, unchanged tarballs that installed and
worked perfectly under 7.2 (which had mostly been upgraded to 8.0, by the
way).
On Saturday 26 May 2001 14:19, Civileme wrote:
> On Friday 25 May 2001 05:11, Praedor Tempus wrote:
> > I have run into this several times myself. With me, the latest such
> > episode occurred with sixpack, a bibliography application for lyx. I
> > installed it, which went fine. I then try to run it and get the same
> > message you do. I then do a "which <executable>" and it properly
> > identifies the executable in the proper place.
[...]
>
> If which works then you can always use
> $(which program) to execute program.
>
> When those two don't match up, it is usually a PATH problem. You really
> need a blank path at the front of the stream of paths.
>
> Civileme
--
Against stupidity, the gods themselves contend in vain.
