bug-guile
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: guile-1.8.5 test failures


From: Ludovic Courtès
Subject: Re: guile-1.8.5 test failures
Date: Sun, 08 Jun 2008 20:21:12 +0200
User-agent: Gnus/5.11 (Gnus v5.11) Emacs/22.1 (gnu/linux)

Hi,

"Peter O'Gorman" <address@hidden> writes:

> On Wed, Jun 04, 2008 at 10:07:04PM -0500, Peter O'Gorman wrote:
>> On Mon, Jun 02, 2008 at 09:50:27PM +0200, Ludovic Courtès wrote:
>> > > 3. Fix build error on Tru64 Unix with the DEC compiler, which does not 
>> > > like
>> > >    the non-constant expression in case: statements, and on irix which 
>> > > does
>> > >    not like the non-constant expression in the initializers in read.c and
>> > >    print.c. (yes, I know - yuck).
>> > 
>> > But these are constants!
>> 
>> I'll look into this again.

> In this statement, "0=0" is not constant, but occurs in a context that 
> requires a constant expression. (needconstexpr)

OK, makes sense.

> + /* The Tru64 Unix compiler and HP compiler have issues with case
> + * (0?0=0:x), the compilers see 0=0 and dislike the non-constant
> + * expression in a case statement, so for them no type-checking is
> + * performed. Note that the case to scm_t_bits is required, if we just
> + * define SCM_UNPACK(x) (x) we get errors about returning a pointer
> + * when an int was expected */
> +#if defined __DECC || defined __HP_cc

Your report above mentions IRIX, not HP-UX, and 1.8.5 successfully
compiles on HP-UX 11.11 with HP's cc ("HP92453-01
B.11.X.36086-36089-36092.GP HP C Compiler", as reported by "cc -V").

Thus, the "#ifdef __HP_cc" must be changed to match whatever SGi's
compiler defines---this is `__sgi' according to [0] for the C++
compiler.

Can you confirm this?

Thanks,
Ludovic.

[0] http://ac-archive.sourceforge.net/ac-archive/ac_cxx_compiler_vendor.html





reply via email to

[Prev in Thread] Current Thread [Next in Thread]