Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Symlink to binary not supported but no error provided #4

Open
MehtaKnight01 opened this issue Jun 20, 2022 · 0 comments
Open

Symlink to binary not supported but no error provided #4

MehtaKnight01 opened this issue Jun 20, 2022 · 0 comments

Comments

@MehtaKnight01
Copy link

Running scasa from a symlink is not possible as Scasa expects to be able to access the scasa directory via the "which scasa" command (see SCASA_WRAP_V1.0.0.pl line 36), however, no error message is provided. It is my understanding that using "readlink -f" on the output of the "which scasa" command will return the appropriate directory even if the which scasa command returns the location of the symlink. See https://unix.stackexchange.com/questions/22128/how-to-get-full-path-of-original-file-of-a-soft-symbolic-link

This error is not obvious to the user; Scasa simply "finishes" running without generating an index or count matrix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant