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 07:31:00 -0000	[thread overview]
Message-ID: <199607091431.KAA17618@sanguine.cygnus.com> (raw)
In-Reply-To: <Pine.SV4.3.91.960709085127.12439A-100000@merlin>

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

   I think rtems needs to be treated like vxworks.  I added a 
   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.

   The config/mt-vxworks5 file had the building of a vxconfig.h.  Could
   someone explain it to me well enough so I can decide if I should build
   something similar.  It builds with just the above line in the mt file, I 
   just wanted to know if I should be doing more.

The way libiberty configures itself is to link programs and try to
figure out what is missing.  VxWorks, however, is unusual, in that
programs are never fully linked.  Instead, relocateable object files
are downloaded into the VxWorks system, which completes the link as it
loads the object.  VxWorks provides the basic libc functions.  The
effect of this is that the libiberty configuration method is useless,
because it is not possible to fully link a program, and thus it is not
possible to figure out what is present and what is missing.  The
special VxWorks configuration handling in libiberty is used to get
around that problem.

If RTEMS has similar characteristics, then a similar solution will be
required.  In the more normal case, however, it will not.

Ian


  reply	other threads:[~1996-07-09  7:31 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 [this message]
1996-07-09  8:09   ` Joel Sherrill
1996-07-09  8:17     ` Ian Lance Taylor
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=199607091431.KAA17618@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).