Re: Problems with old GCC and #include_next

[Eric Blake]

-----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,
> and distributing the files it builds. Should I not be doing this?

When both a .in.h and .h file exist, only distribute the .in.h file (the
gnulib automake snippets already do this for you, with no extra effort
needed on your part).  The generated files fall in the same category as
config.h - distributing what worked on your system is wrong, because the
final generated file depends on configure results which are machine-specific.

- --
Don't work too hard, make some time for fun as well!

Eric Blake             address@hidden
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkjVfSkACgkQ84KuGfSFAYDfEwCeK4QtNEroPq8GepIayRc8/SwN
+gEAnREp2o2IQ74AXz//DYXuTkjFEJDV
=sEGN
-----END PGP SIGNATURE-----