I installed GNU Radio 3.10.3 using Homebrew on my M1 MacBook Air last night.  
Seems to work pretty well for my needs.

Royce

> On Aug 12, 2022, at 10:20 AM, Michael Dickens <michael.dick...@ettus.com> 
> wrote:
> 
> I don't know if we'll have GNU Radio 3.10 as the default in MacPorts by 
> GRCon22. Lots of work to do there, mostly getting GR OOT modules updated to 
> compatible versions or removed if there isn't such a version. We'll see how 
> much progress we can make ... 6.5 weeks away, so not impossible ... - MLD
> 
> On Fri, Aug 12, 2022 at 10:26 AM Royce Connerley <royceconner...@yahoo.com 
> <mailto:royceconner...@yahoo.com>> wrote:
> Michael:
> 
> I would second the vote for 3.10.  Do you think this will be ready by GR 
> Con22?
> 
> Royce
> 
>> On May 25, 2022, at 10:52 AM, Price, Rodney D. <price-rod...@zai.com 
>> <mailto:price-rod...@zai.com>> wrote:
>> 
>> About the version of gnuradio: speaking only for myself, I would prefer to 
>> see the 3.10 version packaged. I don’t use many OOT blocks. Others may have 
>> a different opinion. I’m not that set on 3.10, however. Packaging 3.9 would 
>> be fine by me if others prefer it.
>>  
>> Thanks for doing this,
>> -Rod
>>  
>> From: Michael Dickens [mailto:michael.dick...@ettus.com 
>> <mailto:michael.dick...@ettus.com>] 
>> Sent: Tuesday, May 24, 2022 1:55 PM
>> To: Ryan Volz
>> Cc: Price, Rodney D.; discuss-gnuradio@gnu.org 
>> <mailto:discuss-gnuradio@gnu.org>
>> Subject: EXTERNAL: Re: GNU Radio on Mac M1
>>  
>> Related to this general topic -- GR on ARM64:
>>  
>> The MacPorts maintainers of GR are soon going to update the main "gnuradio" 
>> port ... we're proposing to the current 3.10 release. It is a pain to 
>> maintain more than 1 related port, and we were waiting for many GR OOT 
>> modules to be updated before we did this main update. Would folks prefer GR 
>> 3.9 instead of GR 3.10? I think most GR OOT are ported to GR 3.9 by now ... 
>> more than for 3.10, but I'm sure not all have been ported yet. I'm curious 
>> folks thoughts here.
>>  
>> Also: Can someone provide more details of the CMake install issue? I thought 
>> all of the required files were installed into the correct directory for 
>> CMake to find them.
>> ---
>> Dr Michael L Dickens
>> Principal NI/Ettus Technical Support Engineer
>>  
>>  
>> On Tue, May 24, 2022 at 3:23 PM Ryan Volz <ryan.v...@gmail.com 
>> <mailto:ryan.v...@gmail.com>> wrote:
>> Hi Rod,
>> 
>> I have a positive report from a colleague who is running radioconda on 
>> an M1 through rosetta with the non-arm64 build. He also reports 
>> instability with GRC when trying to run the native arm64 packages, so I 
>> think your best shot might be trying the former with rosetta. (Another 
>> thing to consider is that gr-qtgui does not exist yet for arm64, since 
>> conda-forge is still struggling to get the Qt ecosystem built. It has 
>> been seemingly imminent for 6 months now, so I've stopped holding my 
>> breath.) Miniconda vs. radioconda should not matter, except for 
>> convenience in reinstalling if you want to wipe away your whole conda 
>> installation. I'm not sure in what ways the various packaging methods 
>> would interfere with each other's Python installations, but removing 
>> anything you don't need and keeping things minimal is always a good plan.
>> 
>> Cheers,
>> Ryan
>> 
>> On 5/24/22 12:19 PM, Price, Rodney D. wrote:
>> > Ryan,
>> > 
>> > Thanks for your reply. I looked through the Mac OS X bug reports and 
>> > didn't see anything that looked relevant to my case. The problem isn't 
>> > necessarily connected to GRC. The Macports install seems to be missing 
>> > some essential cmake files (i.e. GrSwig and dependencies). The conda 
>> > install would be preferable, anyway. I'm beginning to wonder about m=y 
>> > miniconda install: I have found multiple Python installs around my system, 
>> > and after removing all my homebrew packages and replacing some with 
>> > macports versions, I wonder if the Python libraries that GNU Radio uses 
>> > might not be the ones that GNU Radio expects. I'm considering removing 
>> > miniconda and replacing it with radioconda. What do you think? Is that 
>> > likely to work on a Mac?
>> > 
>> > Thanks,
>> > -Rod
>> > 
>> > -----Original Message-----
>> > From: Ryan Volz [mailto:ryan.v...@gmail.com <mailto:ryan.v...@gmail.com>]
>> > Sent: Monday, May 23, 2022 11:21 AM
>> > To: Price, Rodney D.; discuss-gnuradio@gnu.org 
>> > <mailto:discuss-gnuradio@gnu.org>
>> > Subject: EXTERNAL: Re: GNU Radio on Mac M1
>> > 
>> > Hi Rod,
>> > 
>> > I think your experience is common, unfortunately, and part of the
>> > problem is that there are multiple bugs to work through and not all of
>> > them are necessarily with GRC itself. There are multiple dimensions in
>> > which things are failing (new vs. old macOS version, switch to arm64,
>> > standard DPI display vs. high DPI [Retina] display), so providing as
>> > many details about your system as you can would be helpful. As the
>> > person putting out the conda packages, it saddens me that I haven't been
>> > able to sort through enough of the bugs to get something working for 
>> > people.
>> > 
>> > So, what particular issues are you seeing with the conda install? There
>> > are a few bugs tagged for "Mac OS X" on the GNU Radio Github: do any of
>> > those apply?
>> > 
>> > One thing a recent report has brought to my attention is a possible bug
>> > in conda-forge's cairo package. If you're seeing crashes that might have
>> > to do with cairo (e.g. GRC crashes), you could try installing a patched
>> > cairo package that I have available on my channel:
>> > 
>> > conda install -c ryanvolz/label/bigsur-patch cairo
>> > 
>> > Cheers,
>> > Ryan
>> > 
>> > On 5/23/22 12:33 PM, Price, Rodney D. wrote:
>> >> I've been trying to get a good install of GNU Radio on a Mac M1 (ARM64)
>> >> running Monterey, using several methods. I've tried installing via
>> >> Homebrew, which gave me an install that crashed GRC constantly. I've
>> >> tried conda install (I have miniconda installed) without success. My
>> >> latest attempt is with Macports, which gives me a working GRC, but when
>> >> I attempt to run cmake in the OOT module source, cmake can't find
>> >> GrSwig, so I go online to find a GrSwig.cmake, which then leads to
>> >> another error on LIBTOOL.
>> >>
>> >> This is not to complain, but I would really like to avoid going down
>> >> some rabbit hole on an install that in the end, just won't work.
>> >> Macports' gnuradio is version 3.8, and I would like something more up to
>> >> date. Playing nicely with conda would be nice as well.
>> >>
>> >> So I'm asking for advice on the current state of GNU Radio on Macs with
>> >> the Apple ARM chip. Have others been able to get a working install of
>> >> GNU Radio on this system? What's the current best approach for 3.9 or 
>> >> 3.10?
>> >>
>> >> Thanks,
>> >>
>> >> -Rod
>> >>
>> >> ------------------------------------------------------------------------
>> >> This message is intended only for the use of the individual or entity to
>> >> which it is addressed and may contain ZETA Associates confidential or
>> >> proprietary information. If you are not the intended recipient, any use,
>> >> dissemination, or distribution of this communication is prohibited. If
>> >> you have received this communication in error, please notify the sender
>> >> and delete all copies.
>> > ________________________________
>> >   This message is intended only for the use of the individual or entity to 
>> > which it is addressed and may contain ZETA Associates confidential or 
>> > proprietary information. If you are not the intended recipient, any use, 
>> > dissemination, or distribution of this communication is prohibited. If you 
>> > have received this communication in error, please notify the sender and 
>> > delete all copies.
>> > 
>> 
>> This message is intended only for the use of the individual or entity to 
>> which it is addressed and may contain ZETA Associates confidential or 
>> proprietary information. If you are not the intended recipient, any use, 
>> dissemination, or distribution of this communication is prohibited. If you 
>> have received this communication in error, please notify the sender and 
>> delete all copies.
> 

Reply via email to