From: Eliot Moss <moss@cs.umass.edu>
To: Mark Geisert <mark@maxrnd.com>, cygwin <cygwin@cygwin.com>
Subject: Re: Why is taskset still not in util-linux?
Date: Tue, 24 Mar 2020 04:16:52 -0400 [thread overview]
Message-ID: <33fc06f7-704c-2728-4fd9-085eaba22db0@cs.umass.edu> (raw)
In-Reply-To: <fc08b1da-2883-7a29-c670-60dbebe56049@maxrnd.com>
On 3/24/2020 4:09 AM, Mark Geisert wrote:
> Eliot Moss wrote:
>> Well, I had _thought_ I had done 'cygport install' and run the installed
>> version, but I seem to have been wrong. I seem to have manually over-written
>> the proper (stripped) binary with the wrapper!
>>
>> Anyway, I've got the whole thing working and offer the attached patches for
>> "thoughtful consideration". I have done away with the need to create an empty
>> or fake /usr/local/include/sys/syscall.h and changed the source of the
>> relevant programs to conditional #include <sys/syscall.h> on #indef
>> __CYGWIN__, which sruck me as more legitimate (the file in questions is
>> patched anyway). And I improved configure.ac so that the programs controlled
>> by --enable-schedutils are more independent and can fail individually without
>> failing the build. Part of that was subtituting, as a patch to configure.ac,
>> a check for the sched_getaffinity and sched_setaffinity calls in place of the
>> check for the corresponding syscall. The whole builds and installs. I can
>> provide the packaged up version (I assume that is the 'dist' hierarchy) if
>> that would be helpful.
>
> Thanks very much for working on all this and contributing it. I will build and test as soon as I
> can. I need to research the packaging steps because I intend to ITA this package. I do also want
> to take another look at the other programs built as part of --enable-schedutils; they might (or
> might not) build cleanly but AFAIK there's no support within Cygwin and/or Windows for what they can
> do on Linux.
Agreed - glad to help! Eliot
next prev parent reply other threads:[~2020-03-24 8:16 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
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 [this message]
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=33fc06f7-704c-2728-4fd9-085eaba22db0@cs.umass.edu \
--to=moss@cs.umass.edu \
--cc=cygwin@cygwin.com \
--cc=mark@maxrnd.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).