On Sat, Jul 20, 2019 at 09:01:00AM -0400, Jean-Marc Pigeon via blfs-dev wrote:
> Hello,
>
>
> FYI
> Tried to compile qt-everywhere-src 5.13 and got trouble
>
> ;-------------------------------------------------------------------
> socketcanbackend.cpp: In member function ‘void
> SocketCanBackend::readSocket()’:
> socketcanbackend.cpp:697:41: error: ‘SIOCGSTAMP’ was not declared in this
> scope; did you mean ‘SIOCSARP’?
> 697 | if (Q_UNLIKELY(ioctl(canSocket, SIOCGSTAMP, &timeStamp) <
> 0)) {
> | ^~~~~~~~~~
> /home/jmp/rpmbuild/BUILD/qt-everywhere-src-5.13.0/qtbase/include/QtCore/../../src/corelib/global/qcompilerdetection.h:237:49:
> note: in definition of macro ‘Q_UNLIKELY’
> 237 | # define Q_UNLIKELY(expr) __builtin_expect(!!(expr), false)
> | ^~~~
> make: *** [Makefile:1217: .obj/socketcanbackend.o] Error 1
> ;-------------------------------------------------------------------
>
> this was pin-pointed to using kernel-headers 5.2.1 during build
> process.
>
> Solution is to add
> #include <linux/sockios.h>
> within
> qt-everywhere-src-5.13.0/qtserialbus/src/plugins/canbus/socketcan/socketcanbackend.cpp
>
> Hoping this help.
> (I guess the qt-5.13.0-upstream_fixes-1.patch, need
> to be slightly updated :) ).
>
Sounds as if this is more widespread :-(
https://lore.kernel.org/lkml/20190720174844.4b989d34@sf/T/#u
At a minimum, firefox, qemu, and something called linux-atm.
That was only posted a few minutes ago, will be interesting to see
what is advised so that applications can build against old and new
headers.
The link for linux-atm looks like a good fix (include inux/sockios.h
if SIOCGSTAMP is not defined), but I suggest waiting for comments
from our 'betters' because this almost looks like userspace breakage
;-)
--
One pill makes you larger, And one pill makes you small.
And the ones that mother gives you, Don't do anything at all.
Go ask Alice, When she's ten feet tall.
-- Jefferson Airplane, White Rabbit
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
