A quick fix may be to change line 547 from:

*18*)

To:

*18*|*19*)

That may work, but could be some issues with packages. In that case you could 
add a new case statement for 19.

-Trip

From: Humphries, James R.
Sent: Monday, October 29, 2018 10:17 AM
To: 'Neel Pandeya' <neel.pand...@ettus.com>; John Ackermann N8UR <j...@febo.com>
Cc: GNURadio Discussion List <discuss-gnuradio@gnu.org>
Subject: RE: [Discuss-gnuradio] build-gnuradio.sh and Linux Mint 19

The build-gnuradio script doesn’t appear to have an entry for Mint 19 at the 
moment, I’m sure the maintainers would love a patch to add support 😊

-Trip

From: Discuss-gnuradio 
<discuss-gnuradio-bounces+humphriesjr=ornl....@gnu.org<mailto:discuss-gnuradio-bounces+humphriesjr=ornl....@gnu.org>>
 On Behalf Of Neel Pandeya
Sent: Monday, October 29, 2018 10:07 AM
To: John Ackermann N8UR <j...@febo.com<mailto:j...@febo.com>>
Cc: GNURadio Discussion List 
<discuss-gnuradio@gnu.org<mailto:discuss-gnuradio@gnu.org>>
Subject: Re: [Discuss-gnuradio] build-gnuradio.sh and Linux Mint 19

The "build-gnuradio" script is now being maintained on GitHub.

https://github.com/ccera-astro/build-gnuradio

--Neel Pandeya




On 29 October 2018 at 07:04, John Ackermann N8UR 
<j...@febo.com<mailto:j...@febo.com>> wrote:
I'm trying to run the current build-gnuradio.sh script from 
sbrac.org<http://sbrac.org> on a Linux Mint 19 machine and the script 
immediately fails, saying "Your Mint release must be at least Linux Mint 11 to 
proceed"

Is it safe to just bypass that check, or is there some sort of incompatibilty 
with v19?  Or is sbrac.org<http://sbrac.org> no longer the place to find the 
current version of the script?

Thanks,
John

_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org<mailto:Discuss-gnuradio@gnu.org>
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Reply via email to