Re: stdint vs cycle-check.h

2006-06-20 Thread Paul Eggert
[EMAIL PROTECTED] (Larry Jones) writes: >> # if HAVE_INTTYPES_H >> # include >> # endif >> # if HAVE_STDINT_H >> # include >> # endif > > I don't understand that recommendation. Since is supposed > to #include , why isn't the recommendation: As I recall, it's for some older hosts where doe

Re: stdint vs cycle-check.h

2006-06-20 Thread Larry Jones
Paul Eggert writes: > > For cycle-check.h I'd think this wouldn't be a problem, since > cycle-check.h uses this Autoconf-recommended sequence: > > # if HAVE_INTTYPES_H > # include > # endif > # if HAVE_STDINT_H > # include > # endif I don't understand that recommendation. Since is supposed

Re: stdint vs cycle-check.h

2006-06-20 Thread Paul Eggert
"Mark D. Baushke" <[EMAIL PROTECTED]> writes: > and similar code in the generated stdint.h file, would be sufficient to > make things work... in other words, leave out all of the hacks as to > which OS may or may not define those files and just test for them. That would be fine with me. Perhaps

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 > > generat

Re: stdint vs cycle-check.h

2006-06-20 Thread Paul Eggert
"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 for everything because of the include of Ah, OK, so the problem is in the combinatio

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 ru

system module?

2006-06-20 Thread Eric Blake
Andreas Buening reported that OS/2 violates the CX shading in POSIX 2001 in that the return value of system() is not parseable with WEXITSTATUS: http://www.nabble.com/Re%3A-sysval-and-doc-fixes--was%3A-GNU-M4-1.4.4b-released- %28beta-release%29--t1815393.html#a4961536 In short, on OS/2, waitpid(

Re: stdint vs cycle-check.h

2006-06-20 Thread Paul Eggert
"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 is not yet reliable enough (as you're finding out with SGI), and some packages don't wa

Re: [Bug-tar] missing exit_status in tar-1.15.91

2006-06-20 Thread Paul Eggert
Denis Excoffier <[EMAIL PROTECTED]> writes: > openat.c: In function 'rpl_openat': > openat.c:60: warning: 'mode_t' is promoted to 'int' when passed through '...' > openat.c:60: warning: (so you should pass 'int' not 'mode_t' to 'va_arg') > openat.c:60: note: if this code is reached, the program wi

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 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 # endif Similar

Re: [bug-gnulib] Openat and localcharset issues on Darwin

2006-06-20 Thread Bruno Haible
Sergey Poznyakoff wrote: > /usr/bin/ld: warning multiple definitions of symbol _locale_charset > ../lib/libtar.a(localcharset.o) definition of _locale_charset in section > (__TEXT,__text) > /usr/lib/libiconv.dylib(localcharset.o) definition of _locale_charset You can ignore this warning. The /usr

Re: [bug-gnulib] gettext: -lintl if necessary

2006-06-20 Thread Bruno Haible
Ralf Wildenhues wrote: > I don't dispute > either that the module should be put into gnulib. However, I'd like to > avoid that gnulib ends up just dumping all needed libraries into one > variable, forcing gnulib users to bite and link against them all or use > $as_needed (whatever it's called): th

Re: Openat and localcharset issues on Darwin

2006-06-20 Thread Jim Meyering
"Sergey Poznyakoff" <[EMAIL PROTECTED]> wrote: > Hello, > > The following gnulib-related message was obtained while compiling GNU > tar on powerpc-apple-darwin8.6.0 with GCC 4.1.1 and native ld: > > openat.c: In function 'rpl_openat': > openat.c:60: warning: 'mode_t' is promoted to 'int' when passe

Openat and localcharset issues on Darwin

2006-06-20 Thread Sergey Poznyakoff
Hello, The following gnulib-related message was obtained while compiling GNU tar on powerpc-apple-darwin8.6.0 with GCC 4.1.1 and native ld: openat.c: In function 'rpl_openat': openat.c:60: warning: 'mode_t' is promoted to 'int' when passed through '...' openat.c:60: warning: (so you should pass '