From: "Ludovic Courtès" <ludo@gnu.org>
To: Taylan Kammer <taylan.kammer@gmail.com>
Cc: 44000@debbugs.gnu.org
Subject: bug#44000: Guile-Git cross-compiled to i586-pc-gnu gets bytestructures wrong
Date: Mon, 16 Nov 2020 18:37:56 +0100 [thread overview]
Message-ID: <87blfxurrf.fsf@gnu.org> (raw)
In-Reply-To: <0d2d91d0-c335-ad6a-6249-8090837f16ff@gmail.com> (Taylan Kammer's message of "Mon, 16 Nov 2020 18:07:06 +0100")
Hi,
Taylan Kammer <taylan.kammer@gmail.com> skribis:
> The module (bytestructures guile numeric) ought to work, although it
> doesn't contain the binding 'arch32bit?'. Do you actually need that
> predicate, or was that just for demonstration? The "right" way to
> test whether the predicate works correctly would be to check whether
> e.g. intptr_t equals int32 or int64 as per 'eq?'.
Oh right, that makes sense. Apparently, all is good:
--8<---------------cut here---------------start------------->8---
scheme@(guix-user)> ,m (bytestructures guile numeric)
scheme@(bytestructures guile numeric)> intptr_t
$2 = #<bytestructure-descriptor 0x5600e60>
scheme@(bytestructures guile numeric)> (eq? intptr_t int32)
$3 = #t
scheme@(bytestructures guile numeric)> (eq? intptr_t int64)
$4 = #f
--8<---------------cut here---------------end--------------->8---
I’ll get more debugging info about the crash and will let you know if
Bytestructures is the culprit. ;-)
Ludo’.
next prev parent reply other threads:[~2020-11-16 17:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-14 22:25 bug#44000: Guile-Git cross-compiled to i586-pc-gnu gets bytestructures wrong Ludovic Courtès
2020-10-15 7:42 ` Ludovic Courtès
2020-10-15 8:09 ` Ludovic Courtès
2020-10-15 8:48 ` Mathieu Othacehe
2020-10-15 10:06 ` Jan Nieuwenhuizen
2020-10-16 15:58 ` Taylan Kammer
2020-10-17 17:44 ` Taylan Kammer
2020-10-19 8:23 ` Ludovic Courtès
2020-10-22 18:47 ` Taylan Kammer
2020-11-16 16:10 ` Ludovic Courtès
2020-11-16 17:07 ` Taylan Kammer
2020-11-16 17:37 ` Ludovic Courtès [this message]
2020-11-16 22:01 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87blfxurrf.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=44000@debbugs.gnu.org \
--cc=taylan.kammer@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 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.