public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Kaz Kylheku (Cygwin)" <743-406-3965@kylheku.com>
To: Cygwin <cygwin@cygwin.com>
Subject: Build spends a long time in "mkimport".
Date: Sat, 10 Oct 2020 19:32:22 -0700	[thread overview]
Message-ID: <af9f360a0a782f3c4db698e9f4584d16@mail.kylheku.com> (raw)

Hi All,

When building the Cygwin DLL, this single step takes almost ten minutes:

   ../../.././winsup/cygwin/mkimport --cpu=i686 --ar=ar --as=as --nm=nm 
--objcopy=objcopy \
   --replace=atexit= --replace=timezone= --replace=uname=uname_x 
--replace=__xdrrec_getrec=

   [ .. SNIP ... ]

   --replace=truncate=_truncate64 libcygwin.a cygdll.a 
_cygwin_crt0_common.o \
   atexit.o cygwin_attach_dll.o cygwin_crt0.o dll_entry.o dll_main.o 
dso_handle.o \
   libcmain.o premain0.o premain1.o premain2.o premain3.o 
pseudo-reloc-dummy.o

What's puzzling is that there is very CPU activity during this time. 
It's launching
some objcopy commands.

Is there some documentation that provides an overview of what exactly 
this does,
other than studying its perl source code?

Maybe it can be sped up?

I'm going to have to cycle quite a few times on some changes, so this is 
frustrating.




             reply	other threads:[~2020-10-11  2:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-11  2:32 Kaz Kylheku (Cygwin) [this message]
2020-10-11  7:24 ` Mark Geisert

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=af9f360a0a782f3c4db698e9f4584d16@mail.kylheku.com \
    --to=743-406-3965@kylheku.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).