From: "Bill Schottstaedt" <bil@ccrma.Stanford.EDU>
Subject: Re: Guile 1.7.91 has been released.
Date: Mon, 13 Feb 2006 04:49:25 -0800 [thread overview]
Message-ID: <20060213124618.M39651@ccrma.Stanford.EDU> (raw)
In-Reply-To: <87y80gyxrq.fsf@zagadka.de>
In solaris 10, I think the readdir_r usage is incorrect.
gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I.. -g -O2 -Wall -Wmissing-prototypes -MT filesys.lo -MD -
MP -MF .deps/filesy
s.Tpo -c filesys.c -fPIC -DPIC -o .libs/filesys.o
filesys.c: In function `scm_readdir':
filesys.c:860: error: `NAME_MAX' undeclared (first use in this function)
filesys.c:860: error: (Each undeclared identifier is reported only once
filesys.c:860: error: for each function it appears in.)
filesys.c:863: error: too many arguments to function `readdir_r'
readdir_r is now:
struct dirent *readdir_r(DIR *dirp, struct dirent *entry);
I changed filesys.c line 860 (or thereabouts) from:
union {
struct dirent ent;
char pad1 [sizeof(struct dirent) + NAME_MAX];
char pad2 [offsetof (struct dirent, d_name) + NAME_MAX + 1];
} u;
SCM_SYSCALL (readdir_r ((DIR *) SCM_CELL_WORD_1 (port), &u.ent, &rdent));
to:
struct dirent ent;
SCM_SYSCALL (readdir_r ((DIR *) SCM_CELL_WORD_1 (port), &ent));
and the rest went smoothly, although I had to remove -Werror from libguile/Makefile
because:
In file included from eval.c:5969:
eval.c: In function `deval':
eval.c:3248: warning: implicit declaration of function `alloca'
make[2]: *** [libguile_la-eval.lo] Error 1
make[2]: Leaving directory `/home/bil/test/guile-1.7.91/libguile'
make[1]: *** [all-recursive] Error 1
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2006-02-13 12:49 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-12 23:15 Guile 1.7.91 has been released Marius Vollmer
2006-02-12 23:46 ` Michael Tuexen
2006-02-14 21:50 ` Marius Vollmer
2006-02-18 23:45 ` Han-Wen Nienhuys
2006-02-20 20:59 ` Marius Vollmer
2006-02-13 8:37 ` Han-Wen Nienhuys
2006-02-13 9:41 ` Ludovic Courtès
2006-02-13 19:50 ` Marius Vollmer
2006-02-14 9:22 ` Ludovic Courtès
2006-02-14 19:39 ` Marius Vollmer
2006-02-13 12:49 ` Bill Schottstaedt [this message]
2006-02-13 21:35 ` Kevin Ryde
2006-02-13 22:33 ` Bill Schottstaedt
2006-02-13 22:50 ` Kevin Ryde
2006-02-13 23:35 ` Bill Schottstaedt
2006-02-14 0:58 ` Kevin Ryde
2006-02-14 1:28 ` Kevin Ryde
2006-02-14 21:36 ` Bill Schottstaedt
2006-02-15 0:03 ` Kevin Ryde
2006-02-15 7:56 ` Ludovic Courtès
2006-02-15 12:37 ` Guile 1.7.91 has been released (x86-64 segfault) Bill Schottstaedt
2006-02-14 9:27 ` Guile 1.7.91 has been released Ludovic Courtès
2006-02-13 15:31 ` Bill Schottstaedt
2006-02-14 8:50 ` Andy Wingo
2006-02-20 18:36 ` Neil Jerram
2006-02-20 20:04 ` Bill Schottstaedt
2006-02-13 18:40 ` Bill Schottstaedt
2006-02-14 11:35 ` Han-Wen Nienhuys
2006-02-14 21:32 ` Marius Vollmer
2006-02-14 13:58 ` 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=20060213124618.M39651@ccrma.Stanford.EDU \
--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).