public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "James Le Cuirot" <chewi@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: games-engines/odamex/, games-engines/odamex/files/
Date: Sun,  2 Jul 2023 20:49:07 +0000 (UTC)	[thread overview]
Message-ID: <1688330930.0e81bdf479705e3665ad94da434891adc38b6787.chewi@gentoo> (raw)

commit:     0e81bdf479705e3665ad94da434891adc38b6787
Author:     James Le Cuirot <chewi <AT> gentoo <DOT> org>
AuthorDate: Sun Jul  2 20:34:09 2023 +0000
Commit:     James Le Cuirot <chewi <AT> gentoo <DOT> org>
CommitDate: Sun Jul  2 20:48:50 2023 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=0e81bdf4

games-engines/odamex: Fix USE=master with upstream patch

Closes: https://bugs.gentoo.org/907745
Signed-off-by: James Le Cuirot <chewi <AT> gentoo.org>

 .../odamex/files/odamex-10.3.0-master-fix.patch    | 31 ++++++++++++++++++++++
 games-engines/odamex/odamex-10.3.0-r1.ebuild       |  1 +
 2 files changed, 32 insertions(+)

diff --git a/games-engines/odamex/files/odamex-10.3.0-master-fix.patch b/games-engines/odamex/files/odamex-10.3.0-master-fix.patch
new file mode 100644
index 000000000000..1a20d8f6523c
--- /dev/null
+++ b/games-engines/odamex/files/odamex-10.3.0-master-fix.patch
@@ -0,0 +1,31 @@
+From 10beb4212625ee5e6d5b8a55e94d22d70d630217 Mon Sep 17 00:00:00 2001
+From: Jan200101 <sentrycraft123@gmail.com>
+Date: Wed, 19 Apr 2023 14:33:33 +0200
+Subject: [PATCH] include time.h on all platforms
+
+---
+ master/main.cpp | 3 +--
+ 1 file changed, 1 insertion(+), 2 deletions(-)
+
+diff --git a/master/main.cpp b/master/main.cpp
+index a69af8dd0..3226792a7 100644
+--- a/master/main.cpp
++++ b/master/main.cpp
+@@ -38,16 +38,15 @@
+ #include <string.h>
+ 
+ #include <stdint.h>
++#include <time.h>
+ 
+ #ifdef UNIX
+ #include <netinet/in.h>
+ #include <unistd.h>
+-#include <sys/time.h>
+ #endif
+ 
+ #ifdef _WIN32
+ #include <winsock.h>
+-#include <time.h>
+ #define usleep(n) Sleep(n/1000)
+ #endif
+ 

diff --git a/games-engines/odamex/odamex-10.3.0-r1.ebuild b/games-engines/odamex/odamex-10.3.0-r1.ebuild
index 594869339e54..0c99afc1d885 100644
--- a/games-engines/odamex/odamex-10.3.0-r1.ebuild
+++ b/games-engines/odamex/odamex-10.3.0-r1.ebuild
@@ -42,6 +42,7 @@ S="${WORKDIR}/${PN}-src-${PV}"
 
 PATCHES=(
 	"${FILESDIR}"/${PN}-10.3.0-unbundle-fltk.patch
+	"${FILESDIR}"/${P}-master-fix.patch
 )
 
 src_prepare() {


             reply	other threads:[~2023-07-02 20:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-02 20:49 James Le Cuirot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-03-19 23:04 [gentoo-commits] repo/gentoo:master commit in: games-engines/odamex/, games-engines/odamex/files/ James Le Cuirot
2023-12-18 21:57 James Le Cuirot
2023-05-14 14:26 James Le Cuirot
2022-03-20 13:32 James Le Cuirot
2022-03-04 22:49 James Le Cuirot
2021-05-29 14:54 James Le Cuirot
2020-08-25 21:57 James Le Cuirot
2020-08-25 21:57 James Le Cuirot
2020-04-08 22:46 James Le Cuirot
2019-09-07 14:33 James Le Cuirot
2019-09-07 14:33 James Le Cuirot
2018-10-14 18:35 Andreas Sturmlechner
2017-07-23 13:12 Michael Palimaka

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=1688330930.0e81bdf479705e3665ad94da434891adc38b6787.chewi@gentoo \
    --to=chewi@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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