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: Mon, 23 Mar 2020 00:05:27 +0100 [thread overview]
Message-ID: <d8cc746d-a82f-04d4-44ad-26e0ece86454@gmail.com> (raw)
In-Reply-To: <4b93cb17c7c59a459eceae350125657ce6823da1.camel@cygwin.com>
Am 22.03.2020 um 21:19 schrieb Yaakov Selkowitz:
> On Sat, 2020-03-21 at 07:40 +0100, Marco Atzeri via Cygwin wrote:
>> Am 21.03.2020 um 05:55 schrieb Marco Atzeri:
>>> Am 20.03.2020 um 20:24 schrieb Hans-Bernhard Bröker:
>>>> Am 20.03.2020 um 00:18 schrieb Brian Inglis:
>>>>> On 2020-03-18 23:25, Marco Atzeri via Cygwin wrote:
>>>>>> It seems something is adding 5M or more to the normal
>>>>>> size of the programs
>>>>>
>>>>> See attached for summary details by arch, but main points for both
>>>>> are, on x86_64:
>>>> [...]
>>>>
>>>> Could this be due to the ginormous number of targets configured into
>>>> the build?
>>>
>>> may be, as it also take ages to full compile with the
>>> current configuration:
>>>
>>> # --enable-shared
>>> CYGCONF_ARGS="
>>> --enable-install-libiberty
>>> --disable-gdb
>>> --disable-libdecnumber
>>> --disable-readline
>>> --disable-sim
>>> --enable-64-bit-bfd
>>> --enable-targets=all
>>> "
>>>
>>> I am testing a build dropping the "enable-targets=all"
>>> and also forcing the "enable-shared"
>>>
>>> --enable-shared \
>>> lt_cv_deplibs_check_method=pass_all
>
> If that doesn't work, feel free to borrow:
thanks. It does not work.
>
> https://github.com/cygwinports/binutils/blob/master/2.24.51-shared-libs.patch
>
> However, these libraries are (by design) API-unstable, so is not
> recommended to allow other code to link against these shared libs,
> therefore I would also suggest:
>
> https://github.com/cygwinports/binutils/blob/master/binutils.cygport#L30-L38
understood
>
>>> Hoping it will note ages again....
>>
>> "NOT take"
>>
>> dropping the target seems to work very well
>>
>> current version
>> $ du -sb /usr/bin/gprof.exe
>> 5424147 /usr/bin/gprof.exe
>>
>> under build
>> $ du -sb gprof/gprof.exe
>> 19968 gprof/gprof.exe
in reality I was fooled by the stub,
the stripped version is ~ 1M insted of 5M
$ du -sb inst/usr/bin/gprof.exe
1146387 inst/usr/bin/gprof.exe
>> any clue why we are using a "enable-targets=all" options ?
>
> Not sure, but if it's just so that 32-bit utils can read 64-bit
> binaries (which is useful), --enable-targets=x86_64-pep should be
> enough.
there is a trace of previous setting before "all" in the cygport
#
--enable-targets=i686-efi-pe,x86_64-efi-pe,ia64-efi-elf,x86_64-pc-cygwin,i686-pc-cygwin
>
>> Any cross compiler should use its own binutils not the cygwin one, correct ?
>
> Yes, regardless.
>
> --
> Yaakov
>
Thanks as usual
Marco
next prev parent reply other threads:[~2020-03-22 23:05 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
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 [this message]
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=d8cc746d-a82f-04d4-44ad-26e0ece86454@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).