public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Manfred Hollstein <manfred@s-direktnet.de>
To: ghazi@caip.rutgers.edu
Cc: egcs@cygnus.com
Subject: Re: egcs, does gcc fixincludes etc guarantee a stdlib.h exists?
Date: Sun, 29 Mar 1998 05:14:00 -0000	[thread overview]
Message-ID: <13597.5567.26876.276804@saturn.s-direktnet.de> (raw)
In-Reply-To: <199803272118.QAA25896@caip.rutgers.edu>

On Fri, 27 March 1998, 16:18:24, ghazi@caip.rutgers.edu wrote:

    	Simple question.  Does gcc guarantee that after it diddles with
    the system headers that a stdlib.h exists in some form?

Yes, it does. I have this situation on m68k-motorola-sysv. I've added
a small patch recently, which guarantees the generated stdlib.h
contains a definition for `size_t'. Otherwise, lots of g++ tests will fail.
    
    	For target files which include tconfig.h, since we can't check
    autoconf macros, I'd like to hardwire including stdlib.h to possibly get
    prototypes for malloc, et al. 

I'll have to look on Monday, which prototypes are actually generated.
    
    	This set of files would include frame.c and libgcc2.c.
    
    		Thanks,
    		--Kaveh

manfred

  parent reply	other threads:[~1998-03-29  5:14 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-03-27 15:18 Kaveh R. Ghazi
1998-03-28 19:24 ` Philippe De Muyter
1998-03-29  5:14 ` Manfred Hollstein [this message]
1998-03-31  0:46   ` Manfred Hollstein
1998-03-31  0:46 ` Jeffrey A Law
1998-04-02 11:32   ` Per Bothner
1998-04-02  9:35     ` Jeffrey A Law
1998-04-13 12:29 Kaveh R. Ghazi
1998-04-14  2:02 ` Philippe De Muyter
1998-04-16 15:31 ` Jim Wilson
1998-04-14  9:37 Kaveh R. Ghazi
1998-04-14  7:45 ` Philippe De Muyter
1998-04-16 16:34   ` Jim Wilson
1998-04-16 18:39     ` Jeffrey A Law
1998-04-17  2:23     ` Philippe De Muyter
1998-04-17 14:49       ` Jim Wilson
1998-04-20  4:16         ` Philippe De Muyter
1998-04-17 14:42   ` Philippe De Muyter
1998-04-20 22:16     ` Jim Wilson
1998-04-21 13:29       ` Philippe De Muyter
1998-04-21 17:38         ` Jim Wilson
1998-04-17  8:41 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=13597.5567.26876.276804@saturn.s-direktnet.de \
    --to=manfred@s-direktnet.de \
    --cc=egcs@cygnus.com \
    --cc=ghazi@caip.rutgers.edu \
    /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).