[Cross posting to bug-gnulib@gnu.org, bug-texi...@gnu.org and
bug-recut...@gnu.org]
On Fri, Aug 24, 2012 at 07:52:01AM +0200, Jose E. Marchesi wrote:
Hi John.
I suggest this patch.
We are following the advise of Karl Berry and not using @acronym{} in
the
On 08/23/2012 02:44 PM, Paul Eggert wrote:
> I worry that this may break on older GCCs that
> don't let you put attributes at the start of a declaration.
Ah, I now see that we have such declarations elsewhere,
so if this were a problem we'd probably have run into it
by now. So please don't bother
On 08/23/2012 01:10 PM, Jim Meyering wrote:
> -void _Noreturn xstrtol_fatal (enum strtol_error,
> +_Noreturn void xstrtol_fatal (enum strtol_error,
I worry that this may break on older GCCs that
don't let you put attributes at the start of a declaration.
_Noreturn expands to __attribute__ ((__nore
Building coreutils with the latest gcc from git/svn, I see this new failure:
./xstrtol.h:69:1: error: '_Noreturn' is not at beginning of declaration \
[-Werror=old-style-declaration]
void _Noreturn xstrtol_fatal (enum strtol_error,
^
The following fixes it, but I suspect we'll want t
> Date: Thu, 23 Aug 2012 13:36:16 +0200
> From: Bastien ROUCARIES
> Cc: Eli Zaretskii , emacs-de...@gnu.org, egg...@cs.ucla.edu,
> bug-gnulib@gnu.org, monn...@iro.umontreal.ca
>
> [sorry for retrieving this old thread]
I suggest to let the sleeping dogs lie.
[sorry for retrieving this old thread]
On Wed, Jan 26, 2011 at 1:02 PM, Jim Meyering wrote:
> Eli Zaretskii wrote:
>>> From: Bastien ROUCARIES
>>> Date: Tue, 25 Jan 2011 23:37:08 +0100
>>>
>>> (if and only if doslfn is buggy, and it does not seems according to
>>> a quick search).
>>
>> Your sear
Le Thursday 23 August 2012 11:23:49, Bruno Haible a écrit :
> Hi Bastien,
>
> > Could be possible to get under the section target platform the
> > compiler supported?
>
> You mean in the documentation?
Yes in the documentation
> gnulib supports all ANSI C compilers,
> except those that are evid
Hi Bastien,
> Could be possible to get under the section target platform the
> compiler supported?
You mean in the documentation? gnulib supports all ANSI C compilers,
except those that are evidently too buggy (e.g. pcc-1.0 [1]).
> I need to know the compiler used.
You get a list of known prede
Hi,
Could be possible to get under the section target platform the
compiler supported?
I have a new idea to get a portable programname but I need to know the
compiler used.
Bastien
