From: Christopher Howard <christopher@librehacker.com>
To: 41033@debbugs.gnu.org
Subject: [bug#41033] [PATCH] gnu: libusb-0.1: fix build failure on newer gcc
Date: Sat, 02 May 2020 14:47:56 -0800 [thread overview]
Message-ID: <1a3c1bf5091742ae78a5946c92a622206dcdf596.camel@librehacker.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 371 bytes --]
I need libusb-0.1 to build some older software, but libusb-0.1 build
fails due to a warning from the current GCC version. (Evidently libusb-
0.1 is set to die on any warning.) The attached patch silences the
warning.
--
Christopher Howard
p: +1 (907) 374-0257
w: https://librehacker.com
social: https://gnusocial.club/librehacker
gpg: ADDEAADE5D607C8D (keys.gnupg.net)
[-- Attachment #2: 0001-gnu-libusb-0.1-fix-build-failure-on-newer-gcc.patch --]
[-- Type: text/x-patch, Size: 1383 bytes --]
From 351bb7004f9bbe8d50bbc7a2e2a1cb3900551e27 Mon Sep 17 00:00:00 2001
From: Christopher Howard <christopher@librehacker.com>
Date: Sat, 2 May 2020 14:41:00 -0800
Subject: [PATCH] gnu: libusb-0.1: fix build failure on newer gcc
Package build fails on truncation warning from current gcc. Silences
this warning.
---
gnu/packages/libusb.scm | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/gnu/packages/libusb.scm b/gnu/packages/libusb.scm
index 01c138cb4e..3bb2dcd186 100644
--- a/gnu/packages/libusb.scm
+++ b/gnu/packages/libusb.scm
@@ -8,6 +8,7 @@
;;; Copyright © 2017 Jonathan Brielmaier <jonathan.brielmaier@web.de>
;;; Copyright © 2018 Tobias Geerinckx-Rice <me@tobias.gr>
;;; Copyright © 2018 Vagrant Cascadian <vagrant@debian.org>
+;;; Copyright © 2020 Christopher Howard <christopher@librehacker.com>
;;;
;;; This file is part of GNU Guix.
;;;
@@ -113,7 +114,8 @@ version of libusb to run with newer libusb.")
(sha256
(base32
"0i4bacxkyr7xyqxbmb00ypkrv4swkgm0mghbzjsnw6blvvczgxip"))
- (patches (search-patches "libusb-0.1-disable-tests.patch"))))))
+ (patches (search-patches "libusb-0.1-disable-tests.patch"))))
+ (arguments `(#:configure-flags (list "CFLAGS=-Wno-format-truncation")))))
(define-public libusb4java
;; There is no public release so we take the latest version from git.
--
2.26.2
next reply other threads:[~2020-05-02 22:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-02 22:47 Christopher Howard [this message]
2020-05-03 10:58 ` [bug#41033] [PATCH] gnu: libusb-0.1: fix build failure on newer gcc Jakub Kądziołka
2020-05-03 16:13 ` Christopher Howard
2020-05-03 20:56 ` bug#41033: " Jakub Kądziołka
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1a3c1bf5091742ae78a5946c92a622206dcdf596.camel@librehacker.com \
--to=christopher@librehacker.com \
--cc=41033@debbugs.gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).