From: Richard Stallman <rms@gnu.ai.mit.edu>
To: hjl@innovix.com
Cc: A.Schroeter@dkfz-heidelberg.de, gcc2@cygnus.com, ian@cygnus.com,
raeburn@cygnus.com, gas2@cygnus.com
Subject: Re: fat binaries ?
Date: Thu, 30 May 1996 00:21:00 -0000 [thread overview]
Message-ID: <199605300721.DAA10378@delasyd.gnu.ai.mit.edu> (raw)
In-Reply-To: <m0uOQ2D-0000WKC@eric.innovix.com>
I don't think it is essential to have fat binaries.
In fact I think it is more convenient to use other techniques
such as architecture-dependent symlinks together with separate
directories for the various architectures.
But if a convention is established for multi-architecture binaries, we
might as well support it. All that would be needed would be a simple
program to extract and install subfiles in an archive of that kind.
This is a modular design which would not involve any changes in the C
compiler or GAS, and perhaps not even in the binutils.
prev parent reply other threads:[~1996-05-30 0:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9605281010.ZM21624@borneo.inet.dkfz.heidelberg.de>
1996-05-28 7:47 ` H.J. Lu
1996-05-28 9:25 ` Mat Hostetter
1996-05-29 0:04 ` Samuel Figueroa
1996-05-30 0:21 ` Richard Stallman [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=199605300721.DAA10378@delasyd.gnu.ai.mit.edu \
--to=rms@gnu.ai.mit.edu \
--cc=A.Schroeter@dkfz-heidelberg.de \
--cc=gas2@cygnus.com \
--cc=gcc2@cygnus.com \
--cc=hjl@innovix.com \
--cc=ian@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).