public inbox for gas2@sourceware.org
 help / color / mirror / Atom feed
From: joel@OARcorp.com
To: Jeffrey A Law <law@cygnus.com>
Cc: egcs@cygnus.com, gas2@cygnus.com
Subject: Re: egcs and binutils snapshots
Date: Tue, 08 Sep 1998 05:48:00 -0000	[thread overview]
Message-ID: <Pine.LNX.3.96.980908075208.2424C-100000@oar3remote.oarcorp.com> (raw)
In-Reply-To: <1536.905232609@hurl.cygnus.com>

On Mon, 7 Sep 1998, Jeffrey A Law wrote:

>   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.

This is not the first time this has happened. :)

> 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.

It is hard to keep everything in sync with so many tools using the same
top level scripts.

>   > + egcs does not yet know about libintl (internationalization library)
> Yes.  This will be changing after the next merge from gcc2.

As long as it is egcs + binutils snapshot, then it is OK.  Before a new
binutils release, this needs to be fixed.


--joel


      reply	other threads:[~1998-09-08  5:48 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
1998-09-08  5:48   ` joel [this message]

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.LNX.3.96.980908075208.2424C-100000@oar3remote.oarcorp.com \
    --to=joel@oarcorp.com \
    --cc=egcs@cygnus.com \
    --cc=gas2@cygnus.com \
    --cc=law@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).