fix creation of symlink for libraries in tbb easyblock#2927
fix creation of symlink for libraries in tbb easyblock#2927akesandgren merged 4 commits intoeasybuilders:developfrom
tbb easyblock#2927Conversation
PR easybuilders#2539 introduced a suspicious `os.path.join(libpath)` which was likely intended to be `os.path.join(self.installdir, libpath)` but works due to a possible(!) `chdir` when TBB is installed via the system toolchain. Fix this by making `libpath` always absolute and simplify the code a bit.
|
Test report by @Flamefire Overview of tested easyconfigs (in order)
Build succeeded for 4 out of 4 (4 easyconfigs in total) From the logs: While previously it was: |
akesandgren
left a comment
There was a problem hiding this comment.
This does fix incorrect symlinks being generated for newer (20xx) versions, but the code for "if self.toolchain.is_system_toolchain():" both was and still is broken due to multiple layers of relative synlinking.
I see, we have
Now |
|
From installdir of tbb/4.4.x (based under /home/a/ake/easybuild-amd64_ubuntu2004_bdw/software): But since that last one is really |
|
@akesandgren I updated the easyblock to create the symlink with the resolved path. I expect that to change I can't test/debug this though as I can't find the 4.4 archive. |
|
Test report by @akesandgren Overview of tested easyconfigs (in order)
Build succeeded for 1 out of 1 (1 easyconfigs in total) |
|
Test report by @akesandgren Overview of tested easyconfigs (in order)
Build succeeded for 4 out of 4 (4 easyconfigs in total) |
|
Going in, thanks @Flamefire! |
2 similar comments
|
Going in, thanks @Flamefire! |
|
Going in, thanks @Flamefire! |
So I assume the symlinks are good there now? |
|
As far as I can tell at least. |
tbb easyblock
PR #2539 introduced a suspicious
os.path.join(libpath)which was likely intended to beos.path.join(self.installdir, libpath)but works due to a possible(!)chdirwhen TBB is installed via the system toolchain.Fix this by making
libpathalways absolute and simplify the code a bit.@mboisson Please take a look at this instead of ComputeCanada@f34b32b