public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>
To: law@cygnus.com
Cc: egcs@cygnus.com, jfc@mit.edu, robertl@dgii.com
Subject: Re: including <stdlib.h>
Date: Fri, 13 Feb 1998 10:31:00 -0000	[thread overview]
Message-ID: <199802131537.KAA05197@caip.rutgers.edu> (raw)

 > From: Jeffrey A Law <law@hurl.cygnus.com>
 >  
 >   > On pre-ANSI systems, I think varargs was present on svr3.  I don't know
 >   > about older BSD.  (Did they use _doprnt?)
 >  
 > I don't think we need to worry too much about that -- 4.2BSD had varargs
 > if I remember correctly (it used _doprnt internally in the C library,
 > but I believe it still had a varargs.h include file).
 > jeff 

	The only system I ever had access to on which configure decided
to use _doprnt was an old Tektronix 4300 running a variant of BSD 4.2
called UTek 4.?.  When building meyering's *utils packages, configure
would punt down to _doprnt which was used by *utils/lib/error.c because
vprintf wasn't present.  I don't recall if varargs.h was available or
not. 

	I don't think it matters because to my knowledge gcc never
officially worked on that system, though I think an unofficial port was
floating around. 

	Other BSD 4.2 systems may or may not be an issue.  Anyone
remember what Pyramid OSx 4.x had in its BSD universe?  Hmm, maybe this
doesn't matter? :-)

		--Kaveh
--
Kaveh R. Ghazi			Project Manager / Custom Development
ghazi@caip.rutgers.edu		ICon CMT Corp.

             reply	other threads:[~1998-02-13 10:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-02-13 10:31 Kaveh R. Ghazi [this message]
  -- strict thread matches above, loose matches on Subject: below --
1998-02-12 19:36 Kaveh R. Ghazi
1998-02-13  2:04 ` Jeffrey A Law
1998-02-11 11:23 Kaveh R. Ghazi
1998-02-11 11:23 ` Robert Lipe
1998-02-11 17:22 ` Ross Smith
1998-02-12  4:26   ` Mark Mitchell
1998-02-11 11:23 Kaveh R. Ghazi
1998-02-12  4:26 ` Jeffrey A Law
1998-02-11  4:23 John Carr
1998-02-11  6:50 ` Robert Lipe
1998-02-11  6:50   ` John Carr
1998-02-11 11:23 ` Jeffrey A 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=199802131537.KAA05197@caip.rutgers.edu \
    --to=ghazi@caip.rutgers.edu \
    --cc=egcs@cygnus.com \
    --cc=jfc@mit.edu \
    --cc=law@cygnus.com \
    --cc=robertl@dgii.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).