-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Eric Blake on 9/16/2008 4:50 PM:
> I've finally figured out why c-stack is being finicky on Irix 5.3 [1]. POSIX
> requires that sigaltstack be given ss_sp pointing to the smallest address in
> the alternate stack. But Irix is non-compl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Reuben Thomas on 9/20/2008 4:22 PM:
>> gnulib checks that the compiler supports #include_next before actually
>> stuffing #include_next into the generated .h files.
>
> I think I might be confused here. I am running gnulib on my computer,
On Sun, 21 Sep 2008, Bruno Haible wrote:
Hi,
Reuben Thomas wrote:
Trying to build some code I wrote using gnulib on an old machine, it choked
on #include_next. It is using gcc 3.3.3. Some other machines with non-GNU
compilers seem to work OK, so is the problem that gnulib assumes that
too-old
Hi,
Reuben Thomas wrote:
> Trying to build some code I wrote using gnulib on an old machine, it choked
> on #include_next. It is using gcc 3.3.3. Some other machines with non-GNU
> compilers seem to work OK, so is the problem that gnulib assumes that
> too-old versions of GCC support #include_n
Trying to build some code I wrote using gnulib on an old machine, it choked
on #include_next. It is using gcc 3.3.3. Some other machines with non-GNU
compilers seem to work OK, so is the problem that gnulib assumes that
too-old versions of GCC support #include_next?
--
http://rrt.sc3d.org/ | P
Hi Bruno,
Thanks for your reply.
* Bruno Haible wrote on Sat, Sep 20, 2008 at 04:20:02PM CEST:
> > > It is all committed now.
> >
> > Thanks. Some change between then and now caused differences in the
> > coreutils po files, though.
>
> Yes, this is intentional.
OK, good to know. I was afrai
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Bruno Haible on 9/18/2008 4:34 AM:
> (You apparently copied the code for 'double'.
Yes.
> In the
> 'double' case on mingw, in 'e' format, we need to use 3 digits for the
> exponent, to match what MSVCRT does. This is not needed for 'long
Hi Ralf,
> > It is all committed now.
>
> Thanks. Some change between then and now caused differences in the
> coreutils po files, though.
Yes, this is intentional. In the draft patch, I had special code to
guarantee backward compatibility, namely in case of ambiguity, to choose
the string with
On Sat, Sep 20, 2008 at 02:52:28PM +0200, Bruno Haible wrote:
> Thanks for reporting this. The problem is apparently that on this platform,
> neither not defines wint_t. I'm applying the attached
> tentative workaround.
>
> When you create a new testdir from latest gnulib mbchar, does it now pas
Tom G. Christensen wrote:
> I was trying to build GNU tar 1.20 but got stuck on gnulib mbchar.
>
> I created a testdir from the latest gnulib mbchar and this is the
> result:
> make[3]: Entering directory `/usr/people/tgc/mbchar.test/mbchar/gllib'
> source='localcharset.c' object='localcharset.o'
10 matches
Mail list logo