The next test for me to get working is options.at.
The issue is that the VMS UID is 32 bits with the GID encoded in it,
unless special mapping is in place.
So to encode the UID in uid_to_chars(), the value needed is (uid >> 16)
unless the special mapping is in place, in which case the UID wou
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Bruno Haible on 3/6/2008 2:41 PM:
| However, I would prefer API changes as follows:
| - freadahead keeps its signature but returns the total buffered bytes
count.
| - freadptr is changed to also return the size of the buffer.
|
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[Adding the Austin Group]
According to Bruno Haible on 3/6/2008 3:46 PM:
| Do you know the wording that the newest POSIX has about this?
I think that Interp 002 is incomplete in the face of ungetc.
http://www.opengroup.org/austin/interps/uploads/40
Bruno Haible clisp.org> writes:
>
> Eric Blake wrote:
> > Newlib has two bugs - first, fflush is failing to discard ungetc data when
> > changing the underlying fd offset.
>
> This bug is common to all BSD and AT&T Unix derived implementations. For BSD
> systems, I'm committing this fix. For AT
Bruno Haible clisp.org> writes:
>
> Eric Blake wrote on Saturday:
> > Newlib has two bugs - first, fflush is failing to discard ungetc data when
> > changing the underlying fd offset.
>
> Do you know the wording that the newest POSIX has about this?
The ungetc wording is unchanged from POSIX 2
Eric Blake wrote:
> Second, ftell is improperly calling
> fflush under the hood, which when coupled with the first bug, results in a
> confused file offset, but even when the first bug is fixed, loses data
> contrary to POSIX.
Can you please document it in gnulib/doc/?
Bruno
Eric Blake wrote:
> Newlib has two bugs - first, fflush is failing to discard ungetc data when
> changing the underlying fd offset.
This bug is common to all BSD and AT&T Unix derived implementations. For BSD
systems, I'm committing this fix. For AT&T Unix derived implementations, I
don't see an e
Bruno Haible clisp.org> writes:
> This fixes it. Committed.
>
> 2008-03-06 Bruno Haible clisp.org>
>
> * modules/fseeko (Dependencies): Add extensions.
> * m4/fseeko.m4 (gl_FUNC_FSEEKO): Require AC_USE_SYSTEM_EXTENSIONS.
> Needed on glibc systems.
And for symmetry, I commi
Yoann Vandoorselaere wrote:
> Reading the documentation, I can see:
>
> "Also sets PTHREAD_CC to any special C compiler that is needed for
> multi-threaded programs (defaults to the value of CC otherwise). (This
> is necessary on AIX to use the special cc_r compiler alias.) "
I don't think that i
Yoann,
> > Neither -pthread nor -D_REENTRANT is a requirement for building
> > multithreaded
> > programs on Linux with glibc.
>
> Can you confirm the validity of this statement for the old linuxthread
> implementation?
For the things that I have tested, yes. I'm doing most of my development on
Eric Blake wrote on Saturday:
> Newlib has two bugs - first, fflush is failing to discard ungetc data when
> changing the underlying fd offset.
Do you know the wording that the newest POSIX has about this?
The following test program, run on various platforms, gives unconclusive
results.
Testing the 'fflush' module on a Linux/x86 systems, I got this warning:
test-fflush.c: Dans la fonction « main »:
test-fflush.c:103: Warnung: implicit declaration of function `fseeko'
This fixes it. Committed.
2008-03-06 Bruno Haible <[EMAIL PROTECTED]>
* modules/fseeko (Dependencies
Eric Blake wrote:
> After more thought, I think we need an API change to freadahead, to add a
> flag parameter. When the flag is 0, return the number of bytes available
> in the current buffer that freadptr would return. When the flag is
> non-zero, return the number of bytes available prior to t
Le jeudi 06 mars 2008 à 14:10 +0100, Bruno Haible a écrit :
> Simon Josefsson wrote:
> > Hm. lock.m4 contains:
> >
> > # For using :
> > case "$host_os" in
> > osf*)
> > # On OSF/1, the compiler needs the flag -D_REENTRANT so that it
> > # groks . cc also understand
Le mercredi 05 mars 2008 à 18:06 +0100, Bruno Haible a écrit :
> Yoann Vandoorselaere asked:
> > Is it expected that the lock module does not set the -pthread CFLAGS
> > when compiling with GCC on a Linux architecture?
>
> Yes it is normal. The module description has this, and gnulib-tool echoes
() Bruno Haible <[EMAIL PROTECTED]>
() Thu, 6 Mar 2008 19:51:36 +0100
There's a particular texinfo command for this: @w{}.
Cool.
thi
Thien-Thi Nguyen wrote:
> to avoid the resulting info file displaying the email
> address at end-of-paragraph split accross two lines,
> (ugly IMHO).
There's a particular texinfo command for this: @w{}.
2008-03-06 Bruno Haible <[EMAIL PROTECTED]>
* doc/gnulib-tool.texi (@nosuchmoduleno
libgnupdf now also uses gnulib.
*** users.txt.orig 2008-03-06 19:40:09.0 +0100
--- users.txt 2008-03-06 19:34:19.0 +0100
***
*** 26,31
--- 26,32
inetutils http://cvs.sv.gnu.org/viewcvs/inetutils/inetutils/
jwhois http://cvs.sv.gnu
() Bruno Haible <[EMAIL PROTECTED]>
() Thu, 6 Mar 2008 18:46:47 +0100
[...] additional paragraph break.
Drat, i knew i should have explained that. I added it
to avoid the resulting info file displaying the email
address at end-of-paragraph split accross two lines,
(ugly IMHO). Ah well, a lit
Thien-Thi Nguyen wrote:
> Below is a patch.
Thank you. I applied it, except for the additional paragraph break.
2008-03-06 Thien-Thi Nguyen <[EMAIL PROTECTED]>
* doc/gnulib-tool.texi (@nosuchmodulenote): New macro.
(Header File Substitutes, Function Substitutes,
Glibc
Bruno Haible <[EMAIL PROTECTED]> writes:
> There's also a program 'ud2cd' which converts a unified diff to
> a context diff a posteriori, and 'cd2ud' which converts a
> context diff to a unified diff. [1]
Emacs diff-mode can also convert between unified and context
diffs.
--
Ben Pfaff
http://be
() Bruno Haible <[EMAIL PROTECTED]>
() Thu, 6 Mar 2008 15:04:12 +0100
Hmm, I would prefer to copy this paragraph to the beginning of
each of the 4 header file / function substitutes chapters.
Without this paragraph, people did not understand what the
notation means.
Sounds reasonable.
Eric Blake wrote:
> Either form works for either case. But for readability purposes,
> documentation patches tend to modify sentences, and it is nice to see the
> before and after effect of a partial sentence without having lots of lines
> in between. And code patches tend to modify logical block
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Thien-Thi Nguyen on 3/6/2008 7:13 AM:
| So i take it context diff is preferred for code patches?
Either form works for either case. But for readability purposes,
documentation patches tend to modify sentences, and it is nice to see the
() Bruno Haible <[EMAIL PROTECTED]>
() Thu, 6 Mar 2008 15:01:18 +0100
Thanks, I've applied a slightly different one. (I don't often
read about "registering with the VCS". "check in" is the more
common term. Also, when you say "marked as ignorable (for
example, by adding them to @file{.
Hi,
Thien-Thi Nguyen wrote:
> Presently, the blurb:
>
> |The notation ``Gnulib module: ---'' means ...
>
> is in @node "Function Substitutes", which comes after usage of that notation
> in the preceding @node "Header File Substitutes".
You're right, this is not so good.
> I think it would good
Hi,
Thien-Thi Nguyen wrote:
> A tiny change.
Thanks, I've applied a slightly different one. (I don't often read about
"registering with the VCS". "check in" is the more common term. Also,
when you say "marked as ignorable (for example, by adding them to
@file{.cvsignore}" - are there other ways t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Bruno Haible on 3/6/2008 6:49 AM:
| When I write a piece of C code (INCLUDES or FUNCTION-BODY), in 99% of
the cases
| I want brackets to denote array dimensions or array indices. I don't
want them
| to expand to nothing.
|
| You say that
Hello Ralf,
I wrote:
> > AC_TRY_COMPILE has a more mnemonic name (it follows the
> > usual rule to use an English verb to as a function/macro name)
> > and simpler quoting rules than AC_COMPILE_IFELSE.
Also, AC_COMPILE_IFELSE presents a pitfall: One is tempted to write
AC_COMPILE_IFELSE([
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Eric Blake on 2/29/2008 6:36 AM:
| According to Bruno Haible on 2/29/2008 3:49 AM:
| | With strace you can see that there is only a single read() from the file
| | descriptor. I.e. at the moment when freadahead() returns 0, it is only
| |
Simon Josefsson wrote:
> Hm. lock.m4 contains:
>
> # For using :
> case "$host_os" in
> osf*)
> # On OSF/1, the compiler needs the flag -D_REENTRANT so that it
> # groks . cc also understands the flag -pthread, but
> # we don't use it because 1. gcc-2.95 does
Presently, the blurb:
|The notation ``Gnulib module: ---'' means that Gnulib does not provide a
|module providing a substitute for the function. When the list
|``Portability problems not fixed by Gnulib'' is empty, such a module is
|not needed: No portability problems are known. Otherwise, it in
A tiny change. (Is there a more preferred format for patches?)
thi
__
doc/gnulib-tool.texi |7 ---
1 files changed, 4 insertions(+), 3 deletions(-)
diff --git a/doc/gnulib-tool.texi b/doc/gnulib-tool.texi
index 9d9ec56..f5a66e0 10064
Simon Josefsson wrote:
> + * doc/gnulib.texi (__func__): Section renamed to func.
> + * doc/gnulib.texi (__func__): Document __func__ module.
I moved out this documentation to a separate file. This will make it easier
in the future to do reorganizations of the manual.
Bruno
2008-03-06
Hello Bruno, Simon,
* Bruno Haible wrote on Thu, Mar 06, 2008 at 12:47:31PM CET:
> Simon Josefsson wrote:
> > I find AC_TRY_COMPILE slightly easier to work with
> > than AC_COMPILE_IFELSE so perhaps we could argue that it should be
> > non-deprecated, unless there were a strong reason to deprecate
Simon Josefsson wrote:
> I find AC_TRY_COMPILE slightly easier to work with
> than AC_COMPILE_IFELSE so perhaps we could argue that it should be
> non-deprecated, unless there were a strong reason to deprecate it.
Likewise for me. AC_TRY_COMPILE has a more mnemonic name (it follows the
usual rule
Simon Josefsson <[EMAIL PROTECTED]> writes:
> Jim Meyering <[EMAIL PROTECTED]> writes:
>
>> Simon Josefsson <[EMAIL PROTECTED]> wrote:
>>> Eric Blake <[EMAIL PROTECTED]> writes:
>> ...
Maybe it's just me, but I hate typing _ (it involves a shift key and some
coordination). Can we name i
So when importing func it into one project, it didn't work because I
used 'LGPL' as license for the module... I'm changing it to 'unlimited'.
/Simon
>From 764a748536df4b41726d4aae341a159de32a6552 Mon Sep 17 00:00:00 2001
From: Simon Josefsson <[EMAIL PROTECTED]>
Date: Thu, 6 Mar 2008 12:06:19 +01
Jim Meyering <[EMAIL PROTECTED]> writes:
> Simon Josefsson <[EMAIL PROTECTED]> wrote:
>> Eric Blake <[EMAIL PROTECTED]> writes:
> ...
>>> Maybe it's just me, but I hate typing _ (it involves a shift key and some
>>> coordination). Can we name it modules/func rather than modules/__func__?
>
> Hi S
Simon Josefsson <[EMAIL PROTECTED]> wrote:
> Eric Blake <[EMAIL PROTECTED]> writes:
...
>> Maybe it's just me, but I hate typing _ (it involves a shift key and some
>> coordination). Can we name it modules/func rather than modules/__func__?
Hi Simon,
> Ouch, I have already pushed it. Should we
Eric Blake <[EMAIL PROTECTED]> writes:
> According to Simon Josefsson on 3/4/2008 7:39 AM:
> |
> | However, what do you think about this?
> |
> | /Simon
> |
> |>From 232f8a7255f8addd9724156d7d245b51a7feb72e Mon Sep 17 00:00:00 2001
> | From: Simon Josefsson <[EMAIL PROTECTED]>
> | Date: Tue, 4 Mar
Bruno Haible <[EMAIL PROTECTED]> writes:
> Simon Josefsson wrote:
>> However, what do you think about this?
>
> Looks all fine to me.
Thanks, installed.
>> Hm. As far as I can tell, AC_CHECK_DECLS is not restricted to
>> functions, the autoconf manual says "If SYMBOL (a function or a
>> variabl
Bruno Haible <[EMAIL PROTECTED]> writes:
>> Using -pthread allow option like -D_REENTRANT to be defined when
>> compiling Gnulib, which sound like a requirement if the program using
>> Gnulib is multithreaded.
>
> Neither -pthread nor -D_REENTRANT is a requirement for building multithreaded
> prog
[EMAIL PROTECTED] (Karl Berry) writes:
> got a 'TeX capacity exceeded, sorry [save size=5000].' error.
> Increasing 'save_size' in texmf.cnf solved it.
>
> FWIW, I increased it to 5 for the next TeX Live release. I don't recall
> exactly why, but maybe because I ran into exactly the
44 matches
Mail list logo
