From: Michael Meissner <meissner@osf.org>
To: raeburn@cygnus.com
Cc: bfd@cygnus.com, gas2@cygnus.com
Subject: merging gas into binutils?
Date: Fri, 17 Jun 1994 07:36:00 -0000 [thread overview]
Message-ID: <9406171436.AA07931@pasta.osf.org> (raw)
In-Reply-To: <199406170048.UAA08348@cujo.cygnus.com>
|
| A suggestion has been made to merge gas into the binutils package,
| meaning there'd be only one distribution. It's an idea that's
| occurred to me before. And of course it's what I'm already doing for
| the nightly snapshots, though they're going under the name `gas' at
| the moment rather than `binutils'.
|
| That would make it about 2/3 the size of the current two packages,
| with bfd &c duplicated. On the other hand, it means someone wanting
| to pick up gas alone would have to download a bit more.
|
| The linker has got SunOS shared library support added (linking against
| them, not creating them), and other nifty new features. So that at
| least is no longer an argument for using gas but not the rest of
| binutils (specifically the linker). Offhand I don't know of a
| situation where you'd want binutils but not gas, though there may be
| one or two targets supported by binutils but not gas. And of course
| people would still have the option of only installing some of the
| programs distributed as `binutils'.
|
| Does anyone see a good reason why I shouldn't just combine them, and
| release `binutils 2.5, including assembler and linker' sometime?
I would say that ok, provided either the old gas tar files get removed
from prep, or a symlink is created from binutils-2.5.tar.gz to
gas-2.5.tar.gz is made.
next prev parent reply other threads:[~1994-06-17 7:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1994-06-16 17:48 Ken Raeburn
1994-06-17 7:36 ` Michael Meissner [this message]
1994-06-17 14:44 ` tower
1994-06-17 10:13 bgb
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=9406171436.AA07931@pasta.osf.org \
--to=meissner@osf.org \
--cc=bfd@cygnus.com \
--cc=gas2@cygnus.com \
--cc=raeburn@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).