The current ebuild for x11-misc/xscreensaver-6.05-r1 has this line: gtk? ( >=x11-libs/gtk+-2.22.0:3 ) I believe the :3 in there is intended to be :2 as this pulls in gtk+-3 even when gtk+-2 is installed. Thanks!
Created attachment 848056 [details] Build log without gtk+-3
This one just got a bit more complicated. When I made that correction to the ebuild it corrected the dependency part of this, but the compile failed at the end of the configure phase without gtk+3. I should note that this specific case is on an x86 system. I've attached the build.log. It doesn't appear to be too clear as to exactly what failed.
I should also note that I get the same configure failure if I try to compile without the gtk USE enabled at all.
So this one gets much more complex than I thought, and there may in fact be no real issue here: Even according to the upstream changelog, GTK 3 actually IS required for 6.05 assuming you use GTK at all. As it turned out, the failure in the config stage that I was getting, which happened even with the gtk USE flag disabled, was being caused by something totally unrelated: I had an old /etc/pam.d directory even though PAM wasn't installed, and the configure script uses that directory to assume that PAM is available, but not being used for xscreensaver which caused the config failure. So again, I don't think there's any issue here, as the only options are to use GTK 3 or no GTK at all...the latter being what I'm now using.
Yes, this really gets incredibly complicated. So, with 6.05 upstream switched from gtk2 to gtk3 finally. What upstream did not do is update the version check for gtk in their configure scripts. So, the version that we have to have at least is 2.22.0, but it must be gtk3. In reality this is nonsense, there is no gtk3 with version 2.22.0. But I did not want to pick an arbitrary version number, as this would confuse even more. So I kept the version that upstream is checking for and used to slot number to make sure it is gtk3. (In reply to Tom Dexter from comment #3) > I should also note that I get the same configure failure if I try to compile > without the gtk USE enabled at all. This should not happen. Even if this is caused by something unrelated it should not report a wrong error message then. From version 6.06 on I wanted to drop the option to build without gtk entirely since upstream dropped it as well. So I think there is not much sense in putting in the energy to fix that.
