From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Why is taskset still not in util-linux?
Date: Sat, 21 Mar 2020 14:29:37 +0100 [thread overview]
Message-ID: <84e61507-aece-22d0-e956-0436d083d25c@gmail.com> (raw)
In-Reply-To: <b9a74f8a-93cb-bc57-e970-60503a4e064b@cs.umass.edu>
Am 21.03.2020 um 12:07 schrieb Eliot Moss:
> So here's a thing, though I don't understand it:
>
> In addition the build/taskset.exe, there's a build/.libs/taskset.exe.
that is usually the unstripped version
> If I install the latter in /usr/bin/.libs/taskset.exe, then
> /usr/bin/taskset
> works. In fact, it seems that the version in .libs is the "real" program
> and /usr/bin/taskset is some kind of trampoline (?) to it?
it is the libtool wrapper, infact it is linked only to cygwin1.dll
$ objdump -x .libs/gprof.exe | grep "DLL Name"
DLL Name: cygwin1.dll
DLL Name: cygintl-8.dll
DLL Name: KERNEL32.dll
$ objdump -x gprof.exe | grep "DLL Name"
DLL Name: cygwin1.dll
DLL Name: KERNEL32.dll
$ strings gprof.exe | grep ".libs"
./.libs/lt-gprof.c
# gprof - temporary wrapper script for .libs/gprof
...
>
> In fact, a stripped version of build/.libs/taskset installed in /usr/bin
> works just fine. There must be some kind of build and install convention
> going on that I am not familiar with. (I'm not familiar with a lot of
> these build processes, actually.)
>
> Best - Eliot
I also forget the details from time to time...
Marco
next prev parent reply other threads:[~2020-03-21 13:29 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-01 21:46 Eliot Moss
2020-03-04 13:32 ` Mark Geisert
2020-03-16 23:34 ` Mark Geisert
2020-03-19 10:14 ` Eliot Moss
2020-03-19 10:41 ` Marco Atzeri
2020-03-19 23:29 ` Mark Geisert
2020-03-20 5:54 ` Mark Geisert
2020-03-20 10:29 ` Eliot Moss
2020-03-20 21:42 ` Andrey Repin
2020-03-20 13:39 ` Yaakov Selkowitz
2020-03-21 1:46 ` Eliot Moss
2020-03-21 8:37 ` Mark Geisert
2020-03-21 10:24 ` Eliot Moss
2020-03-21 11:07 ` Eliot Moss
2020-03-21 13:29 ` Marco Atzeri [this message]
2020-03-21 14:26 ` Roumen Petrov
2020-03-21 23:13 ` Eliot Moss
2020-03-22 4:10 ` Eliot Moss
2020-03-22 5:20 ` Eliot Moss
2020-03-24 8:09 ` Mark Geisert
2020-03-24 8:16 ` Eliot Moss
2020-03-22 20:09 ` Yaakov Selkowitz
2020-03-21 4:59 ` Eliot Moss
2020-03-21 8:18 ` Mark Geisert
2020-03-21 16:41 ` Brian Inglis
2020-03-23 9:31 ` Corinna Vinschen
2020-03-23 9:42 ` Mark Geisert
2020-03-23 18:48 ` Brian Inglis
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=84e61507-aece-22d0-e956-0436d083d25c@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).