From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:41936) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VlZ0J-0002tS-Fy for qemu-devel@nongnu.org; Wed, 27 Nov 2013 01:53:49 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VlZ0C-0006EF-8H for qemu-devel@nongnu.org; Wed, 27 Nov 2013 01:53:43 -0500 Received: from mx1.redhat.com ([209.132.183.28]:23533) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VlZ0C-0006BP-03 for qemu-devel@nongnu.org; Wed, 27 Nov 2013 01:53:36 -0500 Message-ID: <1385535210.13867.15.camel@nilsson.home.kraxel.org> From: Gerd Hoffmann Date: Wed, 27 Nov 2013 07:53:30 +0100 In-Reply-To: <5294CFD3.30609@rdsoftware.de> References: <1212720896.288966.1385477539659.open-xchange@email.1und1.de> <1385481464.10163.37.camel@nilsson.home.kraxel.org> <5294CFD3.30609@rdsoftware.de> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] git master: usb-host needs additional parameters - no documentation which List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Erik Rull Cc: "qemu-devel@nongnu.org" On Di, 2013-11-26 at 17:44 +0100, Erik Rull wrote: > Hi Gerd, > > I only have libusb (0.1 and 1.0) installed. Is there a chance to get an > error message a bit earlier - or a warning that the usb-host support was > disabled? configure doesn't print out a libusb - disabled message when not > passing the libusb-parameter. It lists libusb like everything else: [ ... ] xfsctl support no nss used yes libusb yes <==== usb net redir yes [ ... ] > I tried now explicitly with --enable-libusb - fails :-( Again standard configure behavior: If you explicitly ask for a feature and the dependencies are not found configure will error out (instead of silently disabling the feature). > I would like to point to a different version of libusb - my built machine > has the sources for the latest libusb but not in the location where it is > expected for a standard distribution... pkg-config is used for detection, so if you set PKG_CONFIG_PATH to include your custom location configure should find it. HTH, Gerd