From: "Kevin Brott" <kevin.brott@providence.org>
To: "Guile-User" <guile-user@gnu.org>
Subject: Re: Guile 1.8.2 Compile Error [GAH]
Date: Thu, 15 Nov 2007 12:18:41 -0800 [thread overview]
Message-ID: <1195157921.4359.17.camel@vanguard.or.providence.org> (raw)
In-Reply-To: <1195150204.4359.3.camel@vanguard.or.providence.org>
On Thu, 2007-11-15 at 10:10 -0800, Kevin Brott wrote:
> On Thu, 2007-11-15 at 13:59 +0100, Ludovic Courtès wrote:
> >
> > `Complex' in `_Complex_I' can't possibly be macro-expanded. There must
> > be something else.
>
> Could line 52 be expanded/dereferenced by cpp to make _Complex_I resolve
> as __I?
>
As it turns out - that's exactly what's happening - if I replace the
'_Complex_I' macro with the short-form 'I' macro in numbers.c - cpp
still renders it as __I, and gcc can't compile it because it's not
defined.
This leads me to believe it is a GCC issue with this code directive in
guile 1.8 (which isn't in the 1.4 or 1.6 guile source trees), in that
__I is not being defined by the gcc. AIX's complex.h says specifically
"__I is provided by the AIX xlc C99 compiler" - which argues that gcc on
AIX is not providing it, hence the failure.
My best guess is a fixincludes issue, or possibly not offered on systems
not using GNU libc.
I'm still looking into a fix - as the manual substitution of _Complex_I
in numbers.c isn't workable. Looks like it might be time for me to
start bugging gcc devs about what could be causing this.
>From the guile end - perhaps using a detect that uses whatever the old
routine was for this function - when compiler = gcc and OS = AIX ?
--
#include <stddisclaimer.h>
/* Kevin Brott <Kevin.Brott@Providence.org>
* Unix Systems Engineer - SA Group - Provtech
* Providence Health Systems, Tigard, OR
*/
DISCLAIMER:
This message is intended for the sole use of the addressee, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the addressee you are hereby notified that you may not use, copy, disclose, or distribute to anyone the message or any information contained in the message. If you have received this message in error, please immediately advise the sender by reply email and delete this message.
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2007-11-15 20:18 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-14 19:17 Guile 1.8.2 Compile Error [GAH] Mike Gran
2007-11-14 20:28 ` Kevin Brott
2007-11-15 12:59 ` Ludovic Courtès
2007-11-15 18:10 ` Kevin Brott
2007-11-15 20:18 ` Kevin Brott [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-11-14 1:00 Mike Gran
[not found] <1194888764.4167.13.camel@vanguard.or.providence.org>
[not found] ` <87fxzbql1e.fsf@chbouib.org>
2007-11-12 21:37 ` Guile 1.8.2 Compile Error Kevin Brott
2007-11-12 23:14 ` Ludovic Courtès
2007-11-12 23:39 ` Guile 1.8.2 Compile Error [GAH] Kevin Brott
2007-11-12 23:46 ` Kevin Brott
2007-11-12 23:51 ` Ludovic Courtès
2007-11-13 0:08 ` Kevin Brott
2007-11-13 19:00 ` Kevin Brott
2007-11-13 22:20 ` Ludovic Courtès
2007-11-13 23:05 ` Kevin Brott
2007-11-14 0:39 ` Neil Jerram
2007-11-14 1:29 ` Kevin Brott
2007-11-14 1:54 ` Kevin Brott
2007-11-14 13:35 ` Ludovic Courtès
2007-11-14 17:59 ` Kevin Brott
2007-11-14 18:37 ` Kevin Brott
2007-11-15 20:50 ` Neil Jerram
2007-11-16 16:50 ` Ludovic Courtès
2007-11-26 21:26 ` Neil Jerram
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1195157921.4359.17.camel@vanguard.or.providence.org \
--to=kevin.brott@providence.org \
--cc=guile-user@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).