From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: ludo@gnu.org (Ludovic =?iso-8859-1?Q?Court=E8s?=) Newsgroups: gmane.lisp.guile.devel Subject: Re: Build failure on master Date: Wed, 15 Jul 2009 00:05:34 +0200 Message-ID: <878wiq539t.fsf@gnu.org> References: <1247412093.30108.4.camel@localhost.localdomain> <87bpnpva3w.fsf@gnu.org> <874otf7min.fsf@arudy.ossau.uklinux.net> <87my777649.fsf@gnu.org> <87my775mpo.fsf@arudy.ossau.uklinux.net> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Trace: ger.gmane.org 1247609164 12607 80.91.229.12 (14 Jul 2009 22:06:04 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 14 Jul 2009 22:06:04 +0000 (UTC) To: guile-devel@gnu.org Original-X-From: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Wed Jul 15 00:05:57 2009 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.50) id 1MQq8K-0004S8-Fz for guile-devel@m.gmane.org; Wed, 15 Jul 2009 00:05:56 +0200 Original-Received: from localhost ([127.0.0.1]:46196 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MQq8J-0008MD-Jt for guile-devel@m.gmane.org; Tue, 14 Jul 2009 18:05:55 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MQq8H-0008M8-4d for guile-devel@gnu.org; Tue, 14 Jul 2009 18:05:53 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MQq8C-0008LH-Le for guile-devel@gnu.org; Tue, 14 Jul 2009 18:05:52 -0400 Original-Received: from [199.232.76.173] (port=45937 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MQq8C-0008LB-Ha for guile-devel@gnu.org; Tue, 14 Jul 2009 18:05:48 -0400 Original-Received: from main.gmane.org ([80.91.229.2]:37775 helo=ciao.gmane.org) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MQq8B-0001Yq-Ur for guile-devel@gnu.org; Tue, 14 Jul 2009 18:05:48 -0400 Original-Received: from list by ciao.gmane.org with local (Exim 4.43) id 1MQq8A-0003EX-Ct for guile-devel@gnu.org; Tue, 14 Jul 2009 22:05:46 +0000 Original-Received: from reverse-83.fdn.fr ([80.67.176.83]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 14 Jul 2009 22:05:46 +0000 Original-Received: from ludo by reverse-83.fdn.fr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 14 Jul 2009 22:05:46 +0000 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 28 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: reverse-83.fdn.fr X-URL: http://www.fdn.fr/~lcourtes/ X-Revolutionary-Date: 27 Messidor an 217 de la =?iso-8859-1?Q?R=E9volution?= X-PGP-Key-ID: 0xEA52ECF4 X-PGP-Key: http://www.fdn.fr/~lcourtes/ludovic.asc X-PGP-Fingerprint: 821D 815D 902A 7EAB 5CEE D120 7FBA 3D4F EB1F 5364 X-OS: x86_64-unknown-linux-gnu User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1.50 (gnu/linux) Cancel-Lock: sha1:Pd24q7WcAhrxewCCjqDWq7vECnE= X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6, seldom 2.4 (older, 4) 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:8873 Archived-At: Neil Jerram writes: > ludo@gnu.org (Ludovic Courtès) writes: [...] >> Eventually, maybe it could handle this gracefully. For instance, if >> said object file is from the cache, then it could just recompile and >> overwrite it with a new object file. > > Yes, this is what I'd (intuitively, but without detailed knowledge) > expect. I guess this could be achieved by setting up a dynwind/catch block in `primitive-load-path' when loading things from the cache. Something to look at once 1.9.1 is released. >> Then it could also try to interpret version numbers and determine >> whether that bytecode is really incompatible, or whether it can >> interpret it. > > Are there scenarios where that would be worthwhile? Maybe, e.g., when the `.go' version is known to be a strict subset of the current objcode version. Thanks, Ludo'.