Date: Mon, 10 Feb 2014 11:06:27 +0000 From: "Bjoern A. Zeeb" <bz@FreeBSD.org> To: "Wojciech A. Koszek" <wkoszek@FreeBSD.org> Cc: freebsd-emulation@FreeBSD.org, Juergen Lock <nox@jelal.kn-bremen.de>, freebsd-usb@FreeBSD.org, hselasky@FreeBSD.org Subject: Re: CFT: Re: linux libusb again, I made an updated port... Message-ID: <D4F77E00-748A-4F18-AC39-3821380D13AA@FreeBSD.org> In-Reply-To: <20140210041845.GG12994@FreeBSD.org> References: <20140207201208.GA59695@enceladus10.kn-bremen.de> <20140207204928.GD12994@FreeBSD.org> <20140208084546.GA74796@enceladus10.kn-bremen.de> <20140209025624.GE12994@FreeBSD.org> <20140209135905.GA13024@enceladus10.kn-bremen.de> <20140210041845.GG12994@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 10 Feb 2014, at 04:18 , Wojciech A. Koszek <wkoszek@FreeBSD.org> = wrote: > On nie, lut 09, 2014 at 02:59:06 +0100, Juergen Lock wrote: >> On Sun, Feb 09, 2014 at 02:56:24AM +0000, Wojciech A. Koszek wrote: >>> On sob, lut 08, 2014 at 09:45:46 +0100, Juergen Lock wrote: >>>> On Fri, Feb 07, 2014 at 08:49:28PM +0000, Wojciech A. Koszek wrote: >>>>> On pi??, lut 07, 2014 at 09:12:08 +0100, Juergen Lock wrote: >>>>>> Hi! >>>>>>=20 >>>>>> This came up on irc so I tried to build a linux libusb port = (before >>>>>> I learned about ports/146895), mine uses linux_base-gentoo-stage3 >>>>>> like linux_kdump with a src/lib/libusb head snapshot so it's more >>>>>> up to date than wkoszek's build (ports/146895), and it's really >>>>>> easy to update it again. Also maybe it can be used as linux >>>>>> libusb-1.0.so too; I didn't actually test it tho. >>>>>>=20 >>>>>> Should this be committed? Is wkoszek's version better since it >>>>>> also builds on < 10.x? Comments welcome... >>>>>>=20 >>>>>> wkoszek's version: >>>>>>=20 >>>>>> http://www.freebsd.org/cgi/query-pr.cgi?pr=3D146895 >>>>>>=20 >>>>>> Mine: >>>>>>=20 >>>>>> http://people.freebsd.org/~nox/tmp/linux_libusb.shar >>>>>>=20 >>>>>> Distfile: >>>>>>=20 >>>>>> = http://people.freebsd.org/~nox/tmp/distfiles/linux_libusb-11.0r261448.tar.= bz2 >>>>>>=20 >>>>>> 10/amd64 package: >>>>>>=20 >>>>>> = http://people.freebsd.org/~nox/tmp/packages/10amd64/linux_libusb-11.0r2614= 48.txz >>>>>>=20 >>>>>> (built via: >>>>>>=20 >>>>>> poudriere bulk -v -j 10amd64 -p custom devel/linux_libusb >>>>>>=20 >>>>>> - btw for some reason the dependency = emulators/linux_base-gentoo-stage3 >>>>>> doesn't build for 10i386 in poudriere bulk, I get a pkg segfault. = bapt >>>>>> Cc'd...) >>>>>>=20 >>>>>=20 >>>>> Juergen, >>>> Hi! >>>>>=20 >>>>> What would be the reason for this update? >>>>>=20 >>>>> My stuff may be out of date, but it was all tested and working. I = verified >>>>> it with Linux'ish lsusb(1) and USB-based FPGA JTAG programmer, for = which >>>>> this stuff was written. >>>>>=20 >>>> I was just thinking an updated version may be useful, but if it's >>>> already working for everyone maybe less so... >>>>=20 >>>> Or would it work as a linux libusb-1.0.so too? I know the libusb = 1.0 >>>> stuff added some functions since 9.x at least... maybe hps would = know >>>> (Cc'd.) >>>>=20 >>>=20 >>> Juergen, >>>=20 >>> I think this package is useful and is looking for maintainer, so if = you have >>> time and energy, I'm OK with upgrading it, but I suggest testing it = first. >>> Bjoern might be interested too. >>>=20 >> You mean bz@ ? Cc'd. I tried testing lsusb from debian sid but it = printed >> nothing, neither with my nor with your older version, but maybe it's = just >> `too new' for our current linuxolator. >=20 > I assume you have at least 1 USB device while trying this. I don't = remember > exactly, but while trying within Linuxolator, you may need = devfs/procfs to > be mounted under Linuxolator's root directory. My understanding and from looking at trace is that if we cannot find it = in /compat/linux we ale search in /; so no need for an extra mount = unless maybe you run chrooted. > So you'll have to figure this out. >=20 > Does it return with 0 exit code? >=20 > If not, lsusb should be simple enough to let you place printf() all = over the > place and understand out when it's failing.=20 For me the problem was a clock_gettime() call in the libusb which my = glibc did not provide. That made all things fail (silently) until I = used linux =93rtld" tracing to see the unresolved symbol from libusb/the = commercial 3rd party software dynamically loading libusb. =97=20 Bjoern A. Zeeb ????????? ??? ??????? ??????: '??? ??? ???? ?????? ??????? ?? ?? ??????? ??????? ??? ????? ????? ???? ?????? ?? ????? ????', ????????? ?????????, "??? ????? ?? ?????", ?.???
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?D4F77E00-748A-4F18-AC39-3821380D13AA>