From: Taylan Kammer <taylan.kammer@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 44000@debbugs.gnu.org
Subject: bug#44000: Guile-Git cross-compiled to i586-pc-gnu gets bytestructures wrong
Date: Thu, 22 Oct 2020 20:47:04 +0200 [thread overview]
Message-ID: <87ft66umhj.fsf@gmail.com> (raw)
In-Reply-To: <87blgy39q7.fsf@gnu.org> ("Ludovic Courtès"'s message of "Mon, 19 Oct 2020 10:23:28 +0200")
Ludovic Courtès <ludo@gnu.org> writes:
> Hi,
>
> Taylan Kammer <taylan.kammer@gmail.com> skribis:
>
>> Could you please test whether bytestructures 1.0.8 fixes the issue?
>
> Thanks for the prompt reply! I tested 1.0.8 and it does not fix the
> problem.
>
> I think the problem might be that the ‘cond-expand-provide’ call might
> affect a module that’s not the one tested in (eval '(cond-expand …) …).
>
> Does that make sense?
Yes, you're right. I've made another release (1.0.9), where I use
(environment '(guile) '(bytestructures guile numeric-data-model))
for the 'base-environment' binding in case we're running on Guile.
It now gives me correct results locally (woe on me for not having
properly tested the previous one) so I think it should definitely work
when cross-compiling too, since the 'eval' is sure to be executed at
run-time and not compile-time...
Fingers crossed, I hope I don't waste your time this time!
- Taylan
next prev parent reply other threads:[~2020-10-22 18:48 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 [this message]
2020-11-16 16:10 ` Ludovic Courtès
2020-11-16 17:07 ` Taylan Kammer
2020-11-16 17:37 ` Ludovic Courtès
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
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=87ft66umhj.fsf@gmail.com \
--to=taylan.kammer@gmail.com \
--cc=44000@debbugs.gnu.org \
--cc=ludo@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 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).