On Nov 26, 2007 7:48 AM, Simon Josefsson [EMAIL PROTECTED] wrote:
That is what I do in my projects too: I commit gnulib files, but not
other generated files. The problem I have with switching to any other
mode is reproducibility. When checking out an old version of my
software, how can I be
Simon Josefsson [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] (Karl Berry) writes:
The three possibilities are listed in
http://www.gnu.org/software/gettext/manual/html_node/Files-under-CVS.html
There's another possibility, which apparently both you and I follow in
different ways:
Micah Cowan wrote:
While attempting to compile sed from current CVS, I ran across the
following output from bootstrap.sh:
+ cc -DHAVE_CONFIG_H -I.. -I. -c getline.c
getline.c:26: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’
before ‘getline’
Line 26 is the ssize_t
Hello Ralf,
Ralf Wildenhues wrote:
error: pr_byname.h: No such file or directory
Thank you for reporting this.
OK to apply this patch to fix it? Or would you rather add more include
paths?
I would prefer more -I options: If some day the directory structure needs
to be changed, I prefer to
I received a bug report for Texinfo (about AIX 4.3.3) that strncasecmp
was not declared without #include strings.h -- that is, strings.h, not
string.h.
The spec at
http://www.opengroup.org/onlinepubs/009695399/functions/strcasecmp.html
says the same.
The strcase gnulib module only mentions
Karl Berry wrote:
The spec at
http://www.opengroup.org/onlinepubs/009695399/functions/strcasecmp.html
says the same.
The strcase gnulib module only mentions string.h, though, and we don't
seem to do anything with strings.h anywhere.
Yes, gnulib declares these functions in string.h since
Jim Meyering pushed for a quick resolution:
I'm hoping to make a coreutils test release RSN,
and one of the few things missing is the macro to help
work around the freebsd 6.1 long double printf bug.
Your test proggie results revealed that the bug is that although
'long double' generally has
Bruno Haible [EMAIL PROTECTED] wrote:
Jim Meyering pushed for a quick resolution:
I'm hoping to make a coreutils test release RSN,
and one of the few things missing is the macro to help
work around the freebsd 6.1 long double printf bug.
Your test proggie results revealed that the bug is
Hi everyone,
I have a trouble at oset modules of gnulib. I have written my dispose
function, I get as parameter a void pointer,
which it seems I must free too. However its prototype is like:
typedef void (*gl_setelement_dispose_fn) (const void *elt);
Then, if I declare my function with a
gl_REVISION([abc6ba7cb8ac9acb9acd..])
I don't have any objection to such a feature, but I probably wouldn't
use it myself -- I update from gnulib too often to want to munge
configure.ac every time. Pretty much the only time I refrain from
updating is nearing a release.
Best,
karl
10 matches
Mail list logo
