On Sat, 20 Sep 2008, Eric Blake wrote:
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,
and distribu
-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
