Re: Solved package dependencies problem in camitk
Emmanuel Promayon <[email protected]>
| Newsgroups | gmane.linux.debian.devel.medical |
|---|---|
| Organization | TIMC - Polytech |
| Message-ID | <[email protected]> |
Hello to all, I forgot to ask: should I first file a bug to explain the problem and then reference it as closed in d/changelog? Thanks in advance for your help (and understanding of a noob maintainer!) Emmanuel On 15/03/2025 15:17, Emmanuel Promayon wrote: > Dear all, > > We detected an issue with the current camitk package (this issue might > have been present since quite a while in fact but went unnoticed). > After installing camitk-config, on a fresh sid, running camitk-config > displays the following error: > > $ camitk-config > camitk-config: error while loading shared libraries: libjawt.so: > cannot open shared object file: No such file or directory > > camitk-config is indeed linked to two java libraries: > $ ldd /usr/bin/camitk-config | grep "not found" > libjawt.so => not found > libjvm.so => not found > > For information: > $ ldd -r /usr/bin/camitk-config | wc -l > 288 > > This is due to the CMake configuration in camitk version 5.2.0 that > links every camitk binary and library to all the VTK provided > libraries indistinctly if they are used or required. > This includes the VTK libraries that require Java, which are not used > in camitk. > > We worked on this, and with the committed patches on salsa everything > seems to work well now: camitk-config for instance is clear of java: > $ ldd /usr/bin/camitk-config | grep "not found" > $ ldd -r /usr/bin/camitk-config | wc -l > 131 > (notice the reduced number of linked shared objects). > > I also took the opportunity to fix two dh_missing warnings, patch > format warnings and remove xml output from doxygen generation that > seems to generate reproducibility issues. > All is on salsa. > > I did not push the tag to salsa this time, as I noticed this required > some extra work for Etienne last time! > > Let me know if that seems ok to upload. > > Best regards, and as always thank you again for your help! > Emmanuel >