From: David Halik <INVALID.NOREPLY@gnu.org>
To: "Ludovic Courtès" <ludovic.courtes@laas.fr>,
"David Halik" <dhalik@nbcs.rutgers.edu>,
bug-guile@gnu.org
Subject: [bug #21378] guile 1.8.3 numbers.c fails to compile in Solaris 9
Date: Sun, 21 Oct 2007 16:38:47 +0000 [thread overview]
Message-ID: <20071021-163847.sv59484.52052@savannah.gnu.org> (raw)
In-Reply-To: <20071021-132528.sv15145.21683@savannah.gnu.org>
Follow-up Comment #2, bug #21378 (project guile):
Ah, I see what you're getting at. I've actually run into this before.
"inline" is the correct keyword in suncc, but it is much more strict C99 than
gcc, which is usually the case with Sun Studio. You might want to check out
this post, it explains the different uses of inline related to Sun, C99, GNU,
etc, and their incompatibilities with examples. This isn't my best subject,
but it looks like your question can be answered there.
http://www.mail-archive.com/bug-gnulib@gnu.org/msg04321.html
As far as your configure, it looks like it finds inline ok, Suncc is just not
happy with its usage.
configure:21606: checking for inline
configure:21656: result: inline
ac_cv_c_inline=inline
SCM_I_GSC_C_INLINE='"inline"'
We try to use Suncc whenever possible to avoid gcc lib dependencies across
our platforms and because Suncc ferrets out Sun problems more often, but it is
always possible of course. ;) Thanks for the clarification about the
bugtracker by the way.
-Dave
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?21378>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile
next prev parent reply other threads:[~2007-10-21 16:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-20 21:29 [bug #21378] guile 1.8.3 numbers.c fails to compile in Solaris 9 David Halik
2007-10-21 13:25 ` Ludovic Courtès
2007-10-21 16:38 ` David Halik [this message]
2008-02-04 13:40 ` Ludovic Courtès
2008-02-06 13:52 ` Ludovic Courtès
2008-02-06 13:56 ` David Halik
2008-02-06 16:23 ` David Diffenbaugh
2008-02-07 9:32 ` Ludovic Courtès
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=20071021-163847.sv59484.52052@savannah.gnu.org \
--to=invalid.noreply@gnu.org \
--cc=bug-guile@gnu.org \
--cc=dhalik@nbcs.rutgers.edu \
--cc=ludovic.courtes@laas.fr \
/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).