From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Han-Wen Nienhuys Newsgroups: gmane.lisp.guile.devel Subject: ia64 problem Date: Mon, 25 Aug 2003 12:55:29 +0200 Sender: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Message-ID: <16201.60193.195326.156184@localhost.localdomain> Reply-To: hanwen@cs.uu.nl NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1061821799 21569 80.91.224.253 (25 Aug 2003 14:29:59 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 25 Aug 2003 14:29:59 +0000 (UTC) Cc: reuter@ipd.uka.de Original-X-From: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Mon Aug 25 16:29:55 2003 Return-path: Original-Received: from monty-python.gnu.org ([199.232.76.173]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 19rILz-0005ry-00 for ; Mon, 25 Aug 2003 16:29:55 +0200 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.20) id 19rIJi-00043F-TJ for guile-devel@m.gmane.org; Mon, 25 Aug 2003 10:27:34 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20) id 19rIJD-00042o-9v for guile-devel@gnu.org; Mon, 25 Aug 2003 10:27:03 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20) id 19rIIh-0003tN-3w for guile-devel@gnu.org; Mon, 25 Aug 2003 10:27:02 -0400 Original-Received: from [199.232.41.8] (helo=mx20.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.20) id 19rIFN-0002qc-1y for guile-devel@gnu.org; Mon, 25 Aug 2003 10:23:05 -0400 Original-Received: from [194.109.127.138] (helo=smtpzilla2.xs4all.nl) by mx20.gnu.org with esmtp (Exim 4.20) id 19rIE1-0003r3-6e for guile-devel@gnu.org; Mon, 25 Aug 2003 10:21:41 -0400 Original-Received: from localhost.localdomain.xs4all.nl (byrd.xs4all.nl [213.84.26.127]) by smtpzilla2.xs4all.nl (8.12.9/8.12.9) with ESMTP id h7PAtTTF046311; Mon, 25 Aug 2003 12:55:30 +0200 (CEST) Original-To: guile-devel@gnu.org X-Mailer: VM 7.14 under Emacs 21.2.1 X-BeenThere: guile-devel@gnu.org X-Mailman-Version: 2.1.2 Precedence: list List-Id: Developers list for Guile, the GNU extensibility library List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Xref: main.gmane.org gmane.lisp.guile.devel:2705 X-Report-Spam: http://spam.gmane.org/gmane.lisp.guile.devel:2705 I received the following report on using GUILE on ia64. Juergen is running: The ia64 installation is currently based on redhat server 2.1. I was just told that this uses packages comparable to those of the redhat 7.x series. So, it really may be the same problem. Thinking more about it, mabe it's a gcc or libc bug. gcc version is 2.96; libc is version 2.2.4, Compiled by GNU CC version 2.96 20000731 (Red Hat Linux 7.2 2.96-116.7.2). Compiled on a Linux 2.4.9-9 system on 2003-04-09. Date: Mon, 25 Aug 2003 02:25:41 +0200 (CEST) From: Juergen Reuter To: lilypond-devel@gnu.org Cc: Juergen Reuter Subject: lily on ia64 Hi, still trying to compile and run lily on ia64, I have to report some problems/bugs that we probably should try to fix. Problem 1: ========== First of all, compiling stops quite early with the following message: In file included from /usr/include/signal.h:324, from /usr/include/sys/ucontext.h:23, from /export/home/reuter/usr/include/libguile/continuations.h:49, from /export/home/reuter/usr/include/libguile.h:63, from out/config.h:79, from include/libc-extension.hh:16, from string.cc:22: /usr/include/ucontext.h:32: `ucontext_t' was not declared in this scope /usr/include/ucontext.h:32: `__ucp' was not declared in this scope /usr/include/ucontext.h:32: warning: `getcontext' initialized and declared `extern' /usr/include/ucontext.h:35: parse error before `*' /usr/include/ucontext.h:39: `ucontext_t' was not declared in this scope /usr/include/ucontext.h:39: parse error before `,' /usr/include/ucontext.h:48: `ucontext_t' was not declared in this scope /usr/include/ucontext.h:48: `__ucp' was not declared in this scope /usr/include/ucontext.h:48: `__func' was not declared in this scope /usr/include/ucontext.h:48: parse error before `)' /usr/include/ucontext.h:48: warning: `makecontext' initialized and declared `extern' /usr/include/ucontext.h:48: variable or field `makecontext' declared void /usr/include/ucontext.h:48: initializer list being treated as compound expression Ok, I think this is not a bug in lily, but rather either in guile or the ia64 include headers. Part of the problem is described in : /* * These are here mostly for backwards compatibility with older Unices. * IA-64 Linux does not distinguish between "struct sigcontext" and * "ucontext_t" as all the necessary info is inside the former. */ But the core reason is that includes which includes , which includes , which includes and immediately afterwards uses ucontext_t which is defined in *behind* the inclusion of . So, if is included *before* , the "#ifndef _XXX_H #define _XXX_H #endif" construct will prevent from including ucontext_t in . So, the solution is in to include before (or, even better, just instead of) , which is anyway an ungly hack. Given this error in current versions of Guile, the workaround for lily is to include in flower/include/libc-extension.hh before including "config.h". BTW, do you think this is a Guile bug or rather a bug in the headers of the ia64 headers of the kernel? -- Han-Wen Nienhuys | hanwen@cs.uu.nl | http://www.xs4all.nl/~hanwen _______________________________________________ Guile-devel mailing list Guile-devel@gnu.org http://mail.gnu.org/mailman/listinfo/guile-devel