Github messages for voidlinux
 help / color / mirror / Atom feed
From: pullmoll <pullmoll@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] allegro5: fix build w/ musl-1.2.1 (time64)
Date: Sun, 06 Dec 2020 10:00:10 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26982@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 330 bytes --]

There is a new pull request by pullmoll against master on the void-packages repository

https://github.com/pullmoll/void-packages allegro5
https://github.com/void-linux/void-packages/pull/26982

allegro5: fix build w/ musl-1.2.1 (time64)


A patch file from https://github.com/void-linux/void-packages/pull/26982.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-allegro5-26982.patch --]
[-- Type: text/x-diff, Size: 1856 bytes --]

From e36a543cd530e887dd31c8f197a0854da8c0e805 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?J=C3=BCrgen=20Buchm=C3=BCller?= <pullmoll@t-online.de>
Date: Sun, 6 Dec 2020 09:58:56 +0100
Subject: [PATCH] allegro5: fix build w/ musl-1.2.1 (time64)

---
 srcpkgs/allegro5/patches/time64.patch | 49 +++++++++++++++++++++++++++
 1 file changed, 49 insertions(+)
 create mode 100644 srcpkgs/allegro5/patches/time64.patch

diff --git a/srcpkgs/allegro5/patches/time64.patch b/srcpkgs/allegro5/patches/time64.patch
new file mode 100644
index 00000000000..93b0491c613
--- /dev/null
+++ b/srcpkgs/allegro5/patches/time64.patch
@@ -0,0 +1,49 @@
+--- src/linux/lhaptic.c	2015-06-01 21:58:12.000000000 +0200
++++ src/linux/lhaptic.c	2020-12-06 09:50:58.475010832 +0100
+@@ -57,6 +57,7 @@
+ 
+ 
+ /* forward declarations */
++static void lhap_timerclear(struct input_event* event);
+ static bool lhap_init_haptic(void);
+ static void lhap_exit_haptic(void);
+ 
+@@ -162,6 +163,11 @@
+    { -1,          -1 }
+ };
+ 
++static void lhap_timerclear(struct input_event* event)
++{
++   event->input_event_sec = 0;
++   event->input_event_usec = 0;
++}
+ 
+ static bool lhap_init_haptic(void)
+ {
+@@ -622,7 +628,7 @@
+    struct input_event ie;
+ 
+    lhap->parent.gain = gain;
+-   timerclear(&ie.time);
++   lhap_timerclear(&ie);
+    ie.type = EV_FF;
+    ie.code = FF_GAIN;
+    ie.value = (__s32) ((double)0xFFFF * gain);
+@@ -639,7 +645,7 @@
+    struct input_event ie;
+ 
+    lhap->parent.autocenter = autocenter;
+-   timerclear(&ie.time);
++   lhap_timerclear(&ie);
+    ie.type = EV_FF;
+    ie.code = FF_AUTOCENTER;
+    ie.value = (__s32) ((double)0xFFFF * autocenter);
+@@ -765,7 +771,7 @@
+ 
+    fd = lhap->fd;
+ 
+-   timerclear(&play.time);
++   lhap_timerclear(&play);
+    play.type = EV_FF;
+    play.code = id->_handle;
+    loops = (loops < 0) ? 1 : loops;

             reply	other threads:[~2020-12-06  9:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-06  9:00 pullmoll [this message]
2020-12-06 10:38 ` [PR PATCH] [Merged]: " pullmoll
2020-12-08 15:55 ` hippi777
2020-12-08 16:03 ` pullmoll
2020-12-08 16:18 ` hippi777

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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26982@inbox.vuxu.org \
    --to=pullmoll@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /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;
as well as URLs for NNTP newsgroup(s).