From: Stefan <stefan-guix@vodafonemail.de>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 45716@debbugs.gnu.org
Subject: bug#45716: Bug in ‘network-interface-names’ when building guix for aarch64 on x86_64.
Date: Fri, 8 Jan 2021 14:33:24 +0100 [thread overview]
Message-ID: <18A145C5-A200-4EEC-A559-5E3642521A3F@vodafonemail.de> (raw)
In-Reply-To: <20210108040445.1444c372@scratchpost.org>
Hi Danny and Ludo’!
> Can you try printing (@@ (guix build syscalls) ifreq-struct-size) directly?
I did that, it's printing 40 in both cases. That’s the value which is ending up in stride.
> Is it qemu-user or qemu-system?
~$ /usr/local/bin/qemu-system-x86_64 --version
QEMU emulator version 2.12.1 (-dirty)
Copyright (c) 2003-2017 Fabrice Bellard and the QEMU Project developers
> (Note: Empirically, on armhf, that struct is 32 Bytes big in C.
> And indeed the Linux kernel contains a compat struct ifreq32 in fs/compat_ioctl.c)
Bye
Stefan
next prev parent reply other threads:[~2021-01-08 13:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-07 15:37 bug#45716: Bug in ‘network-interface-names’ when building guix for aarch64 on x86_64 Stefan
2021-01-07 22:17 ` Stefan
2021-01-08 3:04 ` Danny Milosavljevic
2021-01-08 13:33 ` Stefan [this message]
2021-01-08 16:47 ` Stefan
2021-01-08 23:28 ` Stefan
2021-01-09 18:01 ` bug#45716: gnu: qemu: Fix ioclt(…, SIOCGIFCONF, …) for emulated 64 bit architectures Stefan
2021-01-11 13:28 ` Ludovic Courtès
2021-01-11 20:32 ` bug#45716: [PATCH 1/1] " Stefan
2021-01-14 13:39 ` Ludovic Courtès
2021-01-23 15:27 ` bug#45716: Bug in ‘network-interface-names’ when building guix for aarch64 on x86_64 Stefan
2021-01-23 20:13 ` Leo Famulari
2021-02-01 20:58 ` Ludovic Courtès
2021-02-02 8:09 ` Mathieu Othacehe
2021-02-06 12:59 ` Stefan
2021-02-07 18:15 ` Mathieu Othacehe
2021-02-08 7:44 ` Stefan
2021-01-11 13:30 ` Ludovic Courtès
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=18A145C5-A200-4EEC-A559-5E3642521A3F@vodafonemail.de \
--to=stefan-guix@vodafonemail.de \
--cc=45716@debbugs.gnu.org \
--cc=dannym@scratchpost.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).