From: Leo Famulari <leo@famulari.name>
To: 27811@debbugs.gnu.org
Subject: bug#27811: net-tools patch has no effect?
Date: Tue, 25 Jul 2017 00:12:25 -0400 [thread overview]
Message-ID: <20170725041225.GA31642@jasmine.lan> (raw)
In-Reply-To: <20170724220201.GA6136@jasmine.lan>
[-- Attachment #1: Type: text/plain, Size: 2264 bytes --]
The problem is that, in the patch phase, the patch file is referred to
as 'patch', but the package for the `patch` program is what that
variable resolves to:
(let ((patch.gz (assoc-ref inputs "patch")))
After fixing that by renaming the variable for the patch file to
something unique, the build fails like this:
------
gcc -D_GNU_SOURCE -O2 -Wall -g -I. -idirafter ./include/ -Ilib -c -o ipmaddr.o ipmaddr.c
ipmaddr.c: In function ‘multiaddr_modify’:
ipmaddr.c:351:25: warning: pointer targets in passing argument 2 of ‘parse_lla’ differ in signedness [-Wpointer-sign]
if (parse_lla(*argv, ifr.ifr_hwaddr.sa_data) < 0)
^
ipmaddr.c:78:12: note: expected ‘unsigned char *’ but argument is of type ‘char *’
static int parse_lla(char *str, unsigned char *addr)
^
gcc -Llib -o ipmaddr ipmaddr.o -lnet-tools
gcc -D_GNU_SOURCE -O2 -Wall -g -I. -idirafter ./include/ -Ilib -c -o mii-tool.o mii-tool.c
mii-tool.c: In function ‘main’:
mii-tool.c:432:29: error: too few arguments to function ‘parse_media’
case 'A': nway_advertise = parse_media(optarg); break;
^
mii-tool.c:163:12: note: declared here
static int parse_media(char *arg, unsigned *bmcr2)
^
mii-tool.c:433:26: error: too few arguments to function ‘parse_media’
case 'F': fixed_speed = parse_media(optarg); break;
^
mii-tool.c:163:12: note: declared here
static int parse_media(char *arg, unsigned *bmcr2)
^
mii-tool.c:456:2: warning: implicit declaration of function ‘version’ [-Wimplicit-function-declaration]
version();
^
mii-tool.c: At top level:
mii-tool.c:32:13: warning: ‘Version’ defined but not used [-Wunused-variable]
static char Version[] = "$Id: mii-tool.c,v 1.9 2006/09/27 20:59:18 ecki Exp $\n(Author: David Hinds based on Donald Becker's mii-diag)";
^
make: *** [<builtin>: mii-tool.o] Error 1
phase `build' failed after 7.5 seconds
------
This problem with the wrong number of arguments being passed to
parse_media() is introduced in the Debian patch, so we should check if
there is a better version of the patch or if fixes are being applied
upstream.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-07-25 4:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-24 22:02 bug#27811: net-tools patch has no effect? Leo Famulari
2017-07-25 4:12 ` Leo Famulari [this message]
2017-07-25 4:59 ` Leo Famulari
2017-07-25 8:27 ` Ludovic Courtès
2017-07-25 16:10 ` Leo Famulari
2017-07-25 17:52 ` Leo Famulari
2017-07-25 17:53 ` Leo Famulari
2017-07-25 18:03 ` Leo Famulari
2017-07-25 18:08 ` Leo Famulari
2017-07-25 21:30 ` Ludovic Courtès
2017-07-25 21:33 ` Ludovic Courtès
2017-07-26 16:08 ` Leo Famulari
2017-07-26 16:11 ` Leo Famulari
2017-07-26 21:04 ` Ludovic Courtès
2017-07-27 17:41 ` Leo Famulari
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=20170725041225.GA31642@jasmine.lan \
--to=leo@famulari.name \
--cc=27811@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).