From: David Diffenbaugh <INVALID.NOREPLY@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>,
"David Halik" <dhalik@nbcs.rutgers.edu>,
"David Diffenbaugh" <davediff@nbcs.rutgers.edu>,
bug-guile@gnu.org
Subject: [bug #21378] guile 1.8.3 numbers.c fails to compile in Solaris 9
Date: Wed, 06 Feb 2008 16:23:28 +0000 [thread overview]
Message-ID: <20080206-162327.sv65384.85597@savannah.gnu.org> (raw)
In-Reply-To: <20080206-135652.sv59484.66616@savannah.gnu.org>
Follow-up Comment #6, bug #21378 (project guile):
The patch allowed numbers.c to be compiled without a problem, however it
looks like the same issue occurs in libguile/strings.c
"strings.c", line 132: reference to static identifier "scm_double_cell" in
extern inline function
This compiles by replacing
SCM_C_INLINE_KEYWORD SCM with only SCM on line 127
The only other problem I encountered was with the file read.c Sun CC doesn't
have the predefined macro __FUNCTION__. I believe __FUNCTION__ should return
the undecorated name of the enclosing function (as a string). Since it only
occurs twice in the file I just replaced it with the name of the enclosing
function which allowed the compile to complete. Appears to run fine after
installation.
I have your original changes plus the two mentioned above attached in the
file below.
Thanks,
Dave D.
(file #14971)
_______________________________________________________
Additional Item Attachment:
File name: guile.inline-2.patch Size:2 KB
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?21378>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
next prev parent reply other threads:[~2008-02-06 16:23 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
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 [this message]
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=20080206-162327.sv65384.85597@savannah.gnu.org \
--to=invalid.noreply@gnu.org \
--cc=bug-guile@gnu.org \
--cc=davediff@nbcs.rutgers.edu \
--cc=dhalik@nbcs.rutgers.edu \
--cc=ludo@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).