Hello,
I'm resending the GC-cleanup patch in a hopefully more readable form.
Han-Wen: let me know if it's alright.
Thanks,
Ludovic.
---BeginMessage---
Hi,
[EMAIL PROTECTED] (Han-Wen Nienhuys) writes:
void
-scm_i_adjust_min_yield (scm_t_cell_type_statistics *freelist)
+scm_i_adjust_min_yield
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:
I don't think NAME_MAX is defined anywhere -- the documentation says
you should use pathconf instead. Here's the portion of limits.h where
they commented out NAME_MAX:
/*
* POSIX 1003.1a, section 2.9.5, table 2-5 contains [NAME_MAX] and the
* related text states:
*
* A definition of one of
Bill Schottstaedt [EMAIL PROTECTED] writes:
(The d_name field is still defined to be 1 char long, so I think the
glibc comment still pertains to Solaris,
I guess that means you can't just define a struct. What does the
readdir_r man page say you should do? pathconf like you said?
Bill Schottstaedt [EMAIL PROTECTED] writes:
I found some examples by Googling for readdir_r and _PC_NAME_MAX.
Incomplete bit of code below, it's not pretty but I guess it's what
has to be done.
#if HAVE_READDIR_R
/* On Solaris 2.7, struct dirent only contains char d_name[1] and the
Oops, I see opendir doesn't record the opened directoryname. Hmm. It
might be easiest for now to just stick a mutex around plain readdir()
and worry later about readdir_r and its buffer size.
___
Guile-devel mailing list
Guile-devel@gnu.org
