From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1] package/qt5base: fix input_event related compile failure
Date: Sun, 10 May 2020 22:43:30 +0200 [thread overview]
Message-ID: <871rnrr05p.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20200504214552.26570-1-ps.report@gmx.net> (Peter Seiderer's message of "Mon, 4 May 2020 23:45:52 +0200")
>>>>> "Peter" == Peter Seiderer <ps.report@gmx.net> writes:
> Fixes:
> - http://autobuild.buildroot.net/results/af76190876656252eb6f60220cdb1d627a03b7c3
> evdevkeyboard/qevdevkeyboardhandler.cpp: In member function ?void QEvdevKeyboardHandler::switchLed(int, bool)?:
> evdevkeyboard/qevdevkeyboardhandler.cpp:153:28: error: ?struct input_event? has no member named ?time?; did you mean ?type??
> ::gettimeofday(&led_ie.time, 0);
> ^~~~
> type
> evdevtouch/qevdevtouchhandler.cpp: In member function ?void QEvdevTouchScreenData::processInputEvent(input_event*)?:
> evdevtouch/qevdevtouchhandler.cpp:579:29: error: ?struct input_event? has no member named ?time?; did you mean ?type??
> m_timeStamp = data->time.tv_sec + data->time.tv_usec / 1000000.0;
> ^~~~
> type
> evdevtouch/qevdevtouchhandler.cpp:579:49: error: ?struct input_event? has no member named ?time?; did you mean ?type??
> m_timeStamp = data->time.tv_sec + data->time.tv_usec / 1000000.0;
> ^~~~
> type
A similar fix is presumably also needed for 2020.02.x? Care to send a
patch?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2020-05-10 20:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-04 21:45 [Buildroot] [PATCH v1] package/qt5base: fix input_event related compile failure Peter Seiderer
2020-05-05 18:11 ` Peter Seiderer
2020-05-09 21:15 ` Thomas Petazzoni
2020-05-09 21:56 ` Peter Seiderer
2020-05-10 20:43 ` Peter Korsgaard [this message]
2020-05-10 20:45 ` Peter Korsgaard
2020-05-11 20:26 ` Peter Seiderer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871rnrr05p.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox