Re: tests/test-base64.c: executable?

2006-11-28 Thread Mark D. Baushke
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jim Meyering [EMAIL PROTECTED] writes: [EMAIL PROTECTED] (Larry Jones) wrote: Jim Meyering writes: Simon Josefsson [EMAIL PROTECTED] wrote: Here too. Is this possible to fix without direct access to the CVS repository? Yep, but it's a

Re: Updating FreeBSD port

2006-09-21 Thread Mark D. Baushke
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 FYI. My FreeBSD 4.x systems do not have a getopt.h file installed. My FreeBSD 6.1-RELEASE i386 system says this: $ ./foo GNU getopt $ POSIXLY_CORRECT=1 ./foo OpenBSD getopt $ -- Mark Eric Blake-1 [EMAIL PROTECTED] writes: It

inttypes.m4 minor bug fix

2006-09-18 Thread Mark D. Baushke
, -- Mark 2006-09-18 Mark D. Baushke [EMAIL PROTECTED] * inttypes.m4 (gl_cv_header_working_stdint_h): Avoid 'test: =: unary operator expected' on Solaris 9. (gl_cv_header_inttypes_h): Be consistent in quoting. Index: inttypes.m4

Re: bootstrap: marking gnulib-copied/generated files as such

2006-09-08 Thread Mark D. Baushke
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jim Meyering [EMAIL PROTECTED] writes: case $CVS_RSH in '') export CVS_RSH=ssh;; esac One of the following would be better, given that not all shells allow assignment on an export command: case $CVS_RSH in '') CVS_RSH=ssh; export

strnlen.h

2006-09-07 Thread Mark D. Baushke
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I am confused about why some code does this: #if defined HAVE_DECL_STRNLEN !HAVE_DECL_STRNLEN and other code does this: #if !HAVE_DECL_GETADDRINFO If you must check for it being defined, wouldn't this form #if !defined HAVE_DECL_STRNLEN ||

Re: new module proposal: split

2006-09-05 Thread Mark D. Baushke
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Davide Angelocola [EMAIL PROTECTED] writes: On Tuesday 05 September 2006 22:01, Ben Pfaff wrote: Davide Angelocola [EMAIL PROTECTED] writes: I'm proposing another new module for gnulib: split. The function signature is: char

Re: printing size_t variables

2006-09-02 Thread Mark D. Baushke
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Eric Blake [EMAIL PROTECTED] writes: Should we have a gnulib module for *printf that allows us to use the POSIX-mandated printf(%zu, (size_t)1) modifier for size_t variables? Or what is the current recommended practice for printing size_t?

Re: compilation flags per object file

2006-08-25 Thread Mark D. Baushke
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ralf Wildenhues [EMAIL PROTECTED] writes: Hello Bruno, * Bruno Haible wrote on Fri, Aug 25, 2006 at 03:07:26PM CEST: I would love to replace DEFS += -DLIBDIR=\$(libdir)\ with localcharset_CPPFLAGS = $(AM_CPPFLAGS)

Re: compilation flags per object file

2006-08-25 Thread Mark D. Baushke
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ralf Wildenhues [EMAIL PROTECTED] writes: Hello Bruno, Mark, * Mark D. Baushke wrote on Fri, Aug 25, 2006 at 06:01:03PM CEST: There should be no ambiguity if you add the $(ext) to the makefile macro name: localcharset($ext)_CPPFLAGS

Re: hello 2.1.91 pretest

2006-08-21 Thread Mark D. Baushke
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ralf Wildenhues [EMAIL PROTECTED] writes: Hello Mark, * Mark D. Baushke wrote on Mon, Aug 21, 2006 at 10:37:06AM CEST: Ralf Wildenhues [EMAIL PROTECTED] writes: Suggested patch below. OK? I like your change as I think it makes

GNULIB stdint_.h vs windows VC6 compiler

2006-08-21 Thread Mark D. Baushke
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Folks, It seems that the latest stdint_.h file is using contructs that is confusing the windows VC6 compiler used to build the CVS sources. The two problems are .\windows-NT\stdint.h(133) : warning C4067: unexpected tokens following

Re: GNULIB stdint_.h vs windows VC6 compiler

2006-08-21 Thread Mark D. Baushke
PROTECTED] writes: - Original Message - From: Paul Eggert [EMAIL PROTECTED] To: Dennis Jones [EMAIL PROTECTED] Cc: bug-gnulib@gnu.org; Mark D. Baushke [EMAIL PROTECTED]; bug-cvs@nongnu.org Sent: Monday, August 21, 2006 9:57 AM Subject: Re: GNULIB stdint_.h vs windows VC6 compiler

