Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: law@redhat.com
To: gdb-patches@sources.redhat.com
Subject: configure patch for hpux
Date: Wed, 12 Dec 2001 21:46:00 -0000	[thread overview]
Message-ID: <2033.1008222286@porcupine.cygnus.com> (raw)


aclocal.m4 includes code to find what options (if any) will put the host
compiler into an ANSI-like mode.

However, we do not want to go into strict ANSI mode as that turns off
useful extensions and breaks some systems's header files (almost a direct
quote from aclocal.m4).

For HPUX, using -Aa gives you an ANSI compiler, but has non-ANSI extensions
turned off.  -Ae gives you ANSI with the extensions.

Amazingly enough, this actually matters as I've personally experienced on
an hpux10.20 system with the unbundled ANSI compiler installed.

This patch to aclocal.m4 uses -Ae instead of -Aa to get ANSI+extensions
on hpux systems.

I have checked that this patch does not cause any problems on both
hpux10.20 and hpux11.00 systems, with both the bundled and unbundled
compiler.  It does fix compile-time failures when building with the 
unbundled compiler on hpux10.20.

Some time ago I stepped down as PA maintainer for GDB; so I'm not going
to install the patch until I get authorization from the GDB maintainers.

	* aclocal.m4 (proc_cc_stdc): Use -Ae, not -Aa to get ANSI+extensions
	on hpux systems.
	* configure: Rebuilt.

Index: aclocal.m4
===================================================================
RCS file: /cvs/cvsfiles/devo/gdb/aclocal.m4,v
retrieving revision 2.31
diff -c -3 -p -r2.31 aclocal.m4
*** aclocal.m4	2001/08/29 04:06:55	2.31
--- aclocal.m4	2001/12/13 05:29:22
*************** ac_save_CC="$CC"
*** 966,974 ****
  # breaks some systems' header files.
  # AIX			-qlanglvl=ansi
  # Ultrix and OSF/1	-std1
! # HP-UX			-Aa -D_HPUX_SOURCE
  # SVR4			-Xc -D__EXTENSIONS__
! for ac_arg in "" -qlanglvl=ansi -std1 "-Aa -D_HPUX_SOURCE" "-Xc 
-D__EXTENSIONS__"
  do
    CC="$ac_save_CC $ac_arg"
    AC_TRY_COMPILE(
--- 966,974 ----
  # breaks some systems' header files.
  # AIX			-qlanglvl=ansi
  # Ultrix and OSF/1	-std1
! # HP-UX			-Ae -D_HPUX_SOURCE
  # SVR4			-Xc -D__EXTENSIONS__
! for ac_arg in "" -qlanglvl=ansi -std1 "-Ae -D_HPUX_SOURCE" "-Xc 
-D__EXTENSIONS__"
  do
    CC="$ac_save_CC $ac_arg"
    AC_TRY_COMPILE(





             reply	other threads:[~2001-12-13  5:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-12 21:46 law [this message]
2001-12-12 22:43 ` Alexandre Oliva
2001-12-12 22:52   ` law
2001-12-12 23:08     ` Alexandre Oliva
2001-12-15  8:47       ` Andrew Cagney
2001-12-15 21:17         ` Alexandre Oliva
2001-12-18  9:29       ` law
2001-12-18 12:59         ` Tom Tromey
2001-12-15  8:41 ` Andrew Cagney
2001-12-19  8:48 law

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2033.1008222286@porcupine.cygnus.com \
    --to=law@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox