From: "Kevin Brott" <kevin.brott@providence.org>
To: "Guile-User" <guile-user@gnu.org>
Subject: Re: Guile 1.8.2 Compile Error [GAH]
Date: Wed, 14 Nov 2007 12:28:57 -0800 [thread overview]
Message-ID: <1195072137.24926.4.camel@vanguard.or.providence.org> (raw)
In-Reply-To: <107476.82904.qm@web37904.mail.mud.yahoo.com>
On Wed, 2007-11-14 at 11:17 -0800, Mike Gran wrote:
> You are correct. There is a value in that macro called "_Complex_I" that is, for some reason, being processed down to "__I", losing the word "Complex".
>
> What if you replace "_Complex_I" with "(0.0 + 1.0i)" ?
>
> Good Luck,
>
> Mike Gran
Replacing "_Complex_I" with "(0.0 + 1.0i)" and doing a fresh compile
works - with the caveat that I had to remove -Werror from
configure-generated CFLAGS to get past the type-punned warning.
Now I need to figure out WTH is wrong with the AIX <complex.h> that
_Complex_I is dereferencing as __I when the notes in that file clearly
state that __I shouldn't ever be called directly.
--
#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-14 20:28 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 [this message]
2007-11-15 12:59 ` Ludovic Courtès
2007-11-15 18:10 ` Kevin Brott
2007-11-15 20:18 ` Kevin Brott
-- 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=1195072137.24926.4.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).