Date: Sun, 2 Oct 2022 23:26:54 +0200 From: Tomek CEDRO <tomek@cedro.info> To: Hans Petter Selasky <hps@selasky.org> Cc: "freebsd-usb@FreeBSD.org" <usb@freebsd.org> Subject: Re: hackrf / libusb / libusb_interrupt_event_handler Message-ID: <CAFYkXjmSifQD1A1JmsCv4WQD7QqZ1aGBScSxKPqpV53WFf079g@mail.gmail.com> In-Reply-To: <CAFYkXjkkE5PhaMJZ7NyPrjAgLJfx7Wf0EAkaXt0sD1jNUpDzYg@mail.gmail.com> References: <CAFYkXjnKEf=pZ86s4JmaMxvT5s5hpmZs_Kfp1dQ4cOQ-JZpMaQ@mail.gmail.com> <d63d28c0-5542-977e-1fb6-56ea6a5dadad@selasky.org> <CAFYkXjkkE5PhaMJZ7NyPrjAgLJfx7Wf0EAkaXt0sD1jNUpDzYg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Oct 2, 2022 at 8:09 PM Tomek CEDRO wrote: > On Sun, Oct 2, 2022 at 5:43 PM Hans Petter Selasky wrote: > > On 10/2/22 16:23, Tomek CEDRO wrote: > > > Hello HPS :-) > > > The new release of HackRF is out 2022.09.1, I would like to update the > > > port.. however there is a linking problem with libusb: > > > > > > ld: error: ../../libhackrf/src/libhackrf.so.0.7.0: undefined reference > > > to libusb_interrupt_event_handler [--no-allow-shlib-undefined] > > > > > > Indeed this function seems missing in our libusb implementation? > > > % nm -gDC /usr/lib/libusb.so.3 | grep libusb_interrupt_event_handler > > > % > > > Any clues on how to fix? :-) > > > > https://cgit.freebsd.org/src/commit/?id=aa87aa52326be7b726664dba65e91ec3d8160f48 > > > > If the function doesn't exist, then you can comment it out. I see hackrf > > will work also w/o this implemented. > > > > I couldn't bump the LIBUSB version, because I don't have overview what > > else I need to implement then. > > --HPS > > Wow, so the fix is already in the source tree!! ? Then it will have to > propagate to STABLE and then RELEASE ? I can confirm that Your patch fixes the issue, enables the 2022.09.1 build and operations! I have managed to flash firmware (hackrf_spiflash), read device info (hackrf_info), sweep some radio frequencies (hackrf_sweep) and receive/transmit (hackrf_transfer). Thank you HPS :-) When it will be safe to provide port update 2022.09.1 to the port tree? Should we create a separate comms/hackrf-2021.03.1 port for the older systems where this LibUSB call is not available? Or maybe it will be possible to build and update LibUSB on the older systems? > I will bump the port to 2021.03.1 for now and when libusb is in the > Release we could bump it further to 2022.09.1? What do you suggest? Port update to 2021.03.1 is ready: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266774 https://github.com/freebsd/freebsd-ports/pull/132 Thank you HPS!! :-) Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFYkXjmSifQD1A1JmsCv4WQD7QqZ1aGBScSxKPqpV53WFf079g>