From: Maxime Devos <maximedevos@telenet.be>
To: Zhu Zihao <all_but_last@163.com>
Cc: Oleg Pykhalov <go.wigust@gmail.com>, 51747@debbugs.gnu.org
Subject: [bug#51747] [PATCH]: gnu: nix: Update to 2.4.
Date: Wed, 12 Jan 2022 08:26:00 +0000 [thread overview]
Message-ID: <c113a0328f7b1e7d77ce3a4e7c349bac20f4a68d.camel@telenet.be> (raw)
In-Reply-To: <8635lto9z3.fsf@163.com>
[-- Attachment #1: Type: text/plain, Size: 982 bytes --]
Zhu Zihao schreef op wo 12-01-2022 om 12:21 [+0800]:
> [
> ...]
> Interesting, It looks that these blobs are for Windows system. I don't
> care about MS Windows, but blobs are tightly integrated in the source.
>
> The source reports that they're compiled from the source in contrib/MSR
> Driver/Kernel. They're PE COFF format, If we want to compile it ourself,
> we have to use mingw cross compiler. This increase the complexity of
> build script.
>
> AFAIK, nix use libcpuid only in linux context. My idea is replace these
> blobs with empty bytes. Maybe leave a note for who want mingw cross build.
Often (but not always, cf. rust), when software has files for specific
architectures or operating systems, they will only be compiled if they
match the architecture and operating system the software is compiled
for. As such, there's a good chance the build will succeed (at least
for Linux, for Hurd, ...) if they are simply deleted.
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-01-12 8:31 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-10 12:35 [bug#51747] [PATCH]: gnu: nix: Update to 2.4 Zhu Zihao
[not found] ` <handler.51747.B.16365478179399.ack@debbugs.gnu.org>
2021-11-10 13:53 ` [bug#51747] Acknowledgement ([PATCH]: gnu: nix: Update to 2.4. ) Zhu Zihao
2021-11-10 15:47 ` Zhu Zihao
2021-11-17 11:21 ` Zhu Zihao
2021-12-04 15:28 ` Zhu Zihao
2022-01-11 8:23 ` [bug#51747] [PATCH]: gnu: nix: Update to 2.4 Oleg Pykhalov
2022-01-11 9:46 ` Zhu Zihao
2022-01-11 17:19 ` Zhu Zihao
2022-01-11 19:04 ` Maxime Devos
2022-01-12 4:21 ` Zhu Zihao
2022-01-12 5:19 ` Oleg Pykhalov
2022-01-12 7:08 ` Zhu Zihao
2022-01-12 8:26 ` Maxime Devos [this message]
2022-01-13 4:54 ` Zhu Zihao
2022-01-13 7:54 ` Zhu Zihao
2022-01-14 13:06 ` Maxime Devos
2022-01-14 16:51 ` Zhu Zihao
2022-01-14 18:39 ` Maxime Devos
2022-01-15 1:58 ` Zhu Zihao
2022-01-15 5:47 ` Zhu Zihao
2022-01-15 10:52 ` Maxime Devos
2022-01-15 16:06 ` Zhu Zihao
2022-01-21 14:29 ` bug#51747: " Oleg Pykhalov
2022-01-23 11:02 ` [bug#51747] " Maxime Devos
2022-01-11 19:05 ` Maxime Devos
2022-01-14 9:31 ` Zhu Zihao
2022-01-14 12:56 ` Maxime Devos
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=c113a0328f7b1e7d77ce3a4e7c349bac20f4a68d.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=51747@debbugs.gnu.org \
--cc=all_but_last@163.com \
--cc=go.wigust@gmail.com \
/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).