[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: INSTALL should tell about particular systems, HP-UX cc

From: Ralf Wildenhues
Subject: Re: INSTALL should tell about particular systems, HP-UX cc
Date: Thu, 21 Aug 2008 10:42:39 +0200
User-agent: Mutt/1.5.18 (2008-05-17)

* Eric Blake wrote on Wed, Aug 20, 2008 at 03:28:30PM CEST:
> According to Eric Blake on 4/29/2008 6:46 AM:
> > According to Bruno Haible on 4/26/2008 7:18 AM:
> > | Ping? What about installing the patch in
> > |  
> > ?
> > 
> > I haven't forgotten, but also haven't had time to think about it in depth.
> Here's what I'm applying.  Please let me know if this needs touchups.

Thanks, and sorry for dropping the ball on this.

> > Doable, but it will mean AC_USE_SYSTEM_EXTENSIONS has to be called early
> > (the existing implementation only adds -D options, but once you start
> > modifying CFLAGS, it invalidates all prior compilation tests).
> Hmm.  As it stands, AC_USE_SYSTEM_EXTENSIONS already needs to figure out
> $CC, and I already have an in-progress patch that tries to make
> AC_REQUIRE([AC_PROG_CC]) work.  Still, this remains unimplemented; for
> that matter, I'm not sure whether 2.63 should be held up for that.  So I
> went ahead with the documentation as-is for now.

Good thinking.  Let's put off the hard stuff until later.

The patch looks good to me, one tiny nit (which you may freely ignore):

> --- a/doc/install.texi
> +++ b/doc/install.texi
> @@ -179,6 +179,36 @@ Optional Features
>  @address@hidden and @address@hidden to
>  specify their locations.
> address@hidden Particular Systems
> address@hidden Particular systems
> +
> +On HP-UX, the default C compiler is not ANSI C compatible.  If GNU CC is

s/GNU CC/GCC/?  Wondering because GCC is used elsewhere in the document.

> +On OSF/1 a.k.a.@: Tru64, some versions of the default C compiler cannot
> +parse its @code{<wchar.h>} header file.  The option @option{-nodtk} can be
> +used as a workaround.  If GNU CC is not installed, it is therefore


Cheers, and thanks,

reply via email to

[Prev in Thread] Current Thread [Next in Thread]