From: Efraim Flashner <efraim@flashner.co.il>
To: Christopher Howard <christopher@librehacker.com>
Cc: 49372-done@debbugs.gnu.org
Subject: bug#49372: lagrange: illegal instruction
Date: Mon, 5 Jul 2021 09:11:12 +0300 [thread overview]
Message-ID: <YOKigGoY6SMRkeZp@3900XT> (raw)
In-Reply-To: <953d5059d736f1645b94332ae99b66ebbf5ee0bd.camel@librehacker.com>
[-- Attachment #1: Type: text/plain, Size: 2235 bytes --]
It sounds like everything's working now so I'm going to close the bug.
On Sun, Jul 04, 2021 at 05:40:41PM -0800, Christopher Howard wrote:
> I rebuilt from source and challenge now seems to be okay:
>
> christopher@nightshade ~/Repos/guix-working$ guix challenge lagrange
>
> 1 store items were analyzed:
> - 1 (100.0%) were identical
> - 0 (0.0%) differed
> - 0 (0.0%) were inconclusive
>
> --
> Christopher Howard
> my gemini capsule: gemini://gem.librehacker.com
> gemini browser: https://git.skyjake.fi/gemini/lagrange/releases
>
>
> On Sun, 2021-07-04 at 16:40 -0800, Christopher Howard wrote:
> > It seems to have downloaded as a substitute, and I was able to launch the program without getting an error.
> >
> > ```
> > christopher@nightshade ~/Repos/guix-working$ guix build lagrange
> > 11.0 MB will be downloaded:
> > /gnu/store/n45izfbldxjxdzfry2l4gn81lm18gmp0-lagrange-1.5.2
> > substituting /gnu/store/n45izfbldxjxdzfry2l4gn81lm18gmp0-lagrange-1.5.2...
> > downloading from https://ci.guix.gnu.org/nar/lzip/n45izfbldxjxdzfry2l4gn81lm18gmp0-lagrange-1.5.2 ...
> > lagrange-1.5.2 11.4MiB 4.4MiB/s 00:03
> > [##################] 100.0%
> >
> > The following graft will be made:
> > /gnu/store/9n5nyy324bp50yjc7pxv6a53zq7b9cza-lagrange-1.5.2.drv
> > applying 3 grafts for /gnu/store/9n5nyy324bp50yjc7pxv6a53zq7b9cza-lagrange-1.5.2.drv ...
> > grafting '/gnu/store/n45izfbldxjxdzfry2l4gn81lm18gmp0-lagrange-1.5.2' -> '/gnu/store/jj873xpq7h0rxm3rzc4b7rm6kzwnbby4-lagrange-1.5.2'...
> > successfully built /gnu/store/9n5nyy324bp50yjc7pxv6a53zq7b9cza-lagrange-1.5.2.drv
> > /gnu/store/jj873xpq7h0rxm3rzc4b7rm6kzwnbby4-lagrange-1.5.2
> > christopher@nightshade ~/Repos/guix-working$ /gnu/store/jj873xpq7h0rxm3rzc4b7rm6kzwnbby4-lagrange-1.5.2/bin/lagrange
> >
> > (launched without trouble)
> > ```
> >
>
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2021-07-05 6:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-04 3:32 bug#49372: lagrange: illegal instruction Christopher Howard
2021-07-04 12:18 ` Maxime Devos
2021-07-04 12:24 ` Maxime Devos
2021-07-04 19:09 ` Efraim Flashner
2021-07-04 23:14 ` Christopher Howard
2021-07-05 0:40 ` Christopher Howard
2021-07-05 1:40 ` Christopher Howard
2021-07-05 6:11 ` Efraim Flashner [this message]
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=YOKigGoY6SMRkeZp@3900XT \
--to=efraim@flashner.co.il \
--cc=49372-done@debbugs.gnu.org \
--cc=christopher@librehacker.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).