From: Eliot Moss <moss@cs.umass.edu>
To: cygwin@cygwin.com
Subject: Re: Why is taskset still not in util-linux?
Date: Fri, 20 Mar 2020 06:29:34 -0400 [thread overview]
Message-ID: <205bb6db-81d0-3530-2c5c-8ea76351e9a0@cs.umass.edu> (raw)
In-Reply-To: <79d7afa5-a07b-04df-c259-b76c61390f8c@maxrnd.com>
On 3/20/2020 1:54 AM, Mark Geisert wrote:
> Mark Geisert wrote:
>> Eliot Moss wrote:
>> Rats. Sorry you've hit some snags. Are you compiling directly with 'make' or the preferred
>> 'cygport util-linux.cygport build'? With the latter I didn't need to make any changes to the
>> source tree; all mods were accomplished with the new patch file and changes to util-linux.cygport
>> itself.
>
> I've reproduced your snags. It/they are due to my having forgotten another tiny update that should
> have been part of the 2.33.1-cygwin-cpuset.patch file. If you 'echo "#define SYS_sched_getaffinity
> 42" > /usr/local/include/sys/syscall.h' and then back out your other fix attempts, the build using
> cygport should work.
What an amusing hack! I especially like the sensibility of 42! :-)
I will try this. When I built it last night, I got a successful compile, but it didn't do anything.
For example, taskset 1 ls did not output _anything_ -- no error message and no ls output :-( ...
It will be the weekend here in Australia (I'm visiting, and wondering about exactly how and when I
will get home) so maybe I'll play with it some more on Saturday ...
Regards - Eliot
next prev parent reply other threads:[~2020-03-20 10: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 [this message]
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
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=205bb6db-81d0-3530-2c5c-8ea76351e9a0@cs.umass.edu \
--to=moss@cs.umass.edu \
--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).