httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jim Jagielski <...@jaguNET.com>
Subject Re: [PATCH] Barf if using HP-UX non-ANSI cc, Take II
Date Fri, 25 Jul 1997 16:12:50 GMT
I don't think anyone said it _was_ a generic solution. I simply said
a generic solution would be nice.

Stanley Gambarin wrote:
> 
> 	This is not a generic solution, but the one specifically for HP C
> cc.  Bundled cc is always located in /usr/ccs/bin/cc, while ANSI one 
> is installed in /opt/ansic/bin/cc.  One can test for the presence of 
> later, and if not present, issue a warning and quit.  /bin/cc is a link
> to either the first (if ANSI c is not installed) or second if it is.
> 
> 
> On Thu, 24 Jul 1997, Jim Jagielski wrote:
> 
> > Marc Slemko wrote:
> > > 
> > > You could also run cc -Ae and see if it printed:
> > > 
> > > (Bundled) cc: warning 480: The -A option is available only with the C/ANSI
C product; ignored.
> > > 
> > > or some subset thereof.  The real cc won't ouput that warning.
> > > 
> > > The other one I can think of that could perhaps be worth checking is SunOS
> > > 4.x cc.
> > > 
> > 
> > Yeah.... A generic solution would be nice. Maybe just something
> > like a TestAnsi "helper" file would do it. It would try to compile
> > dummy.c and, if it fails, assume that it's because it's a Non-ANSI
> > compiler.
> 
> 


-- 
====================================================================
      Jim Jagielski            |       jaguNET Access Services
     jim@jaguNET.com           |       http://www.jaguNET.com/
            "Look at me! I'm wearing a cardboard belt!"

Mime
View raw message