From: Jonathan Wakely <jwakely.gcc@gmail.com>
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 21:50:47 +0100 [thread overview]
Message-ID: <CAH6eHdQy-TzROYV-k8znFPpk=7S9NyU7FMrQxjO5yGeGSvbLcA@mail.gmail.com> (raw)
In-Reply-To: <A27CF849-ED98-4F70-A513-D3560E5D5998@contoso.com>
On Tue, 4 Aug 2020 at 20:28, Thompson, Matt (GSFC-610.1)[SCIENCE
SYSTEMS AND APPLICATIONS INC] via Gcc-help <gcc-help@gcc.gnu.org>
wrote:
>
> All,
>
> This might be a FAQ, but my Google-fu is being stymied by the fact that my searches are often finding issues about making executables, etc. made by GCC smaller rather than my issue: making GCC itself smaller.
>
> 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
If you're not going to need them you can disable a number of features:
--disable-nls
--disable-libstdcxx-pch
--disable-libcc1
--disable-libsanitizer
--disable-libssp
--disable-libgomp
--disable-libvtv
--disable-libstdcxx-filesystem-ts
I wouldn't recommend this one, despite shrinking the size of
libstdc++.so and libstdc++.a, because it is an ABI break:
--disable-libstdcxx-dual-abi
If this one still works it would also be an ABI break (and make C++
code compile slower):
--disable-extern-template
prev parent reply other threads:[~2020-08-04 20:50 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
2020-08-04 21:10 ` [EXTERNAL] " Thompson, Matt (GSFC-610.1)[SCIENCE SYSTEMS AND APPLICATIONS INC]
2020-08-04 20:50 ` Jonathan Wakely [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='CAH6eHdQy-TzROYV-k8znFPpk=7S9NyU7FMrQxjO5yGeGSvbLcA@mail.gmail.com' \
--to=jwakely.gcc@gmail.com \
--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).