Well, don't I feel dumb. I'd seen install-strip before on that page long ago, but I guess I just forgot about it (plus I got used to using strip with rustup/cargo builds which don't strip by default). And per your question, building with install-strip (in a different, but similar image): $ du -hsc gcc/* 35M gcc/bin 12M gcc/include 22M gcc/lib 29M gcc/lib64 119M gcc/libexec 15M gcc/share 230M total I will take a 1.3G reduction in space. I guess it's time to start using install-strip like a madman and see what I can break in other codes! :D -- Matt Thompson, SSAI, Ld Scientific Programmer/Analyst NASA GSFC, Global Modeling and Assimilation Office Code 610.1, 8800 Greenbelt Rd, Greenbelt, MD 20771 Phone: 301-614-6712 Fax: 301-614-6246 http://science.gsfc.nasa.gov/sed/bio/matthew.thompson On 8/4/20, 4:24 PM, "Segher Boessenkool" <segher@xxxxxxxxxxxxxxxxxxx> wrote: 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://urldefense.proofpoint.com/v2/url?u=https-3A__gcc.gnu.org_install_finalinstall.html&d=DwIBAg&c=ApwzowJNAKKw3xye91w7BE1XMRKi2LN9kiMk5Csz9Zk&r=t-_8LOcT3mR0eRjGIhNBgNcMPWsPBrZlJ8ZiJNKcEVg&m=6Ev8kbRqoawi75HbJkraV_KIXPl6EzRDJK_UzsUpl4Q&s=Jd1M-j9kKHFNkzzM7aJ4Ws2_9iGeEYxw0x9qsmP2JYg&e= There may be other tricks in the installation manual you missed as well? Good luck and have fun, Segher
