From: Jan Nieuwenhuizen <janneke@gnu.org>
Subject: CVS build warning
Date: Wed, 31 Mar 2004 19:58:31 +0200 [thread overview]
Message-ID: <87vfkkrj94.fsf@peder.flower> (raw)
but with the default -Werror flag it breaks the build. I'm sorry that
I don't know the right fix, a simple cast or SCM2PTR or something?
Greetings,
Jan.
make[2]: Entering directory `/var/fred/cvs/savannah/guile/guile-core/libguile'
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I.. -I../libguile-ltdl -g -O2 -DSCM_DEBUG_CELL_ACCESSES=1 -Wall -Wmissing-prototypes -Werror -MT guile.o -MD -MP -MF ".deps/guile.Tpo" \
-c -o guile.o `test -f 'guile.c' || echo './'`guile.c; \
then mv -f ".deps/guile.Tpo" ".deps/guile.Po"; \
else rm -f ".deps/guile.Tpo"; exit 1; \
fi
In file included from ../libguile.h:132,
from guile.c:32:
../libguile/inline.h: In function `scm_cell':
../libguile/inline.h:101: warning: comparison between pointer and integer
make[2]: *** [guile.o] Error 1
make[2]: Leaving directory `/var/fred/cvs/savannah/guile/guile-core/libguile'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/fred/cvs/savannah/guile/guile-core'
make: *** [all] Error 2
19:51:37 janneke@peder:~/cvs/savannah/guile/guile-core
$ gcc --version
gcc (GCC) 3.3.3 (Debian 20040321)
Copyright (C) 2003 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien | http://www.lilypond.org
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next reply other threads:[~2004-03-31 17:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-31 17:58 Jan Nieuwenhuizen [this message]
2004-05-10 21:47 ` CVS build warning Marius Vollmer
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=87vfkkrj94.fsf@peder.flower \
--to=janneke@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).