From: Joel Sherrill <joel@merlin.gcs.redstone.army.mil>
To: Ian Lance Taylor <ian@cygnus.com>
Cc: gas2@cygnus.com
Subject: Re: libiberty question
Date: Tue, 09 Jul 1996 08:09:00 -0000 [thread overview]
Message-ID: <Pine.SV4.3.91.960709095256.12439D-100000@merlin> (raw)
In-Reply-To: <199607091431.KAA17618@sanguine.cygnus.com>
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 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.
RTEMS applications are normally fully linked so libiberty's configuration
method should work.
With the addition of the mt-rtems file, sparc-rtems built and installed
successfully. It will be used in the next RTEMS testing cycle. I am
building the m68k now.
--joel
next prev parent reply other threads:[~1996-07-09 8:09 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 [this message]
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=Pine.SV4.3.91.960709095256.12439D-100000@merlin \
--to=joel@merlin.gcs.redstone.army.mil \
--cc=gas2@cygnus.com \
--cc=ian@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).