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: more compilation failures: -DSCM_DEBUG_TYPING_STRICTNESS=2 Date: Wed, 18 Nov 2009 10:37:25 +0100 Message-ID: <87aayk2my2.fsf@gnu.org> References: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: ger.gmane.org 1258537105 11374 80.91.229.12 (18 Nov 2009 09:38:25 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 18 Nov 2009 09:38:25 +0000 (UTC) To: guile-devel@gnu.org Original-X-From: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Wed Nov 18 10:38:18 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 1NAgzR-0005FJ-J9 for guile-devel@m.gmane.org; Wed, 18 Nov 2009 10:38:17 +0100 Original-Received: from localhost ([127.0.0.1]:33972 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NAgzR-0000Kr-0Q for guile-devel@m.gmane.org; Wed, 18 Nov 2009 04:38:17 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NAgzL-0000Km-5T for guile-devel@gnu.org; Wed, 18 Nov 2009 04:38:11 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NAgzG-0000K3-Hk for guile-devel@gnu.org; Wed, 18 Nov 2009 04:38:10 -0500 Original-Received: from [199.232.76.173] (port=54299 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NAgzG-0000Jq-Bk for guile-devel@gnu.org; Wed, 18 Nov 2009 04:38:06 -0500 Original-Received: from lo.gmane.org ([80.91.229.12]:59952) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1NAgzF-00030f-WF for guile-devel@gnu.org; Wed, 18 Nov 2009 04:38:06 -0500 Original-Received: from list by lo.gmane.org with local (Exim 4.50) id 1NAgzC-00054w-Ud for guile-devel@gnu.org; Wed, 18 Nov 2009 10:38:02 +0100 Original-Received: from laptop-147-210-128-170.labri.fr ([147.210.128.170]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 18 Nov 2009 10:38:02 +0100 Original-Received: from ludo by laptop-147-210-128-170.labri.fr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 18 Nov 2009 10:38:02 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 21 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: laptop-147-210-128-170.labri.fr X-URL: http://www.fdn.fr/~lcourtes/ X-Revolutionary-Date: 28 Brumaire an 218 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 (gnu/linux) Cancel-Lock: sha1:wU+4+2KNB70VHu1BdUZ3ziEUh6o= X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 3) 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:9694 Archived-At: Hi Ken, I agree that we should strive to make Guile portable, especially since we are to stuff it into Emacs. >From time to time, I test it on some “exotic” hardware architectures of the GCC Compile Farm (MIPS, Alpha, PPC64, etc.), and it’s been working pretty well so far. I also got accounts on Tru64, AIX, and now Solaris and HP-UX, which I’m hoping to put to good use by the time we release 2.0. That said, I’m not too worried about the Cray pointer thing. IOW, it’s OK for me to live with potential Cray breakage until someone with access to such a machine (how many are there around the world?) can come up with a bug report or a fix. Now, if ‘SCM_DEBUG_TYPING_STRICTNESS’ can help us prevent breakage, that’s nice. I’ve never used it so far, and never felt the need to use it, but I’d be glad to follow your lead on this matter. :-) Thanks, Ludo’.