Summary: | dev-qt/qtlocation-5.15.10 fails to compile with gcc | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Paul Gover <pmw.gover> |
Component: | Current packages | Assignee: | Qt Bug Alias <qt> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | floppym, manuavazquez |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: | https://bugs.gentoo.org/show_bug.cgi?id=829940 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | The full build log, tarred and feathered |
Description
Paul Gover
2023-07-18 09:05:02 UTC
Created attachment 865710 [details]
The full build log, tarred and feathered
I also couldn't get dev-qt/qtwebengine-5.15.10_p20230623 to compile with gcc, with AFAIR similar error messages, but I don't have the build log any more (drat), and am not keen to spend an hour recreating it! Comment on attachment 865710 [details]
The full build log, tarred and feathered
In the future, don't use tar to archive single files. Just compress the file directly using gzip instead.
Your emerge --info has CXX="clang++", but your build log shows "g++". I wonder if this problem is caused by building some Qt components with clang, and others with GCC. This is likely a duplicate of bug 829940. The comments on that bug allude to the issue being caused by building qtcore and qtpositioning with different compilers. Sorry for the mixup. FWIW, I could get qtlocation to compile with neither gcc (it threw the messages about invalid flags, all of which were for clang) not clang (treating out-of-range enums as errors not warnings.). You may be right about mixing gcc and clang - I converted to using clang almost everywhere (a very few packages won't), but have done it incrementally - i.e. I've not done "-emerge -e", just changed the necessary environment variables such as CFLAGS as per the wiki item, and let it all filter through. That said, all the Qt packages were being updated in the same emerge, so they are all clanged All that said, I found I didn't actually want qtlocation - it appeared via dependencies for marble, and it and qtpositioning are optional there, so I removed it/them, and lo an behold, no need for qtlocation! The exact same problem holds for me with everybody's favourite qtwebengine. That's got a patch that works for me - see: https://bugs.gentoo.org/903573 I can't do without qtwebengine, try as I might! I wish the package designers just used the system browser setting (firefox for me), rather than building it in. Or maybe qtwebengine should just be a wrapper to the system browser rather a browser in its own right. But who are we to complain?! Yeah, in particular, you need at least qtcore and other qt stuff built with the same compiler. I'just moved to clang and been hit by this bug: I cannot compile qtlocation with neither gcc nor clang, despite the fact that I pretty much recompile all qt with clang (using something along the lines of emerge --emptytree kate). Any hint? (In reply to manu from comment #8) Please create a new bug report with a build log and emerge --info. If it turns out to be the same issue we can always close it. |