From: ludo@gnu.org (Ludovic Courtès)
To: guile-user@gnu.org
Subject: Re: Building guile 1.8.6 on Tru64 5.1b
Date: Sun, 19 Apr 2009 00:43:29 +0200 [thread overview]
Message-ID: <874owlh9bi.fsf@gnu.org> (raw)
In-Reply-To: C610037C.27F2F%ldg@ulysium.net
[-- Attachment #1: Type: text/plain, Size: 781 bytes --]
Hi,
Didier Godefroy <ldg@ulysium.net> writes:
> gc_os_dep.c:1130: warning: type defaults to 'int' in declaration of '_end'
> gc_os_dep.c: In function 'scm_get_stack_base':
> gc_os_dep.c:1916: warning: comparison of distinct pointer types lacks a cast
The attached patch should fix it. Can you try it and report back?
(Apply it with "patch -p1 < /the/patch.diff" from the top-level source
directory.)
> In the previous 1.8.5 version which I could never build successfully, I was
> using a cflag -DSCM_DEBUG_TYPING_STRICTNESS=0 although I forgot how I was
> brought to use it, it's been a while since I tried building 1.8.5
This is no longer needed (see
http://git.savannah.gnu.org/cgit/guile.git/commit/?id=95c6523b03387997d62c1bed57bd1a0864e30836).
Hope this helps,
Ludo'.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: The patch --]
[-- Type: text/x-patch, Size: 768 bytes --]
diff --git a/libguile/gc_os_dep.c b/libguile/gc_os_dep.c
index d89f1cf..7bc9644 100644
--- a/libguile/gc_os_dep.c
+++ b/libguile/gc_os_dep.c
@@ -1127,7 +1127,7 @@ scm_get_stack_base ()
# ifdef OSF1
# define OS_TYPE "OSF1"
# define DATASTART ((ptr_t) 0x140000000)
- extern _end;
+ extern int _end;
# define DATAEND ((ptr_t) &_end)
# define HEURISTIC2
/* Normally HEURISTIC2 is too conervative, since */
@@ -1912,7 +1912,7 @@ void *scm_get_stack_base()
# if STACK_GROWS_DOWN
result = GC_find_limit((ptr_t)(&dummy), TRUE);
# ifdef HEURISTIC2_LIMIT
- if (result > HEURISTIC2_LIMIT
+ if ((ptr_t)result > HEURISTIC2_LIMIT
&& (ptr_t)(&dummy) < HEURISTIC2_LIMIT) {
result = HEURISTIC2_LIMIT;
}
next prev parent reply other threads:[~2009-04-18 22:43 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-18 20:23 Building guile 1.8.6 on Tru64 5.1b Didier Godefroy
2009-04-18 22:43 ` Ludovic Courtès [this message]
2009-04-19 9:04 ` Didier Godefroy
2009-04-21 13:59 ` Didier Godefroy
2009-04-21 14:10 ` Linas Vepstas
2009-04-21 15:19 ` Ludovic Courtès
2009-04-21 18:35 ` Didier Godefroy
2009-04-21 19:00 ` Ludovic Courtès
2009-04-21 19:37 ` Didier Godefroy
2009-04-21 20:40 ` Ludovic Courtès
2009-04-21 15:14 ` Ludovic Courtès
2009-04-21 18:25 ` Didier Godefroy
2009-04-21 18:47 ` Didier Godefroy
2009-04-21 19:07 ` Ludovic Courtès
2009-04-21 19:46 ` Didier Godefroy
2009-04-21 20:41 ` Ludovic Courtès
2009-04-21 20:53 ` Didier Godefroy
2009-04-21 22:55 ` Ludovic Courtès
2009-04-22 8:11 ` Didier Godefroy
2009-04-22 8:23 ` Didier Godefroy
2009-04-22 9:27 ` Ludovic Courtès
2009-04-22 14:39 ` Didier Godefroy
2009-04-23 22:49 ` Ludovic Courtès
2009-04-25 12:29 ` Didier Godefroy
2009-04-25 13:24 ` Mike Gran
2009-04-25 14:19 ` Didier Godefroy
2009-04-21 20:25 ` Didier Godefroy
2009-04-21 20:50 ` Ludovic Courtès
2009-04-21 20:58 ` Didier Godefroy
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=874owlh9bi.fsf@gnu.org \
--to=ludo@gnu.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).