all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Guillaume Le Vaillant <glv@posteo.net>
To: 38650@debbugs.gnu.org
Cc: christopher@librehacker.com
Subject: [bug#38650] [PATCH] gnu: adds hackrf
Date: Mon, 27 Apr 2020 17:33:52 +0200	[thread overview]
Message-ID: <871ro97xjz.fsf@yamatai> (raw)
In-Reply-To: <542784b9e65b06a69bf1cd17f10cf4343b411b8e.camel@qlfiles.net>

[-- Attachment #1: Type: text/plain, Size: 1421 bytes --]


Hi,

Christopher Howard <christopher.howard@qlfiles.net> skribis:

> I have asked many times about the new release over the last few months,
> and each time hackrf team says it is a week or so away. But their last
> git commit was in February. Requesting to please proceed with the
> latest commit as represented in this patch. I have added information to
> the description as requested.
>
> Using the old 2018 release would be unsatisfactory due to an annoying
> bug related to maintaining connections to hackrf devices.

I noticed that the package definition builds 'lib/libhackrf.a';
installing static libraries is usually disabled for Guix packages.
Also, some of the lines of the package definition are indented with tabs
instead of spaces, and the commit message is missing the
" * gnu/packages/radio.scm (hackrf): New variable." line.

> As an additional motivation for adding this, I believe you need
> libhackrf installed to use hackrf with gnuradio, through the osmocom
> interface. (I'm not at the moment quite clear on what exactly you have
> to enable in the gnuradio package definitions to link those together.)
> E.g., https://packages.debian.org/stretch/gr-osmosdr

In theory, adding the hackrf package as input of the gnuradio-osmosdr
package should be enough (the library should be auto-detected when
compiling and the support activated).
However, I don't have the hardware to test if it really works.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

  reply	other threads:[~2020-04-27 15:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-17 14:45 [bug#38650] hackrf: new package Christopher Howard
2019-12-23  8:00 ` Danny Milosavljevic
2019-12-24  7:05   ` Christopher Howard
2020-03-31 20:22     ` Christopher Baines
2020-04-01  0:12       ` Christopher Howard
2020-04-01 17:22         ` Christopher Baines
2019-12-23 21:17 ` [bug#38650] hackrf.scm add to gnu/local.mk Jack Hill
2020-04-26 11:06 ` [bug#38650] [PATCH] gnu: adds hackrf Christopher Howard
2020-04-27 15:33   ` Guillaume Le Vaillant [this message]
2020-04-28  0:20     ` Christopher Howard
2020-04-28  8:29       ` bug#38650: " Guillaume Le Vaillant

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=871ro97xjz.fsf@yamatai \
    --to=glv@posteo.net \
    --cc=38650@debbugs.gnu.org \
    --cc=christopher@librehacker.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.