From: I.Gutheil <i.gutheil@fz-juelich.de>
To: bug-guile@gnu.org
Subject: Intel icc finds too many errors in guile 1.8.8 to compile
Date: Fri, 28 Aug 2009 11:22:49 +0200 [thread overview]
Message-ID: <4A97A1E9.1000708@fz-juelich.de> (raw)
Hello all,
did anyone try to compile the guile codes with another compiler but the gcc?
When I tried to use the icc, I got
gen-scmconfig.c(257): error #279: controlling expression is constant
if (SCM_I_GSC_C_INLINE)
^
gen-scmconfig.c(321): error #279: controlling expression is constant
if (SCM_I_GSC_T_INT64)
^
gen-scmconfig.c(333): error #279: controlling expression is constant
if (SCM_I_GSC_T_UINT64)
So I had to change the
if (SCM_I_GSC_T_UINT64)
to
#ifdef (SCM_I_GSC_T_UINT64)
#else
#endif
because these directives had nun-numerical values.
The next problem occured with
debug.c(62): error #188: enumerated type mixed with another type
scm_dynwind_begin (0);
This could be "corrected" by declaring
in dynwind.h
SCM_API void scm_dynwind_begin (int) instead of the derived datatype
which could only be 1
and in dynwind.c
void
scm_dynwind_begin (int flags)
...
I get a lot of remarks that
operands are evaluated in unspecified order
and
remark #193: zero used for undefined preprocessing identifier
"HAVE_SYS_STDTYPES_H"
(for example)
but finally I came to a compiler error which I could not correct:
eval.c(4114): error #589: transfer of control bypasses initialization of:
variable "orig_sym" (declared at line 4038)
goto handle_a_macro;
^
And just for eval.c I get about 700 remarks like
eval.c(6021): remark #981: operands are evaluated in unspecified order
return SCM_I_XEVAL (x, env);
^
(which is the last one)
So I think I have to switch to gcc and just accept what gcc is making of
that code??
Any better idea?
P.S. I do not use the guile package myself but I want to install it for
someone who wants to use meep on a Nehalem Cluster here in Juelich.
Sincerely
Inge Gutheil
--
Inge Gutheil
Juelich Supercomputing Centre
Institute for Advanced Simulation
Forschungszentrum Juelich GmbH
52425 Juelich, Germany
Phone: +49-2461-61-3135
Fax: +49-2461-61-6656
E-mail: i.gutheil@fz-juelich.de
------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------
Forschungszentrum Juelich GmbH
52425 Juelich
Sitz der Gesellschaft: Juelich
Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498
Vorsitzende des Aufsichtsrats: MinDir'in Baerbel Brumme-Bothe
Geschaeftsfuehrung: Prof. Dr. Achim Bachem (Vorsitzender),
Dr. Ulrich Krafft (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt,
Prof. Dr. Sebastian M. Schmidt
------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------
next reply other threads:[~2009-08-28 9:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-28 9:22 I.Gutheil [this message]
2009-10-02 21:21 ` Intel icc finds too many errors in guile 1.8.8 to compile Neil Jerram
2009-10-03 9:43 ` Ludovic Courtès
[not found] ` <8763avzfh9.fsf@ossau.uklinux.net>
[not found] ` <87r5tjbb0h.fsf@gnu.org>
2009-10-06 21:06 ` Neil Jerram
2009-10-06 22:50 ` Ludovic Courtès
2009-10-07 21:09 ` 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=4A97A1E9.1000708@fz-juelich.de \
--to=i.gutheil@fz-juelich.de \
--cc=bug-guile@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).