Ralf Wildenhues <[EMAIL PROTECTED]> writes:
> Hi Simon,
>
> * Simon Josefsson wrote on Fri, Jul 07, 2006 at 01:58:00AM CEST:
>> Simon Josefsson <[EMAIL PROTECTED]> writes:
>>
>> > I'll see if I can fix the crc module, it is probably the same 64-bit
>> > problem as in the md4 or md5 module a while
Hi Simon,
* Simon Josefsson wrote on Fri, Jul 07, 2006 at 01:58:00AM CEST:
> Simon Josefsson <[EMAIL PROTECTED]> writes:
>
> > I'll see if I can fix the crc module, it is probably the same 64-bit
> > problem as in the md4 or md5 module a while ago.
>
> Nope, I think the self-test was created wit
Simon Josefsson <[EMAIL PROTECTED]> wrote:
> Shishi actually do @include getdate.texi in its manual, so please
> don't install this part.
And GNU tar does the same.
Regards,
Sergey
Hello Eric,
* Eric Blake wrote on Fri, Jul 07, 2006 at 03:12:21AM CEST:
> According to Ralf Wildenhues on 7/6/2006 2:51 PM:
> >
> > 1) $destdir may not contain slashes: gnulib-tool does `mkdir "$destdir"'
> >to create it, and `cd "$destdir"; $cmds; cd ..' to enter/exit.
>
> That also could r
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Ralf Wildenhues on 7/6/2006 2:51 PM:
>
> 1) $destdir may not contain slashes: gnulib-tool does `mkdir "$destdir"'
>to create it, and `cd "$destdir"; $cmds; cd ..' to enter/exit.
That also could run into problems if CDPATH is defined
Simon Josefsson <[EMAIL PROTECTED]> writes:
> I'll see if I can fix the crc module, it is probably the same 64-bit
> problem as in the md4 or md5 module a while ago.
Nope, I think the self-test was created with an old buggy crc.c
implementation. I've changed the test vector to be what the curren
Paul Eggert <[EMAIL PROTECTED]> writes:
> Ralf Wildenhues <[EMAIL PROTECTED]> writes:
>
>> 4) Documentation should not be copied into the source tree (bug in
>>getdate module; I'm inferring from other modules here) or the
>>gnulib-tool should 'mkdir doc' to avoid a cp failure. OK?
>
> My
Ralf Wildenhues <[EMAIL PROTECTED]> writes:
> 4) Documentation should not be copied into the source tree (bug in
>getdate module; I'm inferring from other modules here) or the
>gnulib-tool should 'mkdir doc' to avoid a cp failure. OK?
My kneejerk reaction is I'd rather that gnulib-tool c
One of the cheapest (ahem) ways to catch a number of gnulib bugs is to
create one tree with all modules and all tests in it. If it works, that
is. So I started doing this manually, again. Here's some fallout on
the way to make
path/to/gnulib-tool --with-tests $l --dir=foo --megatest
work.
