From: Jeffrey A Law <law@cygnus.com>
To: joel@OARcorp.com
Cc: egcs@cygnus.com, gas2@cygnus.com
Subject: Re: egcs and binutils snapshots
Date: Mon, 07 Sep 1998 22:31:00 -0000 [thread overview]
Message-ID: <1536.905232609@hurl.cygnus.com> (raw)
In-Reply-To: <Pine.LNX.3.96.980907094930.29532G-100000@oar3remote.oarcorp.com>
In message < Pine.LNX.3.96.980907094930.29532G-100000@oar3remote.oarcorp.com >you write:
> I have a report from an RTEMS user that the top level configure scripts
> have gotten out of sync between egcs and binutils snapshots. In
> particular, he mentioned that:
Yes. This is not unexpected.
They are totally separate source trees, and we (I) have not been making
an effort to move our configury changes back to other projects. At
some point it became impractical due to the rapid changes. Now that
it has settled down somewhat I'd like to submit some of those changes.
> + egcs does not yet know about libintl (internationalization library)
Yes. This will be changing after the next merge from gcc2.
jeff
next prev parent reply other threads:[~1998-09-07 22:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-09-07 7:46 joel
1998-09-07 22:31 ` Jeffrey A Law [this message]
1998-09-08 5:48 ` joel
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=1536.905232609@hurl.cygnus.com \
--to=law@cygnus.com \
--cc=egcs@cygnus.com \
--cc=gas2@cygnus.com \
--cc=joel@OARcorp.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).