public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeffrey A Law <law@cygnus.com>
To: Carlo Wood <carlo@runaway.xs4all.nl>
Cc: egcs@cygnus.com (egcs@cygnus.com)
Subject: Re: bcopy -> memcpy/memmove transition proposal
Date: Sun, 20 Sep 1998 13:55:00 -0000	[thread overview]
Message-ID: <4865.906314351@hurl.cygnus.com> (raw)
In-Reply-To: <199809201419.QAA06773@jolan.ppro>

  In message < 199809201419.QAA06773@jolan.ppro >you write:
  > | Some popular systems do not provide ANSI compilers by default with
  > | their systems.  HPUX for example.  Solaris may also be in the same
  > | boat.
  > 
  > >From my ircu package ;)
  > 
  >   The package needs an ANSI compiler.  Some compilers need an extra option
  >   to compile ANSI C.  In those cases you can add these options also here.
  >   For example, on a HPUX-8.x you would use (if you don't have gcc):
  >   "cc -Aa -D_HPUX_SOURCE".
  > 
  > I agree that this from quite an old source, a few years ago, but I can't
  > believe that HPUX can afford NOT to have an ANSI compiler, so I guess
  > this will still work.
hpux9, hpux10 and hpux11 do *NOT* come with an ANSI compiler.  If you
have code which uses ansi prototypes or ansi function definitions and
you have not purchased the ansi compiler you will not be able to build
that code on hpux9, hpux10, or hpux11 systesm.

I don't really remember if hpux8's compiler allowed ansi or not.  Too
long ago.

jeff

  reply	other threads:[~1998-09-20 13:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-09-17  9:59 Per Bothner
1998-09-18  4:02 ` Carlo Wood
1998-09-18 23:53 ` Jeffrey A Law
1998-09-19  8:07 ` John Carr
1998-09-19 20:44   ` Jeffrey A Law
1998-09-20 10:48     ` Carlo Wood
1998-09-20 13:55       ` Jeffrey A Law [this message]
1998-09-20 10:48     ` John Carr
1998-09-20 10:55       ` Jeffrey A Law
1998-09-19 12:03 Kaveh R. Ghazi
1998-09-19 17:40 ` Per Bothner
1998-09-19 22:27   ` Jeffrey A Law
1998-09-20  6:39 ` Jeffrey A Law
1998-09-19 20:44 N8TM
1998-09-20 13:45 Kaveh R. Ghazi
1998-09-20 13:58 Kaveh R. Ghazi

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=4865.906314351@hurl.cygnus.com \
    --to=law@cygnus.com \
    --cc=carlo@runaway.xs4all.nl \
    --cc=egcs@cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).