-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?
>
-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 s
Thanks,
-- 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 qu
-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; exp
-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 || !HAV
-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:
> >
-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_
-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
-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_CPPFLA
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Paul,
I believe that the new openat module needs to depend on lchown.
I updated CVS and it didn't pull in the lchown module which lead
to a build-break on BSDI BSD/OS.
Index: modules/openat
=
t;[EMAIL PROTECTED]> writes:
>
> - Original Message -
> From: "Paul Eggert" <[EMAIL PROTECTED]>
> To: "Dennis Jones" <[EMAIL PROTECTED]>
> Cc: ; "Mark D. Baushke" <[EMAIL PROTECTED]>;
>
> Sent: Monday, August 21, 2006 9
-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
preprocesso
-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
Hi Ralf,
Ralf Wildenhues <[EMAIL PROTECTED]> writes:
> Hello Mark, everyone,
>
> I'm all for making gnulib-tool portable in practice (and not only in
> theory), if only to avoid further such bug reports; but this patch
> definitely changes the semantics (the `!' "binds" higher than `||',
> if on
Paul Eggert <[EMAIL PROTECTED]> writes:
> "Mark D. Baushke" <[EMAIL PROTECTED]> writes:
>
> >../gnulib/gnulib-tool --update
> >
> > command from the hello-2.1.91 directory on a Solaris 9 box yeilds a
> > syntax error:
> >
> >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Karl,
Of possible interest to GNULIB maintainers, running the
../gnulib/gnulib-tool --update
command from the hello-2.1.91 directory on a Solaris 9 box yeilds a
syntax error:
../gnulib/gnulib-tool: syntax error at line 634: `}' unexpected
U
-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 lik
-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
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
=
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"
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: /sources/gnulib/gnulib/modules/cycle-check,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Paul,
Paul Eggert <[EMAIL PROTECTED]> writes:
> Thanks for the bug report. How about this patch instead?
> It includes @FULL_PATH_STDINT_H@ first, before ;
> this should be a bit safer than including @FULL_PATH_STDINT_H@ twice.
Your proposed pat
[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 ' from inside of .
-- Mar
-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 actually
does the #include of for us. This is bad.
On MacOS
-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 has the types except the *
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Martin,
I have Installed Bruno's latest GNULIB changes into the CVS sources.
If there are still problems, it would be good to know what you are
seeing out of the 'configure' command... both the output and selected
parts of the config.log file.
-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 such
-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 th
Bruno Haible <[EMAIL PROTECTED]> writes:
> Mark D. Baushke wrote:
> > In fact, the SGI
> > IRIX 5.3 c99 compiler does have do
> > this. When c89 is used, the file is not included,
> > but all of the needed types are defined.
>
> Let me try to recap it
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 b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Marti,
I have committed a change to CVS top-of-tree that may help you.
Does your system protect against duplication of types out
of ?
-- Mark
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.3 (FreeBSD)
iD8DBQFEnD0ZCg7APGsDnFERAjXSAJ9
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
their
with just
. 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 1.17
diff -u -p -r1.17 s
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 still get warnings like this one:
cc-1035 cc: WARNING File = /usr/include/stdint.h, Line = 5
#error directive: This header file is to be used
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Larry Jones <[EMAIL PROTECTED]> writes:
> 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
>
-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
-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,
-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
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 ca
included from the generated stdint.h file.
An alternative approach would be to change how gl_FULL_HEADER_PATH
works, in which case the define geneated for the confdefs.h file will
need to avoid duplication of the angle brackets.
Thanks,
-- Mark
2006-06-19 Mark D. Baushke <[EM
-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 (((1U
UINT64_MAX
# else
# define UINT_FAST16_MAX UINT32_MAX
# endif
#endif
I am not at all certain that all compilers will ignore illegal
preprocessor expressions in a '#if 0' block. So, should some
other expression for '# if < 32' be generated?
-- Mark
Bruno Haible
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul Eggert <[EMAIL PROTECTED]> writes:
> I'm getting a bit lost with info about both versus
> , 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 with the test due
[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 * _i64toa(_
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 *,
-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 isn't
> > sufficient on SGI when using the compiler in (its default?) C89 mode,
> > because the SGI compil
TECTED]>
>
> * regcomp.c (init_dfa): Don't use wchar_t or wctype_t if RE_ENABLE_I18N
> is not defined. Problem reported by Mark D. Baushke via Derek R. Price.
>
> --- lib/regcomp.c 10 Apr 2006 19:15:08 - 1.7
> +++ lib/regcomp.c 13 Apr 2006 22:11:
-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=detailitem&item_id=15040>
> CVS needs the following patch applied to GNULIB/lib/stdl
ed by both
and .
Alex has verified that the patch below fixes his problem building CVS on
his OpenBSD box.
Thanks,
-- Mark
2006-03-26 Mark D. Baushke <[EMAIL PROTECTED]>
* stdint_.h: Protect against OpenBSD integer types from
.
-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 which may be included from
among other places.
This is the full bug repor
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bruno Haible <[EMAIL PROTECTED]> writes:
> Mark D. Baushke wrote:
> > > I'm trying this patch. Does it work for you?
> >
> > Yes.
>
> Thanks. I've committed the fix.
>
> > | If argume
standard:
http://www.opengroup.org/onlinepubs/009695399/utilities/trap.html#tag_04_146
So, I will let you folks determine the fix to apply.
Thank you,
-- Mark
>
>
> 2006-01-25 Bruno Haible <[EMAIL PROTECTED]>
>
> * gnulib-tool (func_import): Use "trap :&
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!
Greetings,
While trying to run ../gnulib/gnulib-tool on a Solaris 9 system
I have run into problems when /bin/sh is used.
The workaround appears to be to do
/bin/bash ../gnulib/gnulib-tool --import
which seems to avoid the problem (/bin/bash is a 2.05 version).
I am getting these two erro
-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
> supp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ben Pfaff <[EMAIL PROTECTED]> writes:
> I don't understand why ((size_t)-1) is considered C99 specific.
You are correct. It is not C99 specific. I was quoting the C99 standard
which Bruno referenced to be sure everyone was on the same page because
I
>
> > * lib/stdint_.h (intmax_t) [defined intmax_t]: Do 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
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bruno Haible <[EMAIL PROTECTED]> writes:
> Mark D. Baushke wrote on 2005-11-15:
> > it would be more portable to use this:
> >
> > #ifndef SIZE_MAX
> > # define SIZE_MAX ((size_t)-1)
> > #endif
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 'biso
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
&g
-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
> >
>
ntmax_t]: Do not declare.
> (uintmax_t) [defined uintmax_t]: Do not declare.
> This works around a problem if intmax_t.m4 and/or uintmax_t.m4
> are also used. Problem reported by Mark D. Baushke.
>
> --- stdint_.h.~1.7.~ 2005-05-23 03:22:39.0 -0700
> +++ std
-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 or . */
/* The size of a `intmax_t', as co
This compilation problem of lib/cannon-host.c on FreeBSD 4.10-BETA or
4.11 results when lib/getaddrinfo.h does not do a #include
before the #include ...
The change was between 1.5 and 1.6 of
/cvsroot/gnulib/gnulib/lib/getaddrinfo.h,v with the following
log message:
2005-10-01 Simon Josefsson
-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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Many thanks to Paul Eggert <[EMAIL PROTECTED]> who committed the patch
to gl_FUNC_MMAP_ANON to check for message, not for MAP_ANON.
I have updated the feature branch of CVS on cvshome.org to use the new
version of the m4/mmap-anon.m4 file.
E
Hi Folks,
I have not seen any discussion or commit on this patch suggested by
Moriyoshi Koizumi <[EMAIL PROTECTED]> (originally submitted to the
bug-cvs list and forwarded by me) which allows MacOS X (10.2.x and
10.3.x) to properly be able to '#define HAVE_MAP_ANONYMOUS 1' along with
'#define MAP_
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Moriyoshi Koizumi <[EMAIL PROTECTED]> writes:
> Hmm, seems the attachments were stripped. I placed them on
>
> http://www.voltex.jp/patches/cvs-1.12.12-mmap-anon-20050424.patch.diff.gz
> http://www.voltex.jp/patches/cvs-1.12.12-pam-header-20050424-pa
69 matches
Mail list logo
