unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Didier Godefroy <ldg@ulysium.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guile-user@gnu.org
Subject: Re: Building guile 1.8.6 on Tru64 5.1b
Date: Tue, 21 Apr 2009 22:25:00 +0200	[thread overview]
Message-ID: <C613F83C.2807D%ldg@ulysium.net> (raw)
In-Reply-To: <874owhddw4.fsf@gnu.org>

>> numbers.c: In function 'scm_is_unsigned_integer':
>> numbers.c:5756: warning: control may reach end of non-void function
>> '__gmpz_get_ui' being inlined
> 
> That appears to be more of a GMP and/or GCC problem.  There are bug
> reports against GCC for incorrect diagnostics of that sort, e.g.,
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21800 .  That could be
> something like that.
> 
> Which version of GMP and GCC are you using?

gmp 4.1.4
gcc 4.0.2

> In the meantime, you can try compiling without `-Werror', run "make
> check", and report back.

PASS: test-system-cmds
PASS: test-require-extension
PASS: test-bad-identifiers
PASS: test-num2integral
PASS: test-round
PASS: test-gh
PASS: test-asmobs
PASS: test-list
PASS: test-unwind
FAIL: test-conversion
PASS: test-use-srfi
PASS: test-scm-c-read
PASS: test-with-guile-module
PASS: test-scm-with-guile
==================================
1 of 14 tests failed


One more small detail to report. I mentioned that all the include flags were
being duplicated throughout the compile process, but actually I'm a bit
wrong. The flags start to be duplicated when entering the libguile
directory, not before that.


-- 
Didier Godefroy
mailto:dg@ulysium.net






  parent reply	other threads:[~2009-04-21 20:25 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
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 [this message]
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=C613F83C.2807D%ldg@ulysium.net \
    --to=ldg@ulysium.net \
    --cc=guile-user@gnu.org \
    --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).