From: Eliot Moss <moss@cs.umass.edu>
To: cygwin <cygwin@cygwin.com>
Subject: Re: Why is taskset still not in util-linux?
Date: Sat, 21 Mar 2020 06:24:37 -0400 [thread overview]
Message-ID: <4c782f2b-c9f0-cd81-cb8d-f874ddc92fa8@cs.umass.edu> (raw)
In-Reply-To: <f50b2040-c29f-9983-9bce-d1c33fb4bae7@maxrnd.com>
Dear Mark - I am confused by how your build goes through when configure
detects the ionice does not have the ioprio_set/get calls that it needs. In my
case configure stops at that point. That was why I made a patch to
configure.ac so that cygport could explicitly exclude ionice. At the moment,
I am seeing what happens if I add more "fake" syscalls to syscall.h for those
two calls. The configure goes through (as expected), but of course ionice
fails to link (no 'syscall" function).
If I revert to having only SYS_sched_getaffinity defined, configure stops
with:
checking for syscall ioprio_set... no
configure: WARNING: Unable to detect syscall ioprio_set.
configure: error: ionice selected but ioprio_set syscall not found
*** ERROR: configure failed
That why I think I/we need some kind of patch to configure.ac. How does
your build manage to continue?
I am working from the Cygwin util-linux-2.33.1-1 source package. Is that the
correct one? Also, I am in the x86-64 world for all this.
Eliot
next prev parent reply other threads:[~2020-03-21 10:24 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 [this message]
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=4c782f2b-c9f0-cd81-cb8d-f874ddc92fa8@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).