From: mhw@netris.org
To: Andreas Enge <andreas@enge.fr>
Cc: 18221@debbugs.gnu.org
Subject: bug#18221: Source of mit-scheme
Date: Wed, 13 Aug 2014 21:50:40 -0400 [thread overview]
Message-ID: <87a977n8jz.fsf@netris.org> (raw)
In-Reply-To: <20140813210422.GA1856@debian> (Andreas Enge's message of "Wed, 13 Aug 2014 23:04:22 +0200")
Andreas Enge <andreas@enge.fr> writes:
> On Wed, Aug 13, 2014 at 03:22:28PM -0400, Mark H Weaver wrote:
>> The problem here is that the "c" belongs in a different place in the
>> filename than where the "i386" or "x86-64" goes. The filenames are:
>> mit-scheme-9.2-i386.tar.gz
>> mit-scheme-9.2-x86-64.tar.gz
>> mit-scheme-c-9.2.tar.gz
>
> There is also mit-scheme-9.2.tar.gz; I thought this would need to be taken
> on other systems. But maybe this is the non-boot-strappable source code?
Yes, I believe mit-scheme-9.2.tar.gz can only be built if you already
have an executable copy of mit-scheme with which to build it.
> Second, do we not need to replace
> %current-system
> by
> (or (%current-target-system)(%current-system))
Hmm, this would be needed to support cross-compilation for typical
packages, but I suspect that the process is quite a bit different for
mit-scheme. I'd be very surprised if it was that simple.
For now, I suggest that we focus on getting mit-scheme working on mips
with native compilation. Later, if someone is motivated, they can look
into what's needed to cross-compile mit-scheme.
Thanks!
Mark
next prev parent reply other threads:[~2014-08-14 1:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-08 7:47 bug#18221: Source of mit-scheme Andreas Enge
2014-08-13 19:22 ` Mark H Weaver
2014-08-13 21:04 ` Andreas Enge
2014-08-14 1:50 ` mhw [this message]
2014-08-17 15:06 ` Ludovic Courtès
2014-09-27 18:09 ` Andreas Enge
2014-09-27 18:51 ` Ludovic Courtès
2014-09-27 19:42 ` Mark H Weaver
2014-09-27 21:05 ` Andreas Enge
2014-09-27 22:03 ` Ludovic Courtès
2019-02-19 22:50 ` bug#18221: Close Andreas Enge
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=87a977n8jz.fsf@netris.org \
--to=mhw@netris.org \
--cc=18221@debbugs.gnu.org \
--cc=andreas@enge.fr \
/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).