, so (to save everyone some
time) I've added that dependency as follows. In the long run stdbool
will go away, since C99 will become universal, but that will be
several years from now I guess.
2005-05-06 Paul Eggert [EMAIL PROTECTED]
* modules/argmatch (Depends-on): Add stdbool
Bruno Haible [EMAIL PROTECTED] writes:
time_r is even more in the library camp, because it's more important
for a library to be MT-safe than for an application.
Thanks for the advice. I changed time_r to be LGPL too.
___
bug-gnulib mailing list
Derek Price [EMAIL PROTECTED] writes:
We've been removing those sort of constructs from CVS as part of the
move away from KR support. IIRC, I was told that typecasts to and from
(void *) were necessary on some really old systems, but that I could be
confident that we wouldn't encounter any
I installed this change, to adjust recently-added gnulib files to
the gnulib tradition that the CVS version says GPL and gnulib-tool
turns this into the LGPL as needed.
2005-05-13 Paul Eggert [EMAIL PROTECTED]
* byteswap_.h, getsubopt.h, iconvme.h, strsep.c, strsep.h:
Change
I installed the following:
2005-05-14 Paul Eggert [EMAIL PROTECTED]
Sync from coreutils.
* lib/gethrxtime.c, lib/gethrxtime.h, lib/getpass.h, lib/mountlist.h,
lib/path-concat.c, lib/regex.h, lib/strtoll.c, lib/unlocked-io.h,
lib/xtime.h: White space changes only
One other remark about glob.c. You should remove this comment, as
it's obsolete now:
/* Comment out all this code if we are using the GNU C Library, and are not
actually compiling the library itself. This code is part of the GNU C
Library, but also included in many other GNU
Derek Price [EMAIL PROTECTED] writes:
But let's step back a second. Why are we worried about building
gnulib glob.c under glibc? It will never happen, right? So perhaps
we needn't worry about this problem at all.
Won't it? I thought the idea was that when you and I settled on
something that
Derek Price [EMAIL PROTECTED] writes:
Corrected patch attached.
Thanks. A couple more things. (Sorry I didn't catch it earlier.)
First, the $gl_* variables should be cached, with AC_CACHE_CHECK.
Second, suppose limits.h and sys/param.h have conflicting
definitions of MIN and MAX? To work
I installed this into gnulib. This is just an internal cleanup; it
shouldn't affect behavior.
2005-05-18 Paul Eggert [EMAIL PROTECTED]
* lib/canonicalize.c: Include canonicalize.h first, to test interface.
Include stddef.h unconditionally, since we assume C89 now.
All
Yoann Vandoorselaere [EMAIL PROTECTED] writes:
There is also a problem with the 'intprops.h' dependency.
When gnulib-tool is run, the file is included, but it doesn't seem to be
listed as part of the generated Makefile.am, leading to 'dist' trouble.
I have removed this dependency; fts no
: /cvsroot/gnulib/gnulib/lib/getlogin_r.c,v
retrieving revision 1.1
diff -p -u -r1.1 getlogin_r.c
--- lib/getlogin_r.c25 May 2005 14:21:20 - 1.1
+++ lib/getlogin_r.c25 May 2005 19:12:57 -
@@ -18,7 +18,9 @@
/* written by Paul Eggert and Derek Price */
-#include config.h
Jim Meyering [EMAIL PROTECTED] writes:
Besides, isn't it worth a tiny sacrifice to avoid
systematically including meaningless (and long) strings
like onlinepubs/009695399/ in our code and documentation?
I'm reluctant to put URLs like that in the code or documentation,
since they mutate too
Bruno Haible [EMAIL PROTECTED] writes:
The crucial trick here is the ability to compile lstat.c so that it uses
the original lstat function (be it #defined to lstat64 or not).
This idea looks good to me. But:
! static int
! rpl_lstat (const char *file, struct stat *sbuf)
Surely the static
to stick to the C convention for errno.
(Sorry, I'd forgotten that rule.)
On the other hand, there's no need to restore errno, and apps
shouldn't depend on its being preserved.
I installed this. It should be enough to conform to the C convention,
right?
2005-05-27 Paul Eggert [EMAIL PROTECTED
Derek Price [EMAIL PROTECTED] writes:
1. Corrects an incorrect check for a successful return from
getlogin_r to assume only 0 means success, per the POSIX2 spec:
http://www.opengroup.org/onlinepubs/009695399/functions/getlogin_r.html.
2. Moves the check for GLOB_MARK
The following patch was installed on gnulib but it looks inadvertent.
I assume it's OK for me to revert it? Or perhaps you could revert it.
Index: bison.m4
===
RCS file: /cvsroot/gnulib/gnulib/m4/bison.m4,v
retrieving revision 1.4
Derek Price [EMAIL PROTECTED] writes:
It may be. It looks like the change was intentional
(http://sources.redhat.com/cgi-bin/cvsweb.cgi/libc/sysdeps/generic/glob.c?rev=1.52content-type=text/x-cvsweb-markupcvsroot=glibc),
but I still disagree.
I agree with you. Historically, the * pattern in
James Youngman [EMAIL PROTECTED] writes:
Any ideas/suggestions?
Does the following untested patch fix things? It attempts to mimic
what Bash does.
*** fnmatch.c Fri May 13 23:03:58 2005
--- /tmp/fnmatch.c Tue Jun 7 00:02:03 2005
*** fnmatch (const char *pattern, const char
Bruno Haible [EMAIL PROTECTED] writes:
Five years ago, people made up lists of programs that _do_ work with UTF-8
encoded text files. Today, these programs are uncountable. Instead, people
make up lists of programs that _don't_ work with Unicode:
Derek Price [EMAIL PROTECTED] writes:
+ [test ${$1+set} = set],
+ [{ as_var=$1; eval test \\${$as_var+set}\ = set; }])])
That change looks like it can do only good, so I installed it into
Autoconf. Thanks.
I'm not sure about the documentation change. It's not yet clear to me
that we
of the glibc version?
But in any event, the .c fix should go in, so I installed this into gnulib:
2005-06-10 Paul Eggert [EMAIL PROTECTED]
* fnmatch.c (fnmatch): If there is an encoding error in a
multibyte string or pattern, fall back on unibyte matching.
Problem reported
is being called.
How about the following (untested) change instead? It omits the tests
when they're unnecessary, but it doesn't establish a dependency of
xalloc on calloc. I'd rather leave out dependencies like that if it's
easy.
2005-06-16 Paul Eggert [EMAIL PROTECTED]
* xmalloc
to
reverse the sense and call it HAVE_GNU_CALLOC or something like
that. How about the following (also untested) patch?
2005-06-17 Paul Eggert [EMAIL PROTECTED]
* xmalloc (HAVE_GNU_CALLOC): New macro.
(xcalloc): Omit needless tests if ! HAVE_GNU_CALLOC.
--- xmalloc.c 2005-05-13 23
Jim Meyering [EMAIL PROTECTED] writes:
Oskar Liljeblad [EMAIL PROTECTED] wrote:
What's the proper way to fix these warnings?
quotearg.c: In function `quotearg_n_options':
quotearg.c:586: warning: comparison is always false due to limited range of
data type
Paul, if you don't find a way to
I installed the following (slightly different) patch for that problem,
into gnulib. It's tested with GNU tar.
2005-06-22 Paul Eggert [EMAIL PROTECTED]
* xmalloc.c (HAVE_GNU_CALLOC): New constant.
(xcalloc): Use it to avoid needless tests.
Problem reported by Jim
Tim Waugh [EMAIL PROTECTED] writes:
I had a bug report that 'who -b' and 'who -r' fail to give output with
this patch. This fixes it:
Thanks for reporting that. IS_USER_PROCESS is already defined in
readutmp.h, so I installed this simpler patch in both coreutils
and gnulib.
2005-06-22 Paul
please try it
with your GCC? If it pacifies your GCC I'll propagate it into gnulib
and glibc.
2005-06-22 Paul Eggert [EMAIL PROTECTED]
* mktime.c: Include string.h even if !DEBUG. (From glibc.)
(ranged_convert): Don't save conversion in a temporary struct.
This causes
simply fix GCC instead? Something like the following.
(-Wextra is the new name for -W.) (Also I'd have to document this.)
2005-06-22 Paul Eggert [EMAIL PROTECTED]
* c-common.c (shorten_compare): Unless -Wextra is used,
do not warn against comparisons always being false due
Jim Meyering [EMAIL PROTECTED] writes:
Anyway, I installed this patch into coreutils. Can you please try it
with your GCC? If it pacifies your GCC I'll propagate it into gnulib
and glibc.
It does. Thanks!
OK, I installed it. I also started the ball rolling on propagating
the changes
be used for any object
in C89, e.g.:
mbstate_t initial_state = { 0, };
where we don't know whether mbstate_t is a structure, or an integer,
and the code works either way.
So, I propose that we make the following patch to gnulib, and propagate
this to coreutils:
2005-06-23 Paul Eggert
Derek Price [EMAIL PROTECTED] writes:
Do you want me to keep sending FYI's to this list for this sort of minor
change?
Yes, please.
___
bug-gnulib mailing list
bug-gnulib@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-gnulib
[EMAIL PROTECTED] (Karl Berry) writes:
Here are rms's comments on our draft about the quote character stuff.
1) I don't know how to address his problem with domain at hand, please help?
How about changing this:
Sticking to the ASCII character set (plain text, 7-bit characters) is
Simon Josefsson [EMAIL PROTECTED] writes:
I recall some compilers complaining about a trailing ','s. Is it
really OK by C89? I'm just curious.
Yes, it is allowed in C89.
Perhaps you're thinking of enumeration specifiers. The declaration:
enum { zero, };
is not allowed in C89. (C99
a proposed patch.
2005-06-24 Paul Eggert [EMAIL PROTECTED]
* size_max.m4 (gl_SIZE_MAX): ~(size_t)0 - (size_t) -1,
since the latter works even if size_t is narrower than int.
--- size_max.m4 2005-01-18 05:07:56 -0800
+++ /tmp/size_max.m42005-06-24 11:01:41 -0700
@@ -26,9
[EMAIL PROTECTED] (Karl Berry) writes:
Maybe we should just drop the text about '...' and ..., as it's kind
of implied. Thus:
In the C locale, GNU programs should stick to plain ASCII for
quotation characters in messages to users: preferably 0x60 (`) for
left quotes and 0x27 (') for
I installed the following to fix a porting problem with OpenBSD 3.4.
Its time.h declares 'struct timespec' but does not define it,
i.e., it says only struct timespec;. (That's pretty usesless, hun?)
2005-07-01 Paul Eggert [EMAIL PROTECTED]
* xnanosleep.c: Include timespec.h, since
Patrice Dumas [EMAIL PROTECTED] writes:
I am currently packaging a library under the LGPL, so I cannot use the files
of the gnulib that are under the GPL. Is there somewhere a project similar
with the gnulib but with files with LGPL compatible licences?
Not that I know of.
Note that many of
to prereq.m4 to require
the tzset module).
2005-07-03 Paul Eggert [EMAIL PROTECTED]
Remove the dependency of the strftime module on the tzset module.
* lib/strftime.c (my_strftime)
[! defined _LIBC ! HAVE_RUN_TZSET_TEST]:
Copy the input structure, to work around some
Patrice Dumas [EMAIL PROTECTED] writes:
alloca malloc realloc strtod atexit dup2 getcwd getpagesize memmove memset
strerror regex
These are mostly equivalent to existing and widely used LGPLed code,
so I'd say they should be LGPLed.
I would say the one exception is getcwd, where the code to
Patrice Dumas [EMAIL PROTECTED] writes:
Imagine someone doing coding at 6 places (5 labs and a home)
No, let's not imagine that. (You should be simplifying your life! :-)
Seriously, though, I regularly do something like this:
* Check out a the latest Tar CVS.
* Run ./bootstrap.
This
Stepan Kasal [EMAIL PROTECTED] writes:
A copy of the macro is attached below; does it work for you?
Thanks for suggesting that. Yes, if the current Autoconf macro works
for Bruno, we should simply use a copy of it in gnulib.
___
bug-gnulib mailing
do. Similarly, we shouldn't need to #undef
verify.
I installed this patch into coreutils. Comments?
2005-07-04 Paul Eggert [EMAIL PROTECTED]
* lib/verify.h (GL_CONCAT0, GL_CONCAT): Define unconditionally; don't
depend on whether verify_decl is defined.
(verify
Patrice Dumas [EMAIL PROTECTED] writes:
There is no rpl_mktime defined in mktime.c, although in gl_FUNC_MKTIME
there is
AC_DEFUN([gl_FUNC_MKTIME],
[
AC_REQUIRE([AC_FUNC_MKTIME])
if test $ac_cv_func_working_mktime = no; then
AC_DEFINE(mktime, rpl_mktime,
Doesn't this cause the
is adding
AC_REQUIRE([AC_SYS_LONG_FILE_NAMES])
to the same prerequisites like it is in backupfile.m4.
Thanks; I installed this patch in both gnulib and coreutils:
2005-07-07 Paul Eggert [EMAIL PROTECTED]
* backupfile.m4 (gl_BACKUPFILE): Use AC_CHECK_FUNCS_ONCE on pathconf
Patrice Dumas [EMAIL PROTECTED] writes:
So maybe there shouldn't be
AC_DEFINE(mktime, rpl_mktime,
in gl_FUNC_MKTIME in m4/mktime.m4?
Yes, because otherwise mktime.c would attempt to define an external
function mktime. The C Standard doesn't allow that, and some hosts
don't permit it. The
Bruno Haible [EMAIL PROTECTED] writes:
- Which header files are included by the program, in which order?
That I don't know, but it's pretty easy to see how the problem
would arise by looking at the header (see the pattern below).
- Which C++ header undefines mktime?
On my Debian GNU/Linux
Stepan Kasal [EMAIL PROTECTED] writes:
does this mean that the arbitrarily-deep nesting code is not going to be
contributed back to glibc?
No. I don't think anybody is working on it though, and in the
meantime let's let sleeping dogs lie.
___
Bruno Haible [EMAIL PROTECTED] writes:
What about this patch, then? Add the dependency to the module description.
It's then unnecessary to mention it in the autoconf macro.
Both patches look a bit off to me, since argp should be usable in
multithreaded code. (This is a problem with the
Bruno Haible [EMAIL PROTECTED] writes:
However, Jim's first version with the NULL pointer works in C++ too:
#define verify_expr(R) (void) ((verify_type__ (R) *) 0)
I'd therefore suggest to use this one.
Thanks for catching that; I followed your suggestion in coreutils.
2005-07-11 Paul
Bruno Haible [EMAIL PROTECTED] writes:
I would therefore now suggest to undo the earlier commodity hacks and
return to a state where the modules/* files represent the real dependencies.
Namely, add back 'xalloc-die' as dependency to those modules need it.
Not sure about 'unlocked-io'.
Thanks
Bruno Haible [EMAIL PROTECTED] writes:
Paul Eggert wrote:
I read your email containing accented letters with GNU Emacs 21.4 and
Gnus 5.10.6, a combination that supports UTF-8.
The UTF-8 support in Emacs 21.4 is minimal. Some people recommend the
emacs-unicode-2 branch of the Emacs CVS
Bruno Haible [EMAIL PROTECTED] writes:
So I still think the name lock is fine.
Here's a little bit more evidence. I just checked Debian stable, and
it has an /usr/include/lock.h, installed by an AFS development
package. See:
Simon Josefsson [EMAIL PROTECTED] writes:
1) Port the libc LGPL getdelim into a gnulib module.
2a) Port the libc LGPL getline into a gnulib module.
2b) Write a gnulib LGPL getline module that use the gnulib LGPL getdelim.
3) Keep the current getndelim2 as a GPL module.
The libc getline seem
[EMAIL PROTECTED] (Bob Proulx) writes that
http://en.wikipedia.org/wiki/Quotation_mark#Quotation_marks_in_English:
looks fine to me too on my stock Debian GNU/Linux 3.1 sarge system
running Firefox 1.0.4. (I am saying this only so that readers of the
archive later won't think this is
the underlying problem is first,
before removing this from regex.m4.
2005-07-25 Paul Eggert [EMAIL PROTECTED]
* regex.m4 (gl_INCLUDED_REGEX): Use AC_RUN_ELSE instead of the
obsolescent AC_TRY_RUN. Include the default includes files, for 'exit'.
--- regex.m47 Jul 2005 08:08:39
I removed m4_syscmd, ..., because they were not working on either Mac
OS/X or RHEL3.
Hmm, why not? Shouldn't they be working? What versions of m4 and
Autoconf
were you using? Let's try to see what the underlying problem is first,
before removing this from regex.m4.
Well, I have to
Oskar Liljeblad [EMAIL PROTECTED] writes:
It backports the TEMP_FAILURE_RETRY macro from
GNU Libc to Gnulib.
The proposed implementation isn't portable; it assumes GCC syntax.
And it should probably defer to the unistd.h implementation if available.
My kneejerk reaction is that it's a bit
Ben Pfaff [EMAIL PROTECTED] writes:
Do you know anybody still seriously using a GCC version 2.95 ?
I do not. Is this a serious argument against doing the right
thing?
I think the problem is that we cannot seriously test any changes here.
Also, there are probably some backward-compatibility
filed
a glibc bug report so that it gets put into glibc. Here's what I
installed.
2005-08-15 Paul Eggert [EMAIL PROTECTED]
* config/srclist.txt: Comment out $LIBCSRC/posix/regex.h.
Add comments for each pending glibc patch.
2005-08-15 Bruno Haible [EMAIL PROTECTED
I installed this, adapted from coreutils. I also filed glibc bug 1215
to merge it back into glibc.
2005-08-19 Paul Eggert [EMAIL PROTECTED]
* config/srclist.txt: Comment out $LIBCSRC/posix/regex_internal.c.
* lib/regex_internal.c (re_string_realloc_buffers, re_node_set_insert
I installed this patch, taken from coreutils. I also filed a glibc bug
report.
2005-08-19 Jim Meyering [EMAIL PROTECTED]
* lib/regexec.c (proceed_next_node): Redo local variables to
avoid GCC shadowing warnings.
2005-08-19 Paul Eggert [EMAIL PROTECTED]
* config
I installed this, and filed a glibc bug report.
2005-08-20 Paul Eggert [EMAIL PROTECTED]
* srclist.txt: Add glibc bug 1223.
* lib/regcomp.c (create_initial_state): Remove duplicate decl.
Index: config/srclist.txt
I installed this and filed glibc bug 1225:
2005-08-20 Paul Eggert [EMAIL PROTECTED]
* config/srclist.txt: Add glibc bug 1225.
2005-08-20 Jim Meyering [EMAIL PROTECTED]
* lib/regexec.c (regexec, re_search_stub) [!_LIBC]: Omit declaration
of unused local, dfa
Sam Steingold [EMAIL PROTECTED] writes:
Would you please also consider the 2 patches in
http://article.gmane.org/gmane.comp.lib.gnulib.bugs:3996
OK, I installed the first patch, as follows:
2005-08-20 Paul Eggert [EMAIL PROTECTED]
* config/srclist.txt: Add glibc bug 1226
the following instead (and reported the bug to glibc):
2005-08-20 Paul Eggert [EMAIL PROTECTED]
* config/srclist.txt: Add glibc bug 1227.
* lib/regexec.c (sift_states_bkref): Fix portability bug: the code
assumed that reg_errcode_t is a signed type, which is not
necessarily
Sam Steingold [EMAIL PROTECTED] writes:
the latest and greatest gnulib regexp has the following regressions vs
the previous (monolithic) version:
Sorry, I didn't understand the notation that you used in
http://lists.gnu.org/archive/html/bug-gnulib/2005-08/msg8.html.
I tried to reproduce
Bruno Haible [EMAIL PROTECTED] writes:
That appears to be obsolete. As far as I see, there are no users of this
macro which don't also bundle regex.c.
Yes, that sounds right. I installed this patch into gnulib, and then
reindented.
2005-08-23 Paul Eggert [EMAIL PROTECTED]
* m4
It looks like I spoke too soon and that we still have some regex
problems. Among other things, there seem to be several problems with
the POSIX name space restrictions in regex.h. To get the ball rolling
I installed this:
2005-08-23 Paul Eggert [EMAIL PROTECTED]
* config/srclist.txt
Sam Steingold [EMAIL PROTECTED] writes:
c++ is stricter, so if the code can be compiled with c++ it is probably
safer.
That doesn't match my experience. To make C code work with C++, I
often have to introduce casts (e.g., to convert void * to char *, or
to convert one integer type to
Jim Meyering [EMAIL PROTECTED] writes:
I'll hold off on the commit until Paul signs off on it.
That looks good to me. Thanks for doing the merge.
___
bug-gnulib mailing list
bug-gnulib@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-gnulib
I installed this to patch another POSIX incompatibility with regex,
and filed glibc bug 1240.
2005-08-24 Paul Eggert [EMAIL PROTECTED]
* config/srclist.txt: Add glibc bug 1240.
* lib/regcomp.c (regerror): 2nd arg is 'restrict', as per POSIX.
* lib/regex.h (regerror
Ben Pfaff [EMAIL PROTECTED] writes:
Is there an advantage to defining EX_OK to EXIT_SUCCESS over
defining it to 0?
I can't think of any. Let's please just define it to 0; it's simpler
and less likely to cause trouble.
I also like Simon's suggestion of defining EXIT_SUCCESS and
EXIT_FAILURE
Simon Josefsson [EMAIL PROTECTED] writes:
Ok to install?
OK, with the following caveats:
* Please put the standard implementation first, and the Windows implementation
second. That'll make it easier to read.
* Please use standard GNU indenting style, e.g.,
char *
getpass (const char
Chuck Swiger [EMAIL PROTECTED] writes:
In general, code which assumes that malloc() will never
return NULL is missing a basic sanity check and will result in bugs.
Yes, and that's why gnulib has a malloc wrapper that addresses this
issue systematically. The wrapper handles this sanity check,
Jim Meyering [EMAIL PROTECTED] writes:
Is there a patch yet to make gcc suppress that warning?
Sorry, not yet. Other things are on my plate
- unsigned int n1 = n0 + 1;
+ /* FIXME: technically, the type of n1 should be `unsigned int',
+ but that evokes an unsuppressible
I installed this, to get minor things out of the way before installing
the 64-bit patch for regex. I also filed glibc bug 1273.
2005-08-31 Paul Eggert [EMAIL PROTECTED]
* lib/regex_internal.h (re_sub_match_top_t): Remove unused member
next_last_offset.
(struct re_dfa_t
Jim Meyering [EMAIL PROTECTED] writes:
Is it really permitted to have sizeof (size_t) sizeof (unsigned int)?
Yes, I'm afraid so. The C Standard merely says that size_t is an
unsigned integer type; size_t is allowed to be narrower than unsigned int.
See, for example, Mark Brader's 10-year-old
Simon Josefsson [EMAIL PROTECTED] writes:
But I have never understood why one has to sign per-projects form for
the FSF anyway...
It's a legal thing. When you assign your copyright, you have to
specify what it is you're signing over. Otherwise there could be
abuses of the legal system (you
Bruno Haible [EMAIL PROTECTED] writes:
You're right, and the patch looks good. OK to commit, Paul?
Yes, and thanks for checking it. I committed it.
___
bug-gnulib mailing list
bug-gnulib@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-gnulib
I installed this and filed glibc bug 1302:
2005-09-05 Paul Eggert [EMAIL PROTECTED]
Change bitset word type from unsigned int to unsigned long int,
as this has better performance on typical 64-bit hosts.
Port bitset code to hosts with unusual word sizes.
* lib
Derek Price [EMAIL PROTECTED] writes:
regex_internal.h:837: warning: suggest parentheses around + or - in operand
of
Thanks for reporting that. I installed this patch and updated the glibc
bug report.
2005-09-06 Paul Eggert [EMAIL PROTECTED]
* lib/regex_internal.h (bitset_not
Derek Price [EMAIL PROTECTED] writes:
regex_internal.h: In function â:
regex_internal.h:837: warning: suggest parentheses around + or - in operand
of
By the way, did GCC really say In function â? That is, an a with
a circumflex over it? If so, should this be a GCC bug that we should
be
James Youngman [EMAIL PROTECTED] writes:
On Tue, Sep 06, 2005 at 10:51:45AM -0700, Paul Eggert wrote:
Thanks for reporting that. I installed this patch and updated the glibc
bug report.
Is glibc keeping up with all these patches, or is gnulib;'s regex
implementation now significantly
Derek Price [EMAIL PROTECTED] writes:
shortening the above test to: # if !HAVE_GETADDRINFO, and I'd
rather just simplify the header
Yes, that sounds right.
I think the defined HAVE_GETADDRINFO cruft dates way back to when we
weren't so sure that the Autoconf macro was part of a distribution
-08 Paul Eggert [EMAIL PROTECTED]
* glob.c (glob, globfree, __glob_pattern_p): Use old-style function
definitions, since that's the preferred style in glibc.
Fix a minor spacing issue, and update copyright notice to match glibc's.
* config/srclist.txt: Remove glibc
Sergey Poznyakoff [EMAIL PROTECTED] writes:
The module utimens depends on utime,
Could you please explain why?
As I understand it, the utime module is needed only for ancient
4.3BSD-based systems where the utime function mishandles NULL
arguments. Such systems are no longer in use (and
Sergey Poznyakoff [EMAIL PROTECTED] writes:
Hmm, now I see a better solution: to list m4/utimbuf.m4 in Files
section of modules/utimens.
Right you are. I installed that.
2005-09-08 Paul Eggert [EMAIL PROTECTED]
* modules/utimens (Files): Add m4/utimbuf.m4, since
m4
as needed in glob_.h.
Fourth, we can AC_REQUIRE AC_GNU_SOURCE, so that we needn't worry about
__USE_GNU.
In summary, how about the following patch instead? (Please note that
I haven't tested it.)
2005-09-09 Derek Price [EMAIL PROTECTED]
Paul Eggert [EMAIL PROTECTED]
* modules
Derek Price [EMAIL PROTECTED] writes:
Fourth, we can AC_REQUIRE AC_GNU_SOURCE, so that we needn't worry about
__USE_GNU.
We ran into this problem the first time we went through this:
http://lists.gnu.org/archive/html/bug-gnulib/2005-05/msg00144.html.
Ouch. Sorry I forgot that.
I assume you
I installed this:
2005-09-12 Paul Eggert [EMAIL PROTECTED]
Merge glibc and coreutils changes into gnulib, plus a few
extra fixes.
* lib/md5.c: Use #error rather than a string.
(CYCLIC): New macro, from glibc source. Use it instead of rol.
* lib/md5.h
Ralf Wildenhues [EMAIL PROTECTED] writes:
1) Fix the files that forgot to guard inclusion by HAVE_CONFIG_H.
This is the first patch.
Actually, I was thinking that we should go the other way, and include
config.h unconditionally (except for glibc-derived code). As far as I
know, nobody
Ralf Wildenhues [EMAIL PROTECTED] writes:
I learned about this issue while actually trying to make use of a module
with one of the unguarded files; I did not use AC_CONFIG_HEADERS.
Ok, sorry, I didn't know people still did that. In that case, let's
keep the #if.
Surely there are also
Derek Price [EMAIL PROTECTED] writes:
I've attached hte following for review since I took the liberty of
replacing two #if __GNUC__ = constructs in regex_internal.h with
__GNUC_PREREQ calls.
Let's avoid that, since we want to minimize the differences from glibc.
Other than that, it looks
I installed this as well: it's needed by coreutils but not tar.
2005-09-16 Paul Eggert [EMAIL PROTECTED]
* lib/utimecmp.c: Include stat-time.h.
(SYSCALL_RESOLUTION): Depend on whether various struct stat
members exist, not on the obsolescent ST_MTIM_NSEC
So I installed this:
2005-09-16 Paul Eggert [EMAIL PROTECTED]
* config/srclist.txt: Remove glibc bug 1033 and uncomment mktime.c.
--- config/srclist.txt 8 Sep 2005 20:18:48 - 1.104
+++ config/srclist.txt 16 Sep 2005 21:37:31 - 1.105
@@ -1,4 +1,4 @@
-# $Id
I installed the following into both gnulib and coreutils to simplify
the recently added stat-time.h module a bit:
2005-09-16 Paul Eggert [EMAIL PROTECTED]
* stat-time.h (set_stat_atime, set_stat_ctime, set_stat_mtime):
Remove; they were buggy in the HAVE_STRUCT_STAT_ST_SPARE1
Julien PUYDT [EMAIL PROTECTED] writes:
Paul Eggert a écrit :
Julien PUYDT [EMAIL PROTECTED] writes:
Stepan Kasal a écrit :
I suggest that you get the files from gnulib CVS on savannah.
Those are GPL and not LGPL ;
No, they can be released under either the GPL or the LGPL.
If you use gnulib
Derek Price [EMAIL PROTECTED] writes:
I assume that, since strcase.h provides a prototype for strcasecmp,
other systems have a similar problem and regcomp.c should probably be
#including strcase.h.
Yes. I'm preparing a patch to do that, except it'll be in regex_internal.h
since it's the file
, and verify_expr is for expression contexts.
Here's the patch I just installed:
2005-09-22 Paul Eggert [EMAIL PROTECTED]
* MODULES.html.sh (Diagnostics assert.h): New section,
with verify module.
* modules/verify: New file.
* lib/verify.h: New file.
Index: MODULES.html.sh
I installed this:
2005-09-22 Paul Eggert [EMAIL PROTECTED]
* getloadavg.c: Include fcntl--.h rather than fcntl.h.
Do not include unistd-safer.h.
(getloadavg): Don't call fd_safer; no longer needed
now that we include fcntl--.h.
2005-09-22 Jim Meyering [EMAIL
1 - 100 of 5377 matches
Mail list logo
