Re: [PATCH] maint.mk: add syntax-check rule: detect unnecessary #include

Bruno Haible wrote: > Jim Meyering wrote: >> u64.h >> lib/uninorm/normalize-internal.h >> xreadlink.h >> >> The xreadlink.h use is obviously unused so >> I've removed it (2nd cset, below), >> but I haven't looked at the others yet. > > I've trimmed it from lib/uninorm/normalize-internal.h as

Re: syncing Emacs from sources maintained elsewhere

* Paul Eggert wrote on Sun, Jan 23, 2011 at 09:38:58PM CET: > On 01/23/2011 04:39 AM, Eli Zaretskii wrote: > > > . Why are PACKAGE and VERSION needed, and where are they used? > > That's another Automake thing. PACKAGE should be "emacs", > and VERSION "24.0.50". VERSION is used in some auxilia

Re: syncing Emacs from sources maintained elsewhere

> Date: Sun, 23 Jan 2011 12:38:58 -0800 > From: Paul Eggert > CC: emacs-de...@gnu.org, bug-gnulib > > On 01/23/2011 04:39 AM, Eli Zaretskii wrote: > > > . Why is NO_MINUS_C_MINUS_O needed? Which compilation uses this > >macro? > > That's an Autoconf thing; gnulib doesn't use it. I think

Re: Files from gnulib

> Date: Sun, 23 Jan 2011 11:29:37 -0800 > From: Paul Eggert > CC: emacs-de...@gnu.org, bug-gnulib > > Developers on Microsoft Windows platforms all have access to > better file systems these days, surely. I'm talking only about the MSDOS port. The Windows port has no problems with these file n

Re: Files from gnulib

> From: Stefan Monnier > Cc: Eli Zaretskii , bug-gnulib , > emacs-de...@gnu.org > Date: Sun, 23 Jan 2011 22:26:52 -0500 > > > The Emacs trunk already has seventeen other files > > with 2 dots in their file names, with names like > > lisp/gnus/.dir-locals.el > > I don't know how MSDOS handles

Re: Files from gnulib

> The Emacs trunk already has seventeen other files > with 2 dots in their file names, with names like > lisp/gnus/.dir-locals.el I don't know how MSDOS handles names that start with dot, so either this is a special case that's OK, or it's indeed a problem which we hadn't noticed yet. > and admin

new module 'vma-iter'

As a preparation for a module that determines the size of the data segment (in the sense of RLIMIT_DATA), I'm moving the system dependent code for iterating through the memory areas of a process to a new module. 2011-01-23 Bruno Haible New module 'vma-iter'. * lib/vma-iter.h:

Re: Still unable to build trunk

>> It sounds harsh to me to ask every one who builds out of VCS to have >> to climb such a steep curve. > I dunno, I just started doing some Emacs development after > about five years' absence, and it was a pretty steep learning > curve for me. We decided a long time ago that it should be possible

Re: Documentation for the regexp module

I think it would be nice to make the regex module to import a texinfo file documenting the supported regular expressions syntax I agree in principle, but ... We could get the "Regular Expression Syntax" chapter in its own file regex-syntax.texi, .. this isn't ideal as-is. Ther

Re: [PATCH] maint.mk: add syntax-check rule: detect unnecessary #include

Jim Meyering wrote: > u64.h > lib/uninorm/normalize-internal.h > xreadlink.h > > The xreadlink.h use is obviously unused so > I've removed it (2nd cset, below), > but I haven't looked at the others yet. I've trimmed it from lib/uninorm/normalize-internal.h as well. u64.h looks like it coul

Re: Files from gnulib

Paul Eggert replied to Eli Zaretskii: > > Some of the new files added from gnulib use file names that are > > invalid on 8+3 (aka MSDOS) filesystems. These files are: > > > > c++defs.h -- the `+' character is not allowed in file names > > I am sympathetic to the proposal to rename c++defs.h to

Re: Still unable to build trunk

On 01/23/2011 09:00 AM, Eli Zaretskii wrote: > It sounds harsh to me to ask every one who builds out of VCS to have > to climb such a steep curve. I dunno, I just started doing some Emacs development after about five years' absence, and it was a pretty steep learning curve for me. For example, no

Re: syncing Emacs from sources maintained elsewhere

On 01/23/2011 04:39 AM, Eli Zaretskii wrote: > . Why is NO_MINUS_C_MINUS_O needed? Which compilation uses this >macro? That's an Autoconf thing; gnulib doesn't use it. I think it's not needed in config.h, and will look into removing it at some point. In the meantime, don't worry about it;

Re: new module 'get-rusage-as'

>NetBSD: > a) setrlimit with RLIMIT_AS works. > b) No VMA iteration API exists. Actually, on NetBSD 5.0, there is a /proc file system, like on FreeBSD. Let's extend get_rusage_as() accordingly. In practice it makes no difference, though, since iterating over /proc/curproc/maps yields

Re: Files from gnulib

[Adding bug-gnulib to the thread that started in ]: On 01/23/2011 04:15 AM, Eli Zaretskii wrote: > Some of the new files added from gnulib use file names that are > invalid on 8+3 (aka MSDOS) filesystems. These files are: > >

[PATCH] maint.mk: add syntax-check rule: detect unnecessary #include

Here's another prohibit-header-without-use rule. Note that applying it manually to gnulib's .h files found a few: git ls-files|grep '\.h$' \ | xargs grep -l '^ *#include *' \ | xargs grep -wLE 'NULL|offsetof|ptrdiff_t|size_t|wchar_t' u64.h lib/uninorm/normalize-internal.h xreadlink.h

Re: new module 'get-rusage-as'

A small bug fix to this module: 2011-01-23 Bruno Haible get-rusage-as: Fix bug. * lib/get-rusage-as.c (get_rusage_as_via_setrlimit): Restore the original limit when aborting the first loop. --- lib/get-rusage-as.c.origSun Jan 23 18:55:08 2011 +++ lib/get-rusage-as

Re: [PATCH] gl_CHECK_NEXT_HEADERS implies AC_CHECK_HEADERS_ONCE

Hi Paul, > * m4/wctype_h.m4 (gl_WCTYPE_H): Likewise. This part of the patch did something else: It changed an gl_CHECK_NEXT_HEADERS invocation to gl_NEXT_HEADERS. But this means that when the header does not exist, NEXT_WCTYPE_H will not be set, thus the gnulib-generated wctype.h replacement wil

Re: speed up 'configure' by removing HAVE_RAW_DECL_*

Hi Paul, > one way to would be to follow the example of > gl_ASSERT_NO_GNULIB_TESTS, and add a macro > gl_ASSERT_NO_GNULIB_POSIXCHECK that says "we don't want support for > GNULIB_POSIXCHECK", as follows: > >+# gl_ASSERT_NO_GNULIB_POSIXCHECK >+# asserts that there will never be a need to

Re: move-if-change and parallel make

Hi Paul, thanks for the review. * Paul Eggert wrote on Sat, Jan 22, 2011 at 09:07:08PM CET: > On 01/22/2011 08:03 AM, Ralf Wildenhues wrote: > > > -if test -r "$2" && cmp -s -- "$1" "$2"; then > > +if test -r "$2" && $cmpprog -- "$1" "$2" >/dev/null; then > >rm -f -- "$1" > > else > > - mv