Paul D. Smith <pausmith_at_nortelnetworks.com> wrote:
>
> GNU's autoconf stuff goes to great lengths to find the right switches
> to enable ANSI-ification on the C compiler. You shouldn't need to do
> anything fancy to get this?
Newer versions of autoconf do this quite well, but not every package one
finds on the net was built with the latest versions of autoconf. If I
have problems building, forcing the '-Ae' switch is the first thing I
try.
> ff> env CC=cc CFLAGS='-Ae -O' ./configure [--options]
>
> Is this with the native "cc" that comes free with the HP-UX system, or
> with their unbundled "add-on" C compiler you have to buy separately?
This is with the non-free compiler. The "bundled" compiler is very
noisy and annoying about its inability to become ANSI compliant, giving
a message like this when you try to use -Ae:
(Bundled) cc: warning 480: The -A option is available only with the
C/ANSI C product; ignored.
If you see this, then you have little choice but to go with gcc.
If you (or whoever owns the box you're trying to build on) has paid the
money for the HP ANSI C compiler, you might as well make use of it..
eh? :)
--
fox_at_foxtaur.com (Fuzzy Fox) || "Good judgment comes from experience.
sometimes known as David DeSimone || Experience comes from bad judgment."
http://www.dallas.net/~fox/ || -- Life Lessons
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Tue Nov 30 1999 - 14:17:02 GMT