X-Recipient:	archive-cygwin AT delorie DOT com
X-Original-To:	cygwin AT cygwin DOT com
Delivered-To:	cygwin AT cygwin DOT com
DMARC-Filter:	OpenDMARC Filter v1.3.2 sourceware.org 1023C385C019
Authentication-Results:	sourceware.org;
	dmarc=none (p=none dis=none) header.from=cs.umass.edu
Authentication-Results:	sourceware.org;
	spf=pass smtp.mailfrom=moss AT cs DOT umass DOT edu
Subject:	Re: Why is taskset still not in util-linux?
To:	cygwin <cygwin AT cygwin DOT com>
References:	<1348011a-261a-2a87-d361-4e51fa8dc19f AT cs DOT umass DOT edu>
	<85ae12aa-6cc3-5d4c-5df2-25bf811ec6a9 AT maxrnd DOT com>
	<72fea68a-b3d7-e87c-726f-8a5a2587a992 AT maxrnd DOT com>
	<01e3d337-e5fe-f393-7634-3f1881bca315 AT cs DOT umass DOT edu>
	<dca24f26-9da9-591c-19c1-8020e5de3a4e AT maxrnd DOT com>
	<79d7afa5-a07b-04df-c259-b76c61390f8c AT maxrnd DOT com>
	<c075b981d41ff880e0af76c853e764c468b9c6de DOT camel AT cygwin DOT com>
	<dd8104f5-4a76-1ff3-f769-69154991aa80 AT cs DOT umass DOT edu>
	<f50b2040-c29f-9983-9bce-d1c33fb4bae7 AT maxrnd DOT com>
From:	Eliot Moss <moss AT cs DOT umass DOT edu>
Message-ID:	<4c782f2b-c9f0-cd81-cb8d-f874ddc92fa8@cs.umass.edu>
Date:	Sat, 21 Mar 2020 06:24:37 -0400
User-Agent:	Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101
	Thunderbird/68.6.0
MIME-Version:	1.0
In-Reply-To:	<f50b2040-c29f-9983-9bce-d1c33fb4bae7@maxrnd.com>
X-Spam-Status:	No, score=-6.0 required=5.0 tests=BAYES_00, JMQ_SPF_NEUTRAL,
	KAM_DMARC_STATUS, SPF_HELO_NONE, SPF_PASS,
	TXREP autolearn=no autolearn_force=no version=3.4.2
X-Spam-Checker-Version:	SpamAssassin 3.4.2 (2018-09-13) on
	server2.sourceware.org
X-BeenThere:	cygwin AT cygwin DOT com
X-Mailman-Version:	2.1.29
List-Id:	Cygwin mailing list <cygwin.cygwin.com>
List-Unsubscribe:	<http://cygwin.com/mailman/options/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
List-Archive:	<http://cygwin.com/pipermail/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe:	<http://cygwin.com/mailman/listinfo/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
Reply-To:	moss AT cs DOT umass DOT edu
Errors-To:	cygwin-bounces AT cygwin DOT com
Sender:	"Cygwin" <cygwin-bounces AT cygwin DOT 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
--
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple

- Raw text -