nvptx-none-ar and nvptx-none-ranlib #4
Comments
tschwinge
added a commit
that referenced
this issue
Jan 7, 2021
tschwinge
added a commit
that referenced
this issue
Jul 24, 2023
In the (very likely, given the settings in which nvptx-tools are used) case
that via 'gcc_AC_PROG_LN_S', 'LN_S' is resolved to 'ln -s', 'make install' does
work as expected, but it fails in case that 'LN_S' is resolved to 'ln', (a):
ln /usr/bin/ar [PREFIX]/bin/nvptx-none-ar
ln: failed to create hard link '[PREFIX]/bin/nvptx-none-ar' => '/usr/bin/ar': Invalid cross-device link
..., since "forever".
In the 'ln' case, since #5 commit 2ec6ea2
"Use relative symlinks for [install]/nvptx-none/bin/{ar,as,ld,ranlib}", it
additionally fails, (b):
rel=$(perl -MFile::Spec -e 'print File::Spec->abs2rel(@argv)' [PREFIX]/bin [PREFIX]/nvptx-none/bin) && \
for p in ar as ld nm ranlib; do \
rm -f [PREFIX]/nvptx-none/bin/"$p" && \
ln "$rel"/nvptx-none-"$p" [PREFIX]/nvptx-none/bin/"$p"; \
done
ln: failed to access '../../bin/nvptx-none-ar': No such file or directory
Ideally, these two issues ought to be resolved properly: (a) via
<#4>
"nvptx-none-ar and nvptx-none-ranlib", and (b) via slightly changing the shell
code (first 'cd', then 'ln'). Until that's done, let's assume that 'ln -s'
does work (very likely, given the settings in which nvptx-tools are used).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
During installation,
nvptx-none-arandnvptx-none-ranlibare created as symlinks to thearandranlibbinaries found in$PATH. (The intention is to re-use those of the GNU/Linux host system.)This makes the installation tree non-relocatable to a different system. Maybe wrapper shell scripts should be used instead?
The text was updated successfully, but these errors were encountered: