From: hyperdivision@firefly.is-a-geek.org (hyperdivision)
Subject: libguile/socket.c
Date: Mon, 06 Feb 2006 02:43:14 -0600 [thread overview]
Message-ID: <20060206084314.B6F9B727B@firefly.is-a-geek.org> (raw)
line 1259 from cvs
libguile/socket.c
size_t c_address_size needs to be set to 0
otherwise gcc4 croaks.
also, i am having no luck getting cvs to work with x86_64
alot of errors and i can't get any of them worked out.
stack overflows, etc.
if you want more specific info i can send the build messages.
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile
next reply other threads:[~2006-02-06 8:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-06 8:43 hyperdivision [this message]
2006-02-09 10:10 ` libguile/socket.c Neil Jerram
2006-02-09 12:01 ` libguile/socket.c Ludovic Courtès
2006-02-09 13:43 ` libguile/socket.c Neil Jerram
2006-02-09 21:46 ` libguile/socket.c Marius Vollmer
2006-02-10 6:58 ` libguile/socket.c Neil Jerram
2006-02-10 8:21 ` libguile/socket.c Marius Vollmer
2006-02-10 8:37 ` libguile/socket.c 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=20060206084314.B6F9B727B@firefly.is-a-geek.org \
--to=hyperdivision@firefly.is-a-geek.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).