From: Thiago Jung Bauermann via Guix-patches via <guix-patches@gnu.org>
To: Efraim Flashner <efraim@flashner.co.il>,
50081@debbugs.gnu.org, Mathieu Othacehe <othacehe@gnu.org>,
Maxime Devos <maximedevos@telenet.be>
Subject: [bug#50081] [PATCH core-updates-frozen v2] gnu: texlive-texmf: Disable LuaJIT engines on powerpc64*
Date: Thu, 19 Aug 2021 01:51:56 -0300 [thread overview]
Message-ID: <6444870.dUALR0brB4@popigai> (raw)
In-Reply-To: <YRzjWYMHcZnN0PX3@3900XT>
Em quarta-feira, 18 de agosto de 2021, às 07:39:21 -03, Efraim Flashner
escreveu:
> We now have a target-ppc64le? option which should be useful here.
Yes, that’s a nice code improvement. But unfortunately it’s mutually
exclusive with Maxime’s request to match against “powerpc64*”.
If people think the ‘target-ppc64le?’ alternative would be better than the
“powerpc64*” one, I can send a v3.
--
Thanks,
Thiago
next prev parent reply other threads:[~2021-08-19 4:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-16 19:46 [bug#50081] [PATCH] gnu: texlive-texmf: Disable LuaJIT engines on powerpc64le Thiago Jung Bauermann via Guix-patches via
2021-08-17 12:42 ` Mathieu Othacehe
2021-08-17 14:22 ` Thiago Jung Bauermann via Guix-patches via
2021-08-17 22:51 ` Maxime Devos
2021-08-18 2:53 ` Thiago Jung Bauermann via Guix-patches via
2021-08-18 2:55 ` [bug#50081] [PATCH core-updates-frozen v2] gnu: texlive-texmf: Disable LuaJIT engines on powerpc64* Thiago Jung Bauermann via Guix-patches via
2021-08-18 10:39 ` Efraim Flashner
2021-08-19 4:51 ` Thiago Jung Bauermann via Guix-patches via [this message]
2021-08-19 6:52 ` Efraim Flashner
2021-08-20 0:41 ` Thiago Jung Bauermann via Guix-patches via
2021-08-20 0:47 ` [bug#50081] [PATCH core-updates-frozen v3] gnu: texlive-texmf: Disable LuaJIT engines on powerpc64le Thiago Jung Bauermann via Guix-patches via
2021-08-22 11:19 ` bug#50081: " Efraim Flashner
2021-08-22 22:49 ` [bug#50081] " Thiago Jung Bauermann via Guix-patches via
2021-08-23 6:19 ` Efraim Flashner
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=6444870.dUALR0brB4@popigai \
--to=guix-patches@gnu.org \
--cc=50081@debbugs.gnu.org \
--cc=bauermann@kolabnow.com \
--cc=efraim@flashner.co.il \
--cc=maximedevos@telenet.be \
--cc=othacehe@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.