public inbox for gas2@sourceware.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <ian@cygnus.com>
To: joel@merlin.gcs.redstone.army.mil
Cc: gas2@cygnus.com
Subject: Re: libiberty question
Date: Tue, 09 Jul 1996 08:17:00 -0000	[thread overview]
Message-ID: <199607091516.LAA17703@sanguine.cygnus.com> (raw)
In-Reply-To: <Pine.SV4.3.91.960709095256.12439D-100000@merlin>

   Date: Tue, 9 Jul 1996 09:57:02 -0500 (CDT)
   From: Joel Sherrill <joel@merlin.gcs.redstone.army.mil>

   On Tue, 9 Jul 1996, Ian Lance Taylor wrote:

   >    config/mt-rtems which had the following:
   > 
   >    HDEFINES = -DNO_SYS_PARAM_H -DNO_SYS_FILE_H
   > 
   > I tend to think that you will be better off providing both those
   > files.

   Right now almost every header file we have is directly from newlib.  
   Looking at the Solaris versions of these two, it will be a while before 
   we could do them.  I think the vxworks configuration made a good decision 
   here.

The current version of newlib provides both those files.

VxWorks has its own header files, which are controlled by WRS, so the
VxWorks configuration has no choice.

Here is <sys/file.h> from newlib:

==================================================
#include <sys/fcntl.h>
==================================================

Here is <sys/param.h> from newlib:

==================================================
/* This is a dummy <sys/param.h> file, not customized for any
   particular system.  If there is a param.h in libc/sys/SYSDIR/sys,
   it will override this one.  */

#ifndef _SYS_PARAM_H
# define _SYS_PARAM_H

# define HZ (60)
# define NOFILE	(60)
# define PATHSIZE (1024)

#endif
==================================================

Ian


  reply	other threads:[~1996-07-09  8:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-07-09  7:12 Joel Sherrill
1996-07-09  7:31 ` Ian Lance Taylor
1996-07-09  8:09   ` Joel Sherrill
1996-07-09  8:17     ` Ian Lance Taylor [this message]
1996-07-09  9:52       ` Joel Sherrill

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=199607091516.LAA17703@sanguine.cygnus.com \
    --to=ian@cygnus.com \
    --cc=gas2@cygnus.com \
    --cc=joel@merlin.gcs.redstone.army.mil \
    /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).