public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: binutils-2.34+1git.de9c1b7cfe-1 (x86/x86_64)
Date: Thu, 19 Mar 2020 06:25:02 +0100	[thread overview]
Message-ID: <dba4e3cf-bbfc-8c49-3177-5c15c7936c4b@gmail.com> (raw)
In-Reply-To: <CAAXzdLWXD09FkgTmo2FY0kH4NmyYeAu9gnQaarkwYxKjYjOx3Q@mail.gmail.com>

Am 19.03.2020 um 01:25 schrieb Steven Penny via Cygwin:
>> The following packages have been uploaded to the Cygwin distribution:
>>
>> * binutils-2.34+1git.de9c1b7cfe
>>
>> This release should fix libtool shared library builds on 32bit Cygwin.
> 
> Below are the current "non Base" dependencies (and transitive dependencies) of
> current "python3". As can be seen, "binutils" is now larger than all the other
> dependencies combined.
> 
> Can we please, please address whatever exploded "binutils" size? 


It seems something is adding 5M or more to the normal
size of the programs


$ du -sh *.exe
5.2M    addr2line.exe
5.2M    ar.exe
5.8M    as.exe
5.2M    c++filt.exe
5.2M    coffdump.exe
5.2M    dlltool.exe
48K     dllwrap.exe
40K     elfedit.exe
5.2M    gprof.exe
8.9M    ld.bfd.exe
5.2M    nm.exe
5.3M    objcopy.exe
18M     objdump.exe
5.2M    ranlib.exe
740K    readelf.exe
5.2M    size.exe
5.2M    srconv.exe
5.2M    strings.exe
5.3M    strip.exe
5.2M    sysdump.exe
5.2M    windmc.exe
5.3M    windres.exe

and I will bet it is the same that pushed debian to have some shared lib

/usr/lib/x86_64-linux-gnu/libbfd-2.34-system.so
/usr/lib/x86_64-linux-gnu/libopcodes-2.34-system.so

to avoid data duplication between the binaries
https://packages.debian.org/sid/amd64/libbinutils/filelist







  reply	other threads:[~2020-03-19  5:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-19  0:25 Steven Penny
2020-03-19  5:25 ` Marco Atzeri [this message]
2020-03-19 23:18   ` Brian Inglis
2020-03-20 19:24     ` Hans-Bernhard Bröker
2020-03-21  4:55       ` Marco Atzeri
2020-03-21  6:40         ` Marco Atzeri
2020-03-22 20:19           ` Yaakov Selkowitz
2020-03-22 23:05             ` Marco Atzeri
2020-04-01 11:33 ` Jan Nijtmans
2020-04-06 10:07   ` Problem in mingw64-i686-binutils [Was: Updated: binutils-2.34+1git.de9c1b7cfe-1 (x86/x86_64)] Jan Nijtmans
2020-04-06 23:55     ` JonY
2020-04-07  0:57       ` Yaakov Selkowitz
2020-04-07 10:29         ` JonY
  -- strict thread matches above, loose matches on Subject: below --
2020-03-15 10:33 [ANNOUNCEMENT] Updated: binutils-2.34+1git.de9c1b7cfe-1 (x86/x86_64) JonY via Cygwin-announce

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=dba4e3cf-bbfc-8c49-3177-5c15c7936c4b@gmail.com \
    --to=marco.atzeri@gmail.com \
    --cc=cygwin@cygwin.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).