-
Notifications
You must be signed in to change notification settings - Fork 64
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
libnsl.so.1 missing from AppImage v0.19-23756 #53
Comments
possible the copying is not working anymore after moving to github-actions. Best to look into the log files. |
@brianredbeard Is this also true for the latest FC appimage revision? https://github.com/FreeCAD/FreeCAD/releases/download/0.19_pre/FreeCAD_0.19-24212-macOS-x86_64-conda.dmg |
@luzpaz you linked the osx-bundle. I guess we are talking about the appimage here. |
sorry, i meant the appimage link |
I guess this is obsolete now. Closing |
After updating using zsync from v0.19-23578 to v0.19-23756, the FreeCAD appimage fails with the following error:
$ ./FreeCAD_0.19-23756-Linux-Conda_glibc2.12-x86_64.AppImage /tmp/.mount_FreeCAuZGeOF/usr/bin/freecad: error while loading shared libraries: libnsl.so.1: cannot open shared object file: No such file or directory
Indeed, it does seem that the library is missing from the bundle. After using
$ ./FreeCAD_0.19-23756-Linux-Conda_glibc2.12-x86_64.AppImage --appimage-mount
and changing into the directory specified onSTDOUT
(/tmp/.mount_FreeCAnPMqLM/
) I see the following:Related to this, I see that there are multiple identical copies of libnsl in older AppImages (in this example v0.19-23578):
We see that we have the same SHA256 hash with different paths and different inodes. This is different than the behavior of other libraries (e.g. libkrad, which uses a normative set of cascading symbolic links):
My assumption for this being that the
cp
command originally introduced in 49f8a39 and carried forward into the various build scripts is dereferencing the symbolic link created by the underlying packaging system used to put libnsl in place.The text was updated successfully, but these errors were encountered: