From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Andy Wingo Newsgroups: gmane.lisp.guile.devel Subject: Re: Cross-compiling Guile 2.0 Date: Sat, 05 Mar 2011 22:41:57 +0100 Message-ID: References: <87hbbhbb99.fsf@ossau.uklinux.net> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: dough.gmane.org 1299361337 6389 80.91.229.12 (5 Mar 2011 21:42:17 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Sat, 5 Mar 2011 21:42:17 +0000 (UTC) Cc: guile-devel@gnu.org To: Neil Jerram Original-X-From: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Sat Mar 05 22:42:13 2011 Return-path: Envelope-to: guile-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1PvzEq-0003SZ-7k for guile-devel@m.gmane.org; Sat, 05 Mar 2011 22:42:12 +0100 Original-Received: from localhost ([127.0.0.1]:40819 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PvzEp-00020j-Ot for guile-devel@m.gmane.org; Sat, 05 Mar 2011 16:42:11 -0500 Original-Received: from [140.186.70.92] (port=47638 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PvzEf-0001zD-MQ for guile-devel@gnu.org; Sat, 05 Mar 2011 16:42:02 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PvzEd-0001ZN-Kz for guile-devel@gnu.org; Sat, 05 Mar 2011 16:42:01 -0500 Original-Received: from a-pb-sasl-sd.pobox.com ([64.74.157.62]:48562 helo=sasl.smtp.pobox.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PvzEd-0001ZJ-HR for guile-devel@gnu.org; Sat, 05 Mar 2011 16:41:59 -0500 Original-Received: from sasl.smtp.pobox.com (unknown [127.0.0.1]) by a-pb-sasl-sd.pobox.com (Postfix) with ESMTP id EE2B1473C; Sat, 5 Mar 2011 16:43:22 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=from:to:cc :subject:references:date:in-reply-to:message-id:mime-version :content-type; s=sasl; bh=TsMnUnQRiWlAhggx62x9MmqHNGg=; b=UUyqio ILzxoEIwnfNChStaNhs1bQnssQzxFnN1vB7mo/oqwXtLikIsiV2gAuwEZUz94guf juv0tzXO8fPuzPbEr3s4Vst9WuU7VjwbIw0+A1aLIR8yaPRHElyZLegdl/qJ3CVH 3Pja/05vesr22LRXhZgU46KmNdVOMe+s3yjWY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=from:to:cc :subject:references:date:in-reply-to:message-id:mime-version :content-type; q=dns; s=sasl; b=RuzHoKY6PbiylPVZaAZKunjRQHlJh7gh dXclIORQMS4PuAiDSPDu23AIsQWhnPGSojN2jnI1PQzMD6RAe6clMzcJ0LrR05pw rrYyLlK4Is6uqxQTvc69jRFfnFaRZ/D6HApwZZJ5NbpiYmIjF+tatWR2vrfM5WZS 7/olgnjUAC0= Original-Received: from a-pb-sasl-sd.pobox.com (unknown [127.0.0.1]) by a-pb-sasl-sd.pobox.com (Postfix) with ESMTP id D8A05473A; Sat, 5 Mar 2011 16:43:21 -0500 (EST) Original-Received: from unquote.localdomain (unknown [90.164.198.39]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by a-pb-sasl-sd.pobox.com (Postfix) with ESMTPSA id 31BB64739; Sat, 5 Mar 2011 16:43:19 -0500 (EST) In-Reply-To: <87hbbhbb99.fsf@ossau.uklinux.net> (Neil Jerram's message of "Sat, 05 Mar 2011 19:47:14 +0000") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux) X-Pobox-Relay-ID: 976CC000-4771-11E0-8AC4-AF401E47CF6F-02397024!a-pb-sasl-sd.pobox.com X-detected-operating-system: by eggs.gnu.org: Solaris 10 (beta) X-Received-From: 64.74.157.62 X-BeenThere: guile-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Developers list for Guile, the GNU extensibility library" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Errors-To: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.lisp.guile.devel:11783 Archived-At: On Sat 05 Mar 2011 20:47, Neil Jerram writes: > In principle, how should Guile 2.0 be cross-compiled? I'm thinking > mostly of the part of the build that compiles all the installed > modules. I have never cross-compiled anything, so I really don't know. Ideally we could make a cross-compiling Guile that executed on the host, but produced .go files for the target. Hummmmmm. Does that mean that for cross-compile builds, that we should not add the $builddir to the LOAD_COMPILED_PATH? Probably so, right? A cross-compiler probably doesn't autocompile either. So then the cross-compiler receives as its inputs the source files from a project, then produces .go files for the target, but does not load .go files from the target. Does that sound right to you? Andy -- http://wingolog.org/