We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Not a real bug (nothing broken) but the resolved linkage paths do look a bit funny. For example,
/home/user/openfoam/ThirdParty-common/platforms/linux64Clang150/ADIOS2-2.9.0/bin/bpls: /home/user/openfoam/ThirdParty-common/platforms/linux64Clang150/ADIOS2-2.9.0/bin/../lib64/libadios2_core.so.2: /home/user/openfoam/ThirdParty-common/platforms/linux64Clang150/ADIOS2-2.9.0/bin/../lib64/../lib6/libadios2_perfstubs.so: /home/user/openfoam/ThirdParty-common/platforms/linux64Clang150/ADIOS2-2.9.0/bin/../lib64/../lib64/libadios2_evpath.so: /home/user/openfoam/ThirdParty-common/platforms/linux64Clang150/ADIOS2-2.9.0/bin/../lib64/../lib64/libadios2_ffs.so.2: /home/user/openfoam/ThirdParty-common/platforms/linux64Clang150/ADIOS2-2.9.0/bin/../lib64/../lib64/libadios2_atl.so.2: /home/user/openfoam/ThirdParty-common/platforms/linux64Clang150/ADIOS2-2.9.0/bin/../lib64/../lib64/../lib64/libadios2_dill.so.2:
The bin/../lib64 part kind of makes sense, but the bin/../lib64/../lib64/../lib64/ starts to look a bit unreal.
bin/../lib64
bin/../lib64/../lib64/../lib64/
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Not a real bug (nothing broken) but the resolved linkage paths do look a bit funny. For example,
The
bin/../lib64
part kind of makes sense, but thebin/../lib64/../lib64/../lib64/
starts to look a bit unreal.The text was updated successfully, but these errors were encountered: