From: Mark H Weaver <mhw@netris.org>
To: Rob Browning <rlb@defaultvalue.org>
Cc: Helmut Grohne <helmut@subdivi.de>,
31777@debbugs.gnu.org, 900203@bugs.debian.org,
900203-forwarded@bugs.debian.org
Subject: bug#31777: guile-2.2 FTCBFS for mipsel: In procedure load-thunk-from-memory: No such file or directory
Date: Mon, 11 Jun 2018 11:20:12 -0400 [thread overview]
Message-ID: <87a7s173kj.fsf@netris.org> (raw)
In-Reply-To: <87vaaqpfmc.fsf@trouble.defaultvalue.org> (Rob Browning's message of "Sun, 10 Jun 2018 15:10:19 -0500")
Hi Rob,
Rob Browning <rlb@defaultvalue.org> writes:
> [If possible, please preserve the 900203-forwarded address in replies]
>
> We're currently unable to cross-build guile 2.2 on all of the debian
> release architectures, which is important given that through make, etc.,
> guile's now part of the core bootstrap set for new architectures.
>
> You can see additional information here
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900203
Thanks. I was able to reproduce the problem by running:
./meta/build-env guild compile --target=arm-unknown-linux-gnueabihf \
-Wunbound-variable -Wmacro-use-before-definition -Warity-mismatch \
-Wformat -L module --from=elisp \
-o module/language/elisp/ARM-boot.go \
module/language/elisp/boot.el
from my built git checkout of the stable-2.2 branch.
> ERROR: In procedure load-thunk-from-memory:
> In procedure load-thunk-from-memory: No such file or directory
> Makefile:2267: recipe for target 'language/elisp/boot.go' failed
The "No such file or directory" was bogus, caused by bad error handling
in 'load-thunk-from-memory', and fixed in the following commits:
https://git.savannah.gnu.org/cgit/guile.git/commit/?h=stable-2.2&id=deef64a739d868ed5fda4e55e387528c1b6c196b
https://git.savannah.gnu.org/cgit/guile.git/commit/?h=stable-2.2&id=9fbb36725634d05c3e46de7619e2f6019fbeb6fe
With those fixes, the error message becomes:
In procedure load-thunk-from-memory: ELF file does not have native word size
While cross-compiling our elisp compiler, there were attempts to load
object code built for the target machine into the Guile process running
on the build machine.
I just pushed commit bff75635e5ed08de63b02c661cf65f2e1b28c995 to the
stable-2.2 branch, which together with the earlier commit
988aa29238fca862c7e2cb55f15762a69b4c16ce allows me to successfully
cross-compile language/elisp/boot.el using the above command.
Would you like to try cherry-picking these commits and see if they fix
the problem for you?
https://git.savannah.gnu.org/cgit/guile.git/commit/?h=stable-2.2&id=988aa29238fca862c7e2cb55f15762a69b4c16ce
https://git.savannah.gnu.org/cgit/guile.git/commit/?h=stable-2.2&id=bff75635e5ed08de63b02c661cf65f2e1b28c995
Thanks,
Mark
next prev parent reply other threads:[~2018-06-11 15:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180527152301.GA23270@alf.mars>
[not found] ` <87sh6czwys.fsf@trouble.defaultvalue.org>
[not found] ` <20180528040202.GA19575@alf.mars>
[not found] ` <87h8mrzjjf.fsf@trouble.defaultvalue.org>
[not found] ` <20180528200534.GA30142@alf.mars>
2018-06-10 20:10 ` bug#31777: guile-2.2 FTCBFS for mipsel: In procedure load-thunk-from-memory: No such file or directory Rob Browning
2018-06-11 15:20 ` Mark H Weaver [this message]
2018-06-16 22:08 ` Rob Browning
2020-04-23 15:17 ` bug#31777: guile-2.2 FTCBFS for mipsel Vincent Legoll
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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a7s173kj.fsf@netris.org \
--to=mhw@netris.org \
--cc=31777@debbugs.gnu.org \
--cc=900203-forwarded@bugs.debian.org \
--cc=900203@bugs.debian.org \
--cc=helmut@subdivi.de \
--cc=rlb@defaultvalue.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.
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).