From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1] package/qt5base: fix input_event related compile failure
Date: Sat, 9 May 2020 23:56:02 +0200 [thread overview]
Message-ID: <20200509235602.185dc4e3@gmx.net> (raw)
In-Reply-To: <20200509231534.25fccd75@windsurf.home>
Hello Thomas,
On Sat, 9 May 2020 23:15:34 +0200, Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:
> On Mon, 4 May 2020 23:45:52 +0200
> Peter Seiderer <ps.report@gmx.net> wrote:
>
> > 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
> >
> > Signed-off-by: Peter Seiderer <ps.report@gmx.net>
> > ---
> > ...fix-input_event-time-related-compile.patch | 56 +++++++++++++++++++
> > ...fix-input_event-time-related-compile.patch | 56 +++++++++++++++++++
> > 2 files changed, 112 insertions(+)
> > create mode 100644 package/qt5/qt5base/0005-evdevkeyboard-fix-input_event-time-related-compile.patch
> > create mode 100644 package/qt5/qt5base/0006-evdevtouch-fix-input_event-time-related-compile.patch
>
> I've applied to master, after adding the upstream details of each
> patch, as they have now been merged upstream (thanks for your work!).
>
> It would however be nice if you could remember to use "git format-patch
> -N" when generating patches and/or to run "make check-package" which
> would warn you about this :-)
Ups, thanks for fixing it....will try to work more accurate ;-)
Regards,
Peter
>
> Thanks!
>
> Thomas
next prev parent reply other threads:[~2020-05-09 21:56 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 [this message]
2020-05-10 20:43 ` Peter Korsgaard
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=20200509235602.185dc4e3@gmx.net \
--to=ps.report@gmx.net \
--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