Am Wed, Mar 01, 2023 at 09:14:27AM +0100 schrieb Alexander Asteroth: > guix packages but simply made them compile (after some manual changes to > the code) in my current environment. If I now run a `guix package -u` > the libraries (from qtbase) get upgraded from 5.15.5 to 6.3.1 and the > program fails to run.
Then I suppose that your Qt5 libraries disappear, so that the programs will not find them; and the newly installed Qt6 libraries will not be of help (they have a different name and are thus considered, well, different). To check, you can do "ldd name-of-my-executable", which shows you which libraries needed by your binary are found or not. So the solution is to not do a "guix package -u", or to do a "guix package --do-not-upgrade qtbase qtxxx qtyyy ... -u" (with a potentially long list of Qt packages in the middle). It might be easier then to create a separate profile with a manifest only for your Qt5 development, which you would then avoid to update. It is something I have not done myself yet, so I will have to refer you to the documentation. Andreas
