From: H.J. Lu <hjl@lucon.org>
To: egcs@cygnus.com
Subject: Re: egcs-ss-970814
Date: Sun, 17 Aug 1997 14:30:54 -0000 [thread overview]
Message-ID: <m0x07Mv-0004ecC@ocean.lucon.org> (raw)
In-Reply-To: 4644.871827837@hurl.cygnus.com
> The more I think about it, the more I feel there should be a "full blown"
> release -- with all the languages, testsuites, targets, etc and a "lite"
> release which is just the C compiler, then separate tarballs released in
> lockstep that one can extract to get g++, g77, objc, the testsuite, etc.
>
Should I dig out my libgccbackend.so patch? It will reduce the binary
size:
# ls -l /usr/lib/gcc-lib/i486-linux/2.7.2-951223-so
-rwxr-xr-x 1 root root 204648 Dec 23 1995 cc1
-rwxr-xr-x 1 root root 281244 Dec 23 1995 cc1obj
-rwxr-xr-x 1 root root 608308 Dec 23 1995 cc1plus
-rwxr-xr-x 1 root root 1470404 Dec 23 1995 libgccbnd.so.2.7.2-951223-so
--
H.J. Lu (hjl@gnu.ai.mit.edu)
next reply other threads:[~1997-08-17 14:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-08-17 14:30 H.J. Lu [this message]
-- strict thread matches above, loose matches on Subject: below --
1997-08-17 18:01 970814 and libg++ Mumit Khan
1997-08-17 19:05 ` egcs-ss-970814 Jeffrey A Law
1997-08-16 23:30 egcs-ss-970814 David S. Miller
1997-08-17 4:12 ` egcs-ss-970814 Andi Kleen
1997-08-17 14:23 ` egcs-ss-970814 Jeffrey A Law
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=m0x07Mv-0004ecC@ocean.lucon.org \
--to=hjl@lucon.org \
--cc=egcs@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).