From: Bill Schottstaedt <bil@ccrma.Stanford.EDU>
Subject: OSX 10.4 and CVS Guile
Date: Wed, 20 Jul 2005 04:10:48 -0700 [thread overview]
Message-ID: <42DE3138.6040303@ccrma> (raw)
On OSX 10.4 the CVS Guile hits:
eval.c:2657: error: 'PTHREAD_RECURSIVE_MUTEX_INITIALIZER_NP' undeclared here (not in a function)
make[2]: *** [libguile_la-eval.lo] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
/usr/include/pthread.h on this system does not define this identifier.
Then (configured --without-threads):
gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I.. -no-cpp-precomp -I/Users/bil/test/include -Wall -Wmissing-prototypes -Werror -c posix.c -MT
posix.lo -MD -MP -MF .deps/posix.TPlo -fno-common -DPIC -o .libs/posix.o
In file included from /usr/include/netinet/in.h:78,
from /usr/include/netdb.h:86,
from posix.c:122:
/usr/include/sys/socket.h:99: error: two or more data types in declaration specifiers
make[2]: *** [posix.lo] Error 1
As far as I can tell, socklen_t is defined in both netdb.h and socket.h
(included by netinet/in.h), but both are protected by #ifndef __SOCKLEN_T.
Not sure why this is happening.
In Fedora Core 4 (gcc 4.0), the CVS Guile hits:
cc1: warnings being treated as errors
numbers.c: In function 'scm_is_unsigned_integer':
numbers.c:5711: warning: control may reach end of non-void function '__gmpz_get_ui' being inlined
make[2]: *** [libguile_la-numbers.lo] Error 1
I forgot to check which version of gmp this is.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
reply other threads:[~2005-07-20 11:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=42DE3138.6040303@ccrma \
--to=bil@ccrma.stanford.edu \
/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).