Annoying path issue?

[scootermaster]

So, it's really simple. I have a file I'd like to execute in the

/mnt/hgfs/Dropbox/Research/4.3/vex-3.43/bin

directory. The file is vexcc (not the it matters)

When I execute "vexcc --help" in any directory I get the following:

vexcc: /mnt/hgfs/Dropbox/Research/4.3/vex-3.43/vexcc: Unexpected directory structure

Of course, if I explicitly state the directory, i.e.

/mnt/hgfs/Dropbox/Research/4.3/vex-3.43/bin/vexcc

it works just fine.

"echo $PATH" (this is bash, FC14) returns

/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/mnt/hgfs/Dropbox/Research/4.3/vex-3.43/bin

Edit: Typo!

So, you know, I'm not a complete idiot. It's in the path, as pest as I can tell.

Anyone have any idea what this unexpected directory structure crap means?

This compiler produces all sorts of output and temporary files that I need, and it would really be nice to be able to invoke it from someplace other than it's home vex-3.43/bin directory.

Thanks.

 

[Crusty]

Are you sure you've got the paths right?

In your path you have /bin on the end of the basedir and you claim the exe resides in there, but when you run the exe with the fullpath you are not including /bin.

 

[scootermaster]

Are you sure you've got the paths right?

In your path you have /bin on the end of the basedir and you claim the exe resides in there, but when you run the exe with the fullpath you are not including /bin.

Thanks for looking.

Yeah, that was a typo. When I type the full path, it works. With the bin.

I originally thought it might be because the file was originally called "cc", which is some alias to gcc or something in /usr/bin. But I op-ed it to "vexcc" and see the same behavior.

I guess I just solved it by making an alias between "vexcc" and /mnt/hgfs/Dropbox/Research/4.3/vex-3.43/bin/vexcc. But that seems, y'know, to be beside the whole point of a path, right?