https://bugs.kde.org/show_bug.cgi?id=502434
--- Comment #2 from Allan <allan4...@gmail.com> --- Cool, I didn’t know about this kind of virtual environment—even /tmp behaves differently in it. Very nice! Thanks for pointing out this detail. I tried it, and it compiled the simple program by replacing the prefix with /usr inside Flatpak’s environment. Then I started investigating what could’ve been causing the compilation problems in my project, until I realized it was due to the inclusion of Boost, which had been installed via apt. Its headers reside in the same directory as the system's (/usr/include). So the problem isn’t Boost itself, but rather the system libraries and headers located there. I also noticed that Flatpak’s libc is version 2.40, while the system’s is 2.41. It would be nice if they matched, but now it seems I’ll be quite limited and may have to go back to using Qt the old way, without Flatpak—something I was trying to avoid to keep the system clean. Before closing it, is there something that I could try? Perhaps locking the same libc? -- You are receiving this mail because: You are watching all bug changes.
