Re: fseeko bug

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Larry Jones on 12/16/2007 11:50 AM: > Eric Blake writes: >> Then maybe the best course of action, for now, is just reverting the >> verification I added (since with the verify in place, you can't even >> compile, whereas without the verify

Re: Incompatible module license.

Eric Blake <[EMAIL PROTECTED]> wrote: > According to Yoann Vandoorselaere on 12/17/2007 3:18 AM: >> Hi, >> >> The glob module is licensed under LGPLv2+, and was previously compatible >> with the module it depended on. >> >> I wanted to perform an update today, but there has been changes to the >> g

header file order issue on tar-1.19/lib/inttypes.h

Hello, I am attempting to build tar-1.19 on VMS. I am getting an error assert from inttypes.h: "This file assumes that 'int' has exactly 32 bits. Please report your platform and compiler to . From the analysis of the macro values used to generate the error assert, I have discovered that IN

Re: Incompatible module license.

Yoann Vandoorselaere <[EMAIL PROTECTED]> wrote: > Hi, > > The glob module is licensed under LGPLv2+, and was previously compatible > with the module it depended on. > > I wanted to perform an update today, but there has been changes to the > glob module that make it depend on non LGPL modules: > >

Re: Gnulib and gettext conflicts?

Eric Blake <[EMAIL PROTECTED]> writes: > According to Simon Josefsson on 12/17/2007 4:41 AM: >> >> My attempts to solve it (e.g., overwrite autopoint files with gnulib >> files) caused unnecessary invocations of autoconf due to file time >> changes, and I wasn't able to make it work smoothly. > >

Re: detection of functional openat() for usage inside getcwd.c

Petr Salinger <[EMAIL PROTECTED]> wrote: >>> getcwd.c uses *at() function family iff AT_FDCWD is defined. >>> This approach does not work on GNU/kFreeBSD - FreeBSD kernel + GNU libc. >>> The kernel does not provide needed interfaces, and therefore glibc >>> provides only stub version for function

Re: Incompatible module license.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Yoann Vandoorselaere on 12/17/2007 3:18 AM: > Hi, > > The glob module is licensed under LGPLv2+, and was previously compatible > with the module it depended on. > > I wanted to perform an update today, but there has been changes to the

Re: Gnulib and gettext conflicts?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Simon Josefsson on 12/17/2007 4:41 AM: > > My attempts to solve it (e.g., overwrite autopoint files with gnulib > files) caused unnecessary invocations of autoconf due to file time > changes, and I wasn't able to make it work smoothly. M

Re: Gnulib and gettext conflicts?

FYI, I resolved this issue by upgrading to gettext 0.17 in my packages. Gettext 0.17 is available in Debian, so was easy to do. Still, it seems unfortunate that there aren't any instructions on how to get gettext 0.16 and gnulib to get along. My attempts to solve it (e.g., overwrite autopoint fil

Re: m4-1.4.10 segfault with x86_64 during ./configure when checking whether printf supports infinite 'long double' arguments

Gilles Espinasse wrote: > It compile fine. I didn't look the result of tests. > The problem stay un-noticed for some times until I was looking at the > console screen during compilation. So the only problem is that the configure test crashes? This is easy to fix; I'm applying this patch: 2007-12-

Incompatible module license.

Hi, The glob module is licensed under LGPLv2+, and was previously compatible with the module it depended on. I wanted to perform an update today, but there has been changes to the glob module that make it depend on non LGPL modules: - openat - save-cwd - chown - d-ino - exit - exitfail -