Re: gzip 1.3.14 beta - djgpp makefile error fixed (?)

Allan wrote: > Following up on a thread regarding gzip 1.3.13, I was getting the error > message " no rule to make target - getopt.h". I have got past this error > but still cannot build due to my lack of expertise, apparently broken > djgpp installation and possibly missing gnu libraries. I did ch

Re: Error message doesn't say, "error"

* Alfred M. Szmidt wrote on Sun, Nov 15, 2009 at 06:08:58PM CET: >> configure.ac:9: version `sharutils_version' doesn't follow Gnits standards > >> Where do you get this error from? > >automake. See info Automake Gnits. > > I must be missing something u

Re: Error message doesn't say, "error"

> > configure.ac:9: version `sharutils_version' doesn't follow Gnits > > standards BTW, the fact that there is an `error:' missing is a bug in Automake: Or TODO item, whatever you'd like to call it.

Re: Error message doesn't say, "error"

* Alfred M. Szmidt wrote on Sun, Nov 15, 2009 at 06:08:58PM CET: >> configure.ac:9: version `sharutils_version' doesn't follow Gnits > standards > >> Where do you get this error from? > >automake. See info Automake Gnits. > > I must be missing something utterly obvious, Line w

Re: Error message doesn't say, "error"

> configure.ac:9: version `sharutils_version' doesn't follow Gnits standards > Where do you get this error from? automake. See info Automake Gnits. I must be missing something utterly obvious, but I cannot find it at all: ~/s $ /bin/grep -ir "follow Gnits" autoconf automake gnuli

Re: Error message doesn't say, "error"

* Alfred M. Szmidt wrote on Sun, Nov 15, 2009 at 05:44:40PM CET: >Without some clear marker, it is more than a little hard to find. >This is line 414 of 619 lines of typescript text: > > configure.ac:9: version `sharutils_version' doesn't follow Gnits standards > Where do you get this

Re: Error message doesn't say, "error"

By the way, the `latest' version (i.e. old :-) is avaiable at ... http://gnu.org/software/womb/gnits/

Re: Error message doesn't say, "error"

Without some clear marker, it is more than a little hard to find. This is line 414 of 619 lines of typescript text: configure.ac:9: version `sharutils_version' doesn't follow Gnits standards That is how error messages in GNU look like, and have looked like for the past 20 years. You ca

Re: [PATCH] test-freading: remove a temporary file

Bruno Haible wrote: >> Without this change, this test's temporary file is left behind every >> time it is run. >> >> Any objection? > > The #include and the first unlink are fine. Thanks, well spotted. > > The second unlink is better omitted, since when the message "file operations > failed" > mes

xalloc-die-tests

Pushed. /Simon >From a31c6b23b94970756cf070ab279bb6e5e6af0156 Mon Sep 17 00:00:00 2001 From: Simon Josefsson Date: Sun, 15 Nov 2009 17:20:06 +0100 Subject: [PATCH] Add xalloc-die self-test. --- ChangeLog|7 +++ gnulib-tool |1 + modules/xalloc-die-tests

Re: RFC comments in lib / gc-pbkdf2-sha1.c

> > =20 >> Hello, all. When importing some gnulib code to GRUB2 I stumbled across= =20 >> lib / gc-pbkdf2-sha1.c having comments taken from RFC2898. As far as I= >> know RFC licence prohibits modifications. This seems to be GPL-incompa= tible. >> So is there are any licencing problem with this fi

Re: [PATCH] fix build warning in fnmatch_loop.c

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Robert Millan on 11/15/2009 3:46 AM: > > You don't want the assert() though? I figured it'd be useful for extra > safety. Safety from what? The code has been quite well-tested, belongs to a static method, and both p and startp are loca

Re: RFC comments in lib / gc-pbkdf2-sha1.c

Vladimir 'phcoder' Serbinenko writes: > Hello, all. When importing some gnulib code to GRUB2 I stumbled across > lib / gc-pbkdf2-sha1.c having comments taken from RFC2898. As far as I > know RFC licence prohibits modifications. This seems to be GPL-incompatible. > So is there are any licencing p

RFC comments in lib / gc-pbkdf2-sha1.c

Hello, all. When importing some gnulib code to GRUB2 I stumbled across lib / gc-pbkdf2-sha1.c having comments taken from RFC2898. As far as I know RFC licence prohibits modifications. This seems to be GPL-incompatible. So is there are any licencing problem with this file? Thanks in advance -- Re

Re: [PATCH] fix build warning in fnmatch_loop.c

On Sat, Nov 14, 2009 at 03:41:59PM -0700, Eric Blake wrote: > > Oh, I see. I repeated the experiment on a 64-bit machine, and got the > same error even with -Dbar=1U. It comes because (p - startp) is a 64-bit > ptrdiff_t, but 1U is only 32-bit, so it promotes to long rather than > unsigned long,