dev-tqt/tqtinterface-9999 and trinity-base/tdelibs-9999 compilation failed #125
Closed
opened 4 years ago by Ghost
·
10 comments
Loading…
Reference in new issue
There is no content yet.
Delete Branch '%!s(<nil>)'
Deleting a branch is permanent. It CANNOT be undone. Continue?
dev-tqt/tqtinterface-9999 compilation fails, citing the missing GL/glu.h.
trinity-base/tdelibs-9999 compilation fails at this stage:
Basic information
Steps to reproduce
dev-tqt/tqtinterface-9999 compilation failedto dev-tqt/tqtinterface-9999 and trinity-base/tdelibs-9999 compilation failed 4 years agoThanks for the reporting. 👍
It seems the problem related to
glu
is some old one, existing since 2015 at least.The
tqtinterface
should not depend on any glu headers at all, iftqt
is build withoutopengl
support at all. There is some existing bug related to that: https://bugs.trinitydesktop.org/show_bug.cgi?id=2645Sure, adding
media-libs/glu
as dependency or bettervirtual/glu
isn't the right way to fix that. But because it seems to cause trouble, as you showed, I will add some dependency totqtinterface
as some workaround, in the hope this will be fixed in some time at TDE level.About tdelibs:
It seems you build tdelibs without
hwlib
USE. Right now, this is breaking the build. This needs to be investigated and fixed at TDE level. It seems some commit in 2019 caused that problem. I added some comment about that in the tdelibs ebuild, but it seems the better way would be to mask builds with-hwlib
until that is fixed, to not confuse users.Also I noticed that tdelibs also forcibly depends on udev/eudev, if you remove it and try to compile tdelibs, compilation also fails.
Interesting to know that. 😸
Seems that is needed for
hwlib
. So if tdelibs is build with that, it should maybe depend on udev/eudev. I will verify that and add some depend on that.Just for reference: Do you use Gentoo without udev/eudev and want to use TDE also without it?
I was going to do it, but tdelibs ruined all the plans.
Well, I ask because it seems Gentoo developers are doing their best to make that even more complicated, from what I have read. It seems the old
xf86-input-keyboard
andxf86-input-mouse
drivers, which are working without udev/eudev (until now) were removed. And evdev and so is depending on udev/eudev too. Furthermore the X developers want to remove Linux support of these older drivers.If the TDE stable ebuilds are more or less ready, you could try to build them. Because the stable branch is still working fine without FTBFS on tdelibs if build with
-hwlib
, from what I know. In the long run, I am sure R14.1.x will also build fine without hwlib again. It seems there are a lot of users not wanting that automount functionality and such things.Was your plan to use
mdev
than?About these "sticks in wheels" I am aware, ebuilds for old drivers I saved for this case, and in case of removing support for these drivers from xorg itself, I can make a patch.
Because the fact is that there are people who do not want to use udev/eudev and used static-dev, so in any case, a method for solving these "sticks in wheels" will be found.
And mdev will not help here, because it is incompatible with udev in terms of the API, so you want it or not, but new drivers will require udev anyway.
I am aware,
mdev
is no solution for udev/eudev dependencies, I just was interested, what was your initial plan here.I already read about some existing patches for the old drivers, or was it for evdev to not depend on udev on runtime, not sure, but I also read, they were rejected as "wontfix" at upstream level. It would be nice if people would find some way to offer some ebuilds/overlay for that purpose anyway.
Maybe you will be happy if the stable TDE ebuilds are working later.
I did some commits regarding your report. That should fix that things you pointed out.
dev-tqt/tqtinterface-9999 and dev-tqt/tqtinterface-14.0.6 are damaged, an superfluous bracket after "virtual/glu", as a result of this emerge gives an error.
Should be fixed now. Seems I missed that. 😸
EDIT: If you sync with rsync, please be patient a bit, because that isn't updated instantly.
FYI: The rsync source is usually updated once per hour.