> Fine by me.
I also changed doc/Makefile to run makeinfo in an English locale, regardless
of the user's locale (otherwise, in some versions of makeinfo, it generates
localized some German sentences in the doc if the user is in a German locale).
2008-08-26 Bruno Haible <[EMAIL PROTECTED]>
Eric Blake wrote:
> Is this the sort of patch better suited to an upstream fix in install.texi
> in autoconf (ie. fold the @firstparagraphindent into the .texi file,
> rather than creating a temporary file in the gnulib Makefile rule)?
I don't think so: The install.texi file is also included by th
Karl Berry wrote:
> ! { echo '@firstparagraphindent insert'; cat $<; } > tmp.texi
> ! -$(MAKEINFO) --plaintext --no-warn tmp.texi > $@
> ! rm -f tmp.texi
>
> Fine by me.
Applied.
On Sun, Aug 24, 2008 at 12:29:06PM +0200, Bruno Haible wrote:
> > +dnl On Solaris 8, wcwidth(0x2022) (BULLET) returns -1.
>
> This is not the case for me:
I'm sorry. In my case it also gives 2, not -1. (I forgot to call setlocale
in the new test program, oops). New patch attached.
> Which lo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Bruno Haible on 8/25/2008 5:24 PM:
>
> Yes, thanks. This gives us the freedom to discuss the formatting details
> of this file :-)
>
> Currently, 'makeinfo' produces an INSTALL file which has the first paragraph
> in every section uninde
! { echo '@firstparagraphindent insert'; cat $<; } > tmp.texi
! -$(MAKEINFO) --plaintext --no-warn tmp.texi > $@
! rm -f tmp.texi
Fine by me.
Karl Berry wrote:
> will (manually) generate INSTALL from install.texi via a rule in
> gnulib/doc/Makefile.
>
> Hope that suits. I couldn't think of a better way.
Yes, thanks. This gives us the freedom to discuss the formatting details
of this file :-)
Currently, 'makeinfo' produces an INSTALL
Well, the MODULES.html that was committed on 2008-08-21, with commit message
There should have been checkins since then.
I made more fixes to my stupid cron. Fingers crossed for tonight ...
Sorry,
k
Hi Karl,
On 2008-08-14 you wrote:
> Karl, I think that using the option --git-urls instead of --cvs-urls
> should
> fix this.
>
> Thanks. I changed the cron. We'll see what happens tonight ...
Well, the MODULES.html that was committed on 2008-08-21, with commit message
"autoupdate", s
grabbing upstream changes from Autoconf to gnulib's doc/INSTALL?
Since, as you mentioned, autoconf no longer provides INSTALL in the
source repo, I committed install.texi to gnulib, sync against that, and
will (manually) generate INSTALL from install.texi via a rule in
gnulib/doc/Makefile.
Bruno Haible wrote:
Yoann Vandoorselaere wrote:
- it does not need to see a thread-aware errno,
hence it does not need to compile with THREADCPPFLAGS.
Not using a thread-aware errno from an application that indirectly use
thread through a library (which use thread-aware errno). Are you
comple
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Elbert Pol on 8/13/2008 12:17 PM:
> Hello Eric,
[please don't top-post]
> > However, I'm still interested in seeing what this does when libsigsegv is
> > not present (you can use './configure --without-libsigsegv-prefix' to
> > rebuild m
Hi,
Bruno Haible <[EMAIL PROTECTED]> writes:
> Ludovic Courtès wrote:
>> I'm trying to fix a portability bug related to `strftime(3)' [0]. The
>> `strftime' module doesn't provide `strftime ()' as one would expect
>
> And the gnulib doc is incorrect. Fixing it:
In addition, it doesn't mention a
Hi Simon,
Simon Josefsson <[EMAIL PROTECTED]> writes:
> That doesn't make much sense to me. IMHO, the 'strftime' module should
> provide a 'strftime' function.
Agreed.
IIUC, this could be achieved by compiling the file twice: once with
"#define my_strftime" and once without.
> Where is 'nstrf
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Bruno Haible on 8/25/2008 4:11 AM:
>
> Since -isystem is some burden on the gnulib user (not a big one, but anyway)
> I propose to add
>#ifdef __GNUC__
># pragma GCC system_header
>#endif
> to all gnulib headers that use @[EMA
Simon Josefsson <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] (Ludovic Courtès) writes:
>
>> The `strftime' module doesn't provide `strftime ()' as one would
>> expect but instead provides `nstrftime ()'
>
> That doesn't make much sense to me. IMHO, the 'strftime' module should
> provide a 'strft
Hi Bruno,
Le lundi 25 août 2008 à 11:46 +0200, Bruno Haible a écrit :
> Yoann Vandoorselaere wrote:
> > > - it does not need to see a thread-aware errno,
> > > hence it does not need to compile with THREADCPPFLAGS.
> >
> > Not using a thread-aware errno from an application that indirectly use
>
On Mon, 25 Aug 2008, Bruno Haible wrote:
Paolo Bonzini wrote:
You can put "#pragma GCC system_header" in the gnulib files.
However, this pragma not only affects warnings, it also causes __STDC__ to
evaluate to 0 in such a file, on some platforms (those which define
STDC_0_IN_SYSTEM_HEADERS, n
Ludovic Courtès wrote:
> I'm trying to fix a portability bug related to `strftime(3)' [0]. The
> `strftime' module doesn't provide `strftime ()' as one would expect
And the gnulib doc is incorrect. Fixing it:
2008-08-25 Bruno Haible <[EMAIL PROTECTED]>
* doc/posix-functions/strftime.
Paolo Bonzini wrote:
> You can put "#pragma GCC system_header" in the gnulib files.
However, this pragma not only affects warnings, it also causes __STDC__ to
evaluate to 0 in such a file, on some platforms (those which define
STDC_0_IN_SYSTEM_HEADERS, namely Solaris and Interix).
Incidentally, t
[EMAIL PROTECTED] (Ludovic Courtès) writes:
> The `strftime' module doesn't provide `strftime ()' as one would
> expect but instead provides `nstrftime ()'
That doesn't make much sense to me. IMHO, the 'strftime' module should
provide a 'strftime' function.
Where is 'nstrftime' defined as a GNU
Yoann Vandoorselaere wrote:
> > - it does not need to see a thread-aware errno,
> > hence it does not need to compile with THREADCPPFLAGS.
>
> Not using a thread-aware errno from an application that indirectly use
> thread through a library (which use thread-aware errno). Are you
> completely su
Hi,
I'm trying to fix a portability bug related to `strftime(3)' [0]. The
`strftime' module doesn't provide `strftime ()' as one would expect but
instead provides `nstrftime ()', with additional arguments:
int ut, int ns. What are these arguments about?
Thanks,
Ludovic.
[0] https://savannah.gn
Le jeudi 21 août 2008 à 11:02 -0500, Matthew Woehlke a écrit :
> Yoann Vandoorselaere wrote:
> > Le jeudi 21 août 2008 à 12:28 +0200, Bruno Haible a écrit :
> >> Yoann Vandoorselaere wrote:
> >>> Most program using the library currently don't (and probably won't)
> >>> depend on GnuLib. They are no
> Reuben has chosen to set CPP_PEDANTIC to true, so in order to get rid of the
> warning, he needs to make dir->origin == EXTENSION evaluate to false.
> This means, specify the directory containing the built gnulib header files
> with '-isystem' instead of '-I'.
You can put "#pragma GCC system_
> Reuben has chosen to set CPP_PEDANTIC to true, so in order to get rid of the
> warning, he needs to make dir->origin == EXTENSION evaluate to false.
> This means, specify the directory containing the built gnulib header files
> with '-isystem' instead of '-I'.
I could try implementing somethi
26 matches
Mail list logo
