From: Segher Boessenkool <segher@kernel.crashing.org>
To: "Thompson,
Matt (GSFC-610.1)[SCIENCE SYSTEMS AND APPLICATIONS INC]"
<matthew.thompson@nasa.gov>
Cc: "gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: Re: Reducing size of GCC installation?
Date: Tue, 4 Aug 2020 15:24:14 -0500 [thread overview]
Message-ID: <20200804202414.GK6753@gate.crashing.org> (raw)
In-Reply-To: <A27CF849-ED98-4F70-A513-D3560E5D5998@contoso.com>
Hi!
On Tue, Aug 04, 2020 at 07:26:09PM +0000, Thompson, Matt (GSFC-610.1)[SCIENCE SYSTEMS AND APPLICATIONS INC] via Gcc-help wrote:
> To wit, I'm trying to build some Docker images and found that the code I'm eventually trying to build with gcc (gfortran, actually) doesn't like the versions from RPMs/DEBs/etc. So, my first step is usually to do what I'm quite used to and build GCC a la:
>
> ../gcc-10.2.0/configure --prefix=$HOME/GCC/10.2.0 --disable-multilib --enable-languages=c,c++,fortran
> make
> make install
>
> and this works. Huzzah.
make install-strip
> Ouch. 1.6G.
How much does install-strip safe?
> Or perhaps is there a configure option to "ensmallen GCC" upon installation?
Yes :-) It is documented on
https://gcc.gnu.org/install/finalinstall.html
There may be other tricks in the installation manual you missed as well?
Good luck and have fun,
Segher
next prev parent reply other threads:[~2020-08-04 20:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-04 19:26 Thompson, Matt (GSFC-610.1)[SCIENCE SYSTEMS AND APPLICATIONS INC]
2020-08-04 20:24 ` Segher Boessenkool [this message]
2020-08-04 21:10 ` [EXTERNAL] " Thompson, Matt (GSFC-610.1)[SCIENCE SYSTEMS AND APPLICATIONS INC]
2020-08-04 20:50 ` Jonathan Wakely
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=20200804202414.GK6753@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=gcc-help@gcc.gnu.org \
--cc=matthew.thompson@nasa.gov \
/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).