Re: gnulib breakage on Tru64 UNIX with commercial C compiler

[Gary V. Vaughan]

On 5 Apr 2007, at 17:43, Paul Eggert wrote:

> One dumb question:
>
> Does the Tru64 compiler define __GNUC__, or some other similar symbol?

No, it doesn't.

> For the case of overriding standard headers I am thinking that this
> concern might be overdone.  If someone installs a gnulib-generated
> header like "stdint.h" into a shared location they are asking for
> trouble, no? because so many other things can go wrong.  So perhaps we
> should rethink this, and modify gnulib to use #include_next if
> available.  #include_next is a lot cleaner than the current approach.

Agreed.

> Another possibility is to protect #include_next with "#if
> HAVE_INCLUDE_NEXT"; this might support the shared-location scenario
> better, albeit with some complexity added.

The simpler solution wins out IMHO.

Cheers,
        Gary
--
  ())_.              Email me: address@hidden
  ( '/           Read my blog: http://blog.azazil.net
  / )=         ...and my book: http://sources.redhat.com/autobook
`(_~)_ Join my AGLOCO Network: http://www.agloco.com/r/BBBS7912

PGP.sig
Description: This is a digitally signed message part