Re: CVS -D option with time offset

2006-07-31 Thread Mark D. Baushke
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Larry Jones [EMAIL PROTECTED] writes: Dirk Stoecker writes: cvs diff -D 2006-07-27T18:50:00 CVS is interpreting the T between the date and time as a military timezone. You should use a space instead. Hmmm... Yes, it looks like it takes

Re: cycle-check.h fix imported from coreutils

2006-07-06 Thread Mark D. Baushke
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ralf Wildenhues [EMAIL PROTECTED] writes: * Paul Eggert wrote on Tue, Jul 04, 2006 at 09:43:44AM CEST: Mark D. Baushke [EMAIL PROTECTED] writes: -lib_SOURCES += cycle-check.c cycle-check.h dev-ino.h +lib_SOURCES += cycle-check.c cycle

Re: cycle-check.h fix imported from coreutils

2006-07-04 Thread Mark D. Baushke
Hi Paul, I suspect that you may need something like this or the same-inode.h file will not be added to the tarball with a 'make dist' command. Or at least, it does not seem to do the job with autoconf 2.60. Am I missing something? -- Mark Index: cycle-check

Re: simplification rewrite of stdint module installed into gnulib

2006-07-03 Thread Mark D. Baushke
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Paul Eggert [EMAIL PROTECTED] writes: Mark D. Baushke [EMAIL PROTECTED] writes: +#if @HAVE_SYS_INTTYPES_H@ [EMAIL PROTECTED]@ /* Solaris 7 sys/inttypes.h has the types except the *_fast*_t types, and the macros except for *_FAST

stdint_.h vs MacOS X 10.4.6

2006-07-03 Thread Mark D. Baushke
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Problem: The /usr/include/stdint.h file on MacOS X, apparently needs to be 'fixed' by generation of the GNULIB stdint_.h file into stdint.h, but includes taken later have a problem in that sys/types.h actually does the #include of stdint.h for us.

Re: simplification rewrite of stdint module installed into gnulib

2006-07-03 Thread Mark D. Baushke
[I sent a rather large e-mail message which had another variation of this patch. I think this one is better. The other has not yet appeared on the bug-gnulib or bug-cvs mailing lists.] The following patch seems to be needed due to MacOS X 10.4.6 doing a '#include stdint.h' from inside of

Re: coreutils merge into gnulib

2006-07-03 Thread Mark D. Baushke
I suspect the following patch was missed... Otherwise same-inode.h may not get into the distribution tarballs of cycle-check users. -- Mark Index: modules/cycle-check === RCS file:

Re: coreutils merge into gnulib

2006-07-03 Thread Mark D. Baushke
The modules/dirname seems to now depend on xstrndup if gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I. -I.. -I../intl -Ino/include -g -O2 \ -MT basename.o -MD -MP -MF .deps/basename.Tpo -c -o basename.o basename.c; \ then mv -f .deps/basename.Tpo .deps/basename.Po; else rm -f .deps/basename\ .Tpo; exit

typo in getaddrinfo.c

2006-06-30 Thread Mark D. Baushke
Fixed in CVS sources. -- Mark 2006-06-30 Jim Hyslop [EMAIL PROTECTED] * getaddrinfo.c: fixed typo Index: getaddrinfo.c === RCS file: /sources/gnulib/gnulib/lib/getaddrinfo.c,v retrieving revision 1.10 diff -u -p

Re: [bug-gnulib] Re: stdint.h on IRIX-5.3 SGI-cc

2006-06-27 Thread Mark D. Baushke
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Martin, As an FYI, one of the test machines that builds the CVS sources nightly is an SGI IRIX64 running 6.5 (Hmmm... I had thought we also had an SGI IRIX 5.3 out there somewhere, but I must have been confused as I do not see any results from

Re: stdint module on SGI

2006-06-26 Thread Mark D. Baushke
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Bruno, I believe your patch has a typo. It uses _c99 instead of __c99 as the symbol that the SGI c99 compiler defines. -- Mark Bruno Haible [EMAIL PROTECTED] writes: Mark D. Baushke wrote: Yes. I am told that /usr/include/stdint.h

Re: stdint.h on IRIX-5.3 SGI-cc

2006-06-23 Thread Mark D. Baushke
Hi Martin, The CVS project has forked from the GNULIB project slightly for the stdint stuff as I have not seen any commit to gnulib to support the SGI compilation problems we had observed. I have hopes that they will either adopt our changes or equivalent changes so that we can once more use

Re: stdint module on SGI

2006-06-23 Thread Mark D. Baushke
Hi Bruno, The CVS forked version is getting closer to the GNULIB version. (See below). Bruno Haible [EMAIL PROTECTED] writes: Mark D. Baushke wrote: The following two patches take a closer step toward making things work under the default c89 compiler on SGI boxes. Thanks for suggesting

stdint module

2006-06-22 Thread Mark D. Baushke
including stdint.h if everything works with just inttypes.h. Reported by Mark D. Baushke [EMAIL PROTECTED]. * m4/stdint.h: Ditto. Index: lib/stdint_.h === RCS file: /sources/gnulib/gnulib/lib/stdint_.h,v retrieving revision

stdint module on SGI

2006-06-21 Thread Mark D. Baushke
Hi Bruno, The following two patches take a closer step toward making things work under the default c89 compiler on SGI boxes. All files that #include stdint.h still get warnings like this one: cc-1035 cc: WARNING File = /usr/include/stdint.h, Line = 5 #error directive: This header file is to

stdint vs cycle-check.h

2006-06-20 Thread Mark D. Baushke
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Bruno Jim, A system without an stdint.h file, will have the stdint_.h turned into a valid one. However, the HAVE_STDINT_H will not be defined. This causes problems with files like cycle-check.h which does: # if HAVE_STDINT_H # include stdint.h

Re: stdint vs cycle-check.h

2006-06-20 Thread Mark D. Baushke
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Paul Eggert [EMAIL PROTECTED] writes: Mark D. Baushke [EMAIL PROTECTED] writes: is it desirable to make those modules depend on stdint.m4 and avoid the HAVE_STDINT_H macro? Yes, I think so, in the long run. But in the short run, stdint.m4

Re: stdint vs cycle-check.h

2006-06-20 Thread Mark D. Baushke
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Paul Eggert [EMAIL PROTECTED] writes: Mark D. Baushke [EMAIL PROTECTED] writes: The HAVE_STDINT_H is defined, even though it is useless and there is an stdint.h which is generated and includes the useless SGI version and generates warnings

alloca_.h suggested change

2006-06-19 Thread Mark D. Baushke
On FreeBSD 6.1, the file /usr/include/stdlib.h has the following on lines 219 through 233 inclusive: /* * The alloca() function can't be implemented in C, and on some * platforms it can't be implemented at all as a callable function. * The GNU C compiler provides a built-in alloca() which we

Re: stdint module rewrite (was: Re: Build CVS (TRUNK) failed.)

2006-06-16 Thread Mark D. Baushke
compilers will ignore illegal preprocessor expressions in a '#if 0' block. So, should some other expression for '# if 32' be generated? -- Mark Bruno Haible [EMAIL PROTECTED] writes: Mark D. Baushke wrote: This rewrite works for FreeBSD 4.2, FreeBSD 5.2, FreeBSD 6.1. After

Re: stdint module rewrite (was: Re: Build CVS (TRUNK) failed.)

2006-06-16 Thread Mark D. Baushke
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Bruno Haible [EMAIL PROTECTED] writes: Hi Mark, I see the following: #if 0 # ifndef UINT_FAST16_MAX # if 32 # define UINT_FAST16_MAX (((1 ( - 1)) - 1) * 2 + 1) # else # define UINT_FAST16_MAX (((1UL ( - 1)) - 1) * 2 +

Re: [Cvs-dev] Re: [Cvs-test-results] Build CVS (TRUNK) failed.

2006-06-15 Thread Mark D. Baushke
Hi Folks, The CVS project found a need to add the following patch to lib/strtoimax.c in order to get compilation on Windows to work. The basic problem is that there is an __int64 type and three conversion functions: char * _i64toa(__int64, char *, int); char * _ui64toa(unsigned __int64, char *,

Re: [Cvs-dev] Re: [Cvs-test-results] Build CVS (TRUNK) failed.

2006-06-15 Thread Mark D. Baushke
[Sorry about sending a reverse patch the first time around...] Hi Folks, The CVS project found a need to add the following patch to lib/strtoimax.c in order to get compilation on Windows to work. The basic problem is that there is an __int64 type and three conversion functions: char *

Re: [Cvs-dev] Re: [Cvs-test-results] Build CVS (TRUNK) failed.

2006-06-15 Thread Mark D. Baushke
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Paul Eggert [EMAIL PROTECTED] writes: I'm getting a bit lost with info about both stdint.h versus inttypes.h, but does the following patch fix the problem? This does not fix the problem as the AC_CACHE_VAL(gl_cvs_header_stdint_h) is interfering

Re: [Cvs-dev] Re: [Cvs-test-results] Build CVS (TRUNK) failed.

2006-06-11 Thread Mark D. Baushke
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Paul Eggert [EMAIL PROTECTED] writes: Derek R. Price [EMAIL PROTECTED] writes: The current test that checks for the existence of stdint.h isn't sufficient on SGI when using the compiler in (its default?) C89 mode, because the SGI compiler

Re: PATCH to stdint_.h for OpenBSD Sparc64

2006-03-27 Thread Mark D. Baushke
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mark D. Baushke [EMAIL PROTECTED] writes: Hi Folks, For this is the bug report: http://savannah.nongnu.org/bugs/?func=detailitemitem_id=15040 CVS needs the following patch applied to GNULIB/lib/stdlib_.h FYI. I have applied this patch

GNULIB stdint_.h vs OpenBSD Sparc64

2006-03-18 Thread Mark D. Baushke
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Greetings, It appears that the GNULIB stdint_h.m4 (serial 5) which CVS 1.12 (trunk) is using is not properly protecting against the Exact-width integer types being present in machine/int_types.h which may be included from sys/types.h among other

Re: [bug-gnulib] gnulib/gnulib-tool shell quoting problem for Solaris /bin/sh

2006-01-25 Thread Mark D. Baushke
2006-01-25 Bruno Haible [EMAIL PROTECTED] * gnulib-tool (func_import): Use trap : instead of trap - to get rid of a trap command. For Solaris sh. Reported by Mark D. Baushke [EMAIL PROTECTED]. *** gnulib-tool 24 Jan 2006 19:18:45 - 1.104 --- gnulib-tool 25 Jan

openat-priv.h needs intprops.h

2006-01-24 Thread Mark D. Baushke
Hi Jim, The openat provided file openat-priv.h tries to include intprops.h but that file is not listed in the modules/openat file as a dependency. The following patch seems to fix this problem for me. There is probably a better way to do it, but I will leave that to you. Thanks!

Re: new module lib-ignore; new section build_lib in MODULES.html

2006-01-18 Thread Mark D. Baushke
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Paul Eggert [EMAIL PROTECTED] writes: Quoting Bruno Haible [EMAIL PROTECTED]: It appears that -Xlinker is supported only by gcc, and -Wl by other compilers too? Sorry, I had never heard of -Wl. Do you know whether GCC has supported -Wl

Re: [bug-gnulib] Re: stdint_.h vs intmax_t uintmax_t

2006-01-09 Thread Mark D. Baushke
not declare. (uintmax_t) [defined uintmax_t]: Do not declare. (SIZE_MAX) [defined SIZE_MAX]: Do not define. This works around a problem if intmax_t.m4 and/or uintmax_t.m4 and/or size_max.m4 are also used. Problem reported by Mark D. Baushke. Thanks for applying this patch

Re: Use of bison

2005-12-30 Thread Mark D. Baushke
Hi Eric, Francesco Montorsi on 12/27/2005 11:42 AM wrote: PS: I've recently installed SuSE and I've found that the configure script of coreutils doesn't check for 'bison' presence: on that distro, it was missing and it gave me problems later with make. I think adding a check for 'bison'

Re: stdint_.h vs intmax_t uintmax_t

2005-11-27 Thread Mark D. Baushke
Hi Paul, Did Bruno ever give you his opinion for this fix? Thanks, -- Mark Paul Eggert [EMAIL PROTECTED] writes: Mark D. Baushke [EMAIL PROTECTED] writes: There is one remaining interaction with stdint_.h and config.h which arises from m4/size_max.m4 % grep SIZE_MAX

Re: stdint_.h vs intmax_t uintmax_t

2005-11-15 Thread Mark D. Baushke
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Paul Eggert [EMAIL PROTECTED] writes: Mark D. Baushke [EMAIL PROTECTED] writes: There is one remaining interaction with stdint_.h and config.h which arises from m4/size_max.m4 % grep SIZE_MAX config.h config.h:#define SIZE_MAX

stdint_.h vs intmax_t uintmax_t

2005-11-14 Thread Mark D. Baushke
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I have run into a quirk of GNULIB building CVS on a FreeBSD 4.2 host. It seems that CVS is using m4/intmax.m4 which generate these lines into the config.h file: /* Define if you have the 'uintmax_t' type in stdint.h or inttypes.h. */ /* The size of

Re: lgpl compatible files archive?

2005-07-04 Thread Mark D. Baushke
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Patrice Dumas [EMAIL PROTECTED] writes: Simon Josefsson [EMAIL PROTECTED] wrote: I found it helped to attack the problem one module at a time, carefully considering the details. Exactly which modules do you need which are under the GPL in