m4-1.4.11: build failure on DragonFly

Hi! I don't have a DragonFly box myself, but apparently m4-1.4.11 doesn't compile on it. One of the main DragonFly developers provided a patch, see http://leaf.dragonflybsd.org/mailarchive/users/2008-04/msg00044.html The patch is a patch against pkgsrc, I'll attach the resulting "real" patch aga

m4-1.4.11: build failure on DragonFly

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Thomas Klausner on 4/21/2008 4:46 AM: | Hi! | | I don't have a DragonFly box myself, but apparently m4-1.4.11 doesn't | compile on it. Thanks for the report. Adding bug-gnulib, since this patch should be applied there to affect multiple

M4 checking failed.

Hi, I've compiled M4 and then run 'make check' to run the self-tests. However, the following errors are shown. PASS: test-strstr test-strtod.c:738: assertion failed test-strtod.c:739: assertion failed test-strtod.c:748: assertion failed test-strtod.c:749: assertion failed test-strtod.c:758: a

A small typo in the docs

Hi! While reading the m4 documentation (www.gnu.org/software/m4/manual, last update on April 02, 2008) I found a small typographical error. In section 1.2 Historical References, there is an allusion to Christopher Strachey. His name was erroneously written as Stratchey. The same mistake can be see

Re: A small typo in the docs

Fernando Carrijo gmail.com> writes: > > Hi!While reading the m4 documentation (www.gnu.org/software/m4/manual, last update on April 02, 2008) I found a small typographical error. In section 1.2 Historical References, there is an allusion to Christopher Strachey. His name was erroneously writt

Re: Working os/2 configuratie

Eric Blake byu.net> writes: > Done in the patch below, and tested with mingw. Basically, since I'm testing > that M4 can handle NUL bytes, I can use M4 to generate NUL bytes :) But breaks things when ported to M4 head, at least when tested on the uninstalled wrapper in one of my trees built w

Re: extended stdio API on DragonFly

> | One of the main DragonFly developers provided a patch, see > | http://leaf.dragonflybsd.org/mailarchive/users/2008-04/msg00044.html Thanks. Matthew Dillon added the __sreadahead function just a few days ago. It is equivalent to gnulib's freadahead function, except that freadahead returns 0 if

Re: Working os/2 configuratie

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Gary V. Vaughan on 4/21/2008 5:36 PM: |> +if test "${M4MODPATH+set}" = set ; then |> + M4MODPATH="@abs_top_builddir@/modules:$M4MODPATH" |> +else |> + M4MODPATH="@abs_top_builddir@/modules" |> +fi | | M4MODPATH="@abs_top_builddir@/modul

Re: M4 checking failed.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to [EMAIL PROTECTED] on 4/21/2008 4:18 AM: | Hi, | |I've compiled M4 and then run 'make check' to run | the self-tests. However, the following errors are | shown. | | PASS: test-strstr | test-strtod.c:738: assertion failed | | May I

Re: Working os/2 configuratie

Hi Eric, On 21 Apr 2008, at 22:29, Eric Blake wrote: According to Gary V. Vaughan on 4/21/2008 5:36 PM: |> +if test "${M4MODPATH+set}" = set ; then |> + M4MODPATH="@abs_top_builddir@/modules:$M4MODPATH" |> +else |> + M4MODPATH="@abs_top_builddir@/modules" |> +fi | | M4MODPATH="@abs_top_builddi