From mboxrd@z Thu Jan 1 00:00:00 1970 From: mhw@netris.org Subject: bug#18221: Source of mit-scheme Date: Wed, 13 Aug 2014 21:50:40 -0400 Message-ID: <87a977n8jz.fsf@netris.org> References: <20140808074757.GA13320@debian> <87wqacry8b.fsf@yeeloong.lan> <20140813210422.GA1856@debian> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:47835) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XHkC6-0006eq-0o for bug-guix@gnu.org; Wed, 13 Aug 2014 21:51:16 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XHkBy-0006TI-Dn for bug-guix@gnu.org; Wed, 13 Aug 2014 21:51:09 -0400 Received: from debbugs.gnu.org ([140.186.70.43]:35646) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XHkBy-0006TE-AG for bug-guix@gnu.org; Wed, 13 Aug 2014 21:51:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.80) (envelope-from ) id 1XHkBx-0001Ce-Nh for bug-guix@gnu.org; Wed, 13 Aug 2014 21:51:01 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <20140813210422.GA1856@debian> (Andreas Enge's message of "Wed, 13 Aug 2014 23:04:22 +0200") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org To: Andreas Enge Cc: 18221@debbugs.gnu.org Andreas Enge 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