ia64 problem

* ia64 problem
@ 2003-08-25 10:55 Han-Wen Nienhuys
  2003-09-12 23:16 ` Rob Browning
  0 siblings, 1 reply; 2+ messages in thread
From: Han-Wen Nienhuys @ 2003-08-25 10:55 UTC (permalink / raw)
  Cc: reuter

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 <reuter@ipd.uka.de>
To: lilypond-devel@gnu.org
Cc: Juergen Reuter <reuter@ipd.uka.de>
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
<sys/ucontext.h>:

/*
 * 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 <libguile/continuations.h>
includes <sys/ucontext.h> which includes <signal.h>, which includes
<ucontext.h>, which includes <sys/ucontext.h> and immediately afterwards
uses ucontext_t which is defined in <sys/ucontext.h> *behind* the
inclusion of <signal.h>.  So, if <sys/ucontext.h> is included *before*
<signal.h>, the "#ifndef _XXX_H #define _XXX_H #endif" construct will
prevent <ucontext.h> from including ucontext_t in <sys/ucontext.h>.

So, the solution is in <libguile/continuations.h> to include <signal.h>
before (or, even better, just instead of) <sys/ucontext.h>, which is
anyway an ungly hack.  Given this error in current versions of Guile, the
workaround for lily is to include <signal.h> 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

^ permalink raw reply	[flat|nested] 2+ messages in thread