GNUradio on Mac mini Big Sur M1 Install errors

[Dan Hinckley]

I’m not clever enough to understand these errors. If there is a remedy, can 
someone point me at solutions?

> sudo port install gnuradio
> Password:
> --->  Computing dependencies for glib2
> --->  Fetching archive for glib2
> --->  Attempting to fetch 
> glib2-2.62.6_0+universal+x11.darwin_20.arm64-x86_64.tbz2 from 
> https://packages.macports.org/glib2
> --->  Attempting to fetch 
> glib2-2.62.6_0+universal+x11.darwin_20.arm64-x86_64.tbz2 from 
> https://ywg.ca.packages.macports.org/mirror/macports/packages/glib2
> --->  Attempting to fetch 
> glib2-2.62.6_0+universal+x11.darwin_20.arm64-x86_64.tbz2 from 
> https://mse.uk.packages.macports.org/glib2
> --->  Fetching distfiles for glib2
> --->  Attempting to fetch glib-2.62.6.tar.xz from 
> http://mirror.cc.columbia.edu/pub/software/gnome/sources/glib/2.62/
> --->  Attempting to fetch glib-2.62.6.tar.xz from 
> https://distfiles.macports.org/glib2
> --->  Verifying checksums for glib2
> --->  Extracting glib2
> --->  Applying patches to glib2
> --->  Configuring glib2
> Warning: Configuration logfiles contain indications of 
> -Wimplicit-function-declaration; check that features were not accidentally 
> disabled:
>   isnanf: found in build-x86_64/meson-logs/meson-log.txt
> --->  Building glib2
> --->  Staging glib2 into destroot
> Error: Failed to destroot glib2: glib-2.0.pc differs in 
> /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_glib2/glib2/work/destroot-arm64//opt/local/lib/pkgconfig
>  and 
> /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_glib2/glib2/work/destroot-ppc-intel//opt/local/lib/pkgconfig
>  and cannot be merged
> Error: See 
> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_glib2/glib2/main.log
>  for details.
> Error: Unable to execute port: upgrade cairo failed

Re: Conflicty between MacPorts and Anaconda

[Mircea Trandafir]

I have anaconda and Macports installed side-by-side, with different versions of 
python in each of them. It all runs smoothly, so it can be done. And I also 
have MacTeX installed separately, again without any issues with interaction 
with anaconda. As Ryan said, we need more information to figure out what is the 
problem with your setup.

--
Mircea Trandafir
Associate professor
Department of Business and Economics
University of Southern Denmark
Campusvej 55, 5230 Odense M
Denmark
Email: mircea.tranda...@sam.sdu.dk
Web: http://www.mirceatrandafir.com

On Aug 31, 2021, at 12:54 PM, Ryan Schmidt  wrote:

On Aug 30, 2021, at 09:32, Gerben Wierda wrote:

I had to install Anaconda (Python environment) to collaborate with someone. I 
installed, but it adapted my shell environment in such a way that I’ve lost 
MacPorts (and LMTX ConTeXt). Does anybody have experience with the combination 
of Anaconda and MacPorts and what the correct way is to use them side by side?

I don't know anything about Anaconda...

When you say you've "lost MacPorts" does that mean that when you type "port" 
something it says the command is not found? If so, that means that your PATH 
environment variable is not set up correctly. When you installed MacPorts, it 
edited your shell startup script (which varies depending on which SHELL you are 
using) to add the MacPorts paths /opt/local/bin and /opt/local/sbin to PATH, 
while preserving any other additions you made. Maybe the Anaconda installer 
also modified the PATH in that same shell startup file but did not preserve 
your other PATH modifications. Or if you are using the Bash shell, which 
supports I think three possible startup files, maybe Anaconda edited a 
different one, one which takes precedence and causes Bash to ignore the other 
startup file that contained your MacPorts PATH settings.

Re: Conflicty between MacPorts and Anaconda

[Gerben Wierda via macports-users]

Yes, Anaconda overwrote the PATh settings by creating a .bash_profile file (and 
editing several others). The way it does this happens deep in some python 
scripts (e.g. changing shell prompts happen as well). The thing is invasive.

I have removed it from my system.

Gerben Wierda (LinkedIn )
R&A Enterprise Architecture  (main site)
Book: Chess and the Art of Enterprise Architecture 
Book: Mastering ArchiMate 

> On 31 Aug 2021, at 11:54, Ryan Schmidt  wrote:
> 
> On Aug 30, 2021, at 09:32, Gerben Wierda wrote:
>> 
>> I had to install Anaconda (Python environment) to collaborate with someone. 
>> I installed, but it adapted my shell environment in such a way that I’ve 
>> lost MacPorts (and LMTX ConTeXt). Does anybody have experience with the 
>> combination of Anaconda and MacPorts and what the correct way is to use them 
>> side by side?
> 
> I don't know anything about Anaconda...
> 
> When you say you've "lost MacPorts" does that mean that when you type "port" 
> something it says the command is not found? If so, that means that your PATH 
> environment variable is not set up correctly. When you installed MacPorts, it 
> edited your shell startup script (which varies depending on which SHELL you 
> are using) to add the MacPorts paths /opt/local/bin and /opt/local/sbin to 
> PATH, while preserving any other additions you made. Maybe the Anaconda 
> installer also modified the PATH in that same shell startup file but did not 
> preserve your other PATH modifications. Or if you are using the Bash shell, 
> which supports I think three possible startup files, maybe Anaconda edited a 
> different one, one which takes precedence and causes Bash to ignore the other 
> startup file that contained your MacPorts PATH settings.
> 

Re: Big Sur on M1 - bind9 named daemon don't run

[FritzS GMX]

> Am 31.08.2021 um 11:51 schrieb Ryan Schmidt :
> 
> On Aug 25, 2021, at 02:00, FritzS GMX wrote:
> 
>> after migration from my profile & apps from ElCapitan to Big Sur I 
>> reinstalled all the MacPorts programs,
>> bind9 are new compiled on my MacMini M1 too.
>> 
>> But the named daemon don't run. 
>> 
>> All this commands don’t work:
>> 
>> sudo launchctl load -wF /Library/LaunchDaemons/org.macports.bind9.plist
>> 
>> sudo /opt/local/bin/port load bind9
>> 
>> sudo /opt/local/sbin/rndc reload
>> 
>> What must I do that the named daemon runs?
> 
> Why don't the above commands work? What happens?
> 
> If you were expecting a process to be running after running those commands, 
> and that process is not running, is it crashing? Is the OS creating crash 
> logs in the usual directory? If so, show us one. Or, if no crash logs, does 
> the Console indicate that the process is being restarted every 10 seconds and 
> immediately quitting itself? Does the process write its own log file, and if 
> so, does it contain anything explaining why it isn't staying running?
> 

No, there are no inputs in the own bind9 logging files, no logging files 
available.

Named are allowed in the firewall.

/opt/local/var/run/named/session.key are available and have a actual timestamp

[code]
sudo /opt/local/sbin/rndc-confgen -a
wrote key file "/opt/local/etc/rndc.key“
[/code

named.pid are not seen on this path
[code]
dnssec-validation auto;

pid-file "/opt/local/var/run/named/named.pid";
[/code]

Hint from
https://developer.apple.com/library/archive/documentation/Security/Conceptual/CodeSigningGuide/Procedures/Procedures.html

[code]
sudo spctl --assess --type execute /opt/local/sbin/named
objc[15229]: Class SPExecutionPolicy is implemented in both 
/System/Library/PrivateFrameworks/SystemPolicy.framework/Versions/A/SystemPolicy
 and /usr/sbin/spctl. One of the two will be used. Which one is undefined.
objc[15229]: Class AppWrapper is implemented in both 
/System/Library/PrivateFrameworks/SystemPolicy.framework/Versions/A/SystemPolicy
 and /usr/sbin/spctl. One of the two will be used. Which one is undefined.
objc[15229]: Class AppWrapperPolicyResult is implemented in both 
/System/Library/PrivateFrameworks/SystemPolicy.framework/Versions/A/SystemPolicy
 and /usr/sbin/spctl. One of the two will be used. Which one is undefined.
objc[15229]: Class AppWrapperPolicy is implemented in both 
/System/Library/PrivateFrameworks/SystemPolicy.framework/Versions/A/SystemPolicy
 and /usr/sbin/spctl. One of the two will be used. Which one is undefined.
objc[15229]: Class SPLog is implemented in both 
/System/Library/PrivateFrameworks/SystemPolicy.framework/Versions/A/SystemPolicy
 and /usr/sbin/spctl. One of the two will be used. Which one is undefined.
objc[15229]: Class MIS is implemented in both 
/System/Library/PrivateFrameworks/SystemPolicy.framework/Versions/A/SystemPolicy
 and /usr/sbin/spctl. One of the two will be used. Which one is undefined.
objc[15229]: Class SPExecutionHistoryItem is implemented in both 
/System/Library/PrivateFrameworks/SystemPolicy.framework/Versions/A/SystemPolicy
 and /usr/sbin/spctl. One of the two will be used. Which one is undefined.
objc[15229]: Class SPExecutionPolicyItem is implemented in both 
/System/Library/PrivateFrameworks/SystemPolicy.framework/Versions/A/SystemPolicy
 and /usr/sbin/spctl. One of the two will be used. Which one is undefined.
objc[15229]: Class SPDeveloperPolicy is implemented in both 
/System/Library/PrivateFrameworks/SystemPolicy.framework/Versions/A/SystemPolicy
 and /usr/sbin/spctl. One of the two will be used. Which one is undefined.
objc[15229]: Class GKScanResult is implemented in both 
/System/Library/PrivateFrameworks/SystemPolicy.framework/Versions/A/SystemPolicy
 and /usr/sbin/spctl. One of the two will be used. Which one is undefined.
/opt/local/sbin/named: rejected
[/code]

[code]
spctl --assess --verbose=4  /opt/local/sbin/named   
  
objc[16419]: Class SPExecutionPolicy is implemented in both 
/System/Library/PrivateFrameworks/SystemPolicy.framework/Versions/A/SystemPolicy
 and /usr/sbin/spctl. One of the two will be used. Which one is undefined.
objc[16419]: Class AppWrapper is implemented in both 
/System/Library/PrivateFrameworks/SystemPolicy.framework/Versions/A/SystemPolicy
 and /usr/sbin/spctl. One of the two will be used. Which one is undefined.
objc[16419]: Class AppWrapperPolicyResult is implemented in both 
/System/Library/PrivateFrameworks/SystemPolicy.framework/Versions/A/SystemPolicy
 and /usr/sbin/spctl. One of the two will be used. Which one is undefined.
objc[16419]: Class AppWrapperPolicy is implemented in both 
/System/Library/PrivateFrameworks/SystemPolicy.framework/Versions/A/SystemPolicy
 and /usr/sbin/spctl. One of the two will be used. Which one is undefined.
objc[16419]: Class SPLog is implemented in both 
/System/Library/PrivateFrameworks/SystemPolicy.framework/Versions/A/SystemPol

Re: requested_variants='+universal' for port with no +universal variant?

[Ryan Schmidt]

On Aug 30, 2021, at 14:34, Jim DeLaHunt wrote:

> I am working through the Migration[1] procedure after upgrading my macOS 
> version. I made a list of my installed ports using `port -qv installed`. 
> Curiously, a number of the ports in that list include the notation 
> `requested_variants='+universal'`, even though the port appears to have no 
> +universal variant. For example,
> 
> bison @3.7.6_1+universal requested_variants='+universal' platform='darwin 17' 
> archs='x86_64' date='2021-07-04T14:08:44-0700'
> bison @3.7.6_2+universal (active) requested_variants='+universal' 
> platform='darwin 17' archs='x86_64' date='2021-08-12T18:44:11-0700'
> 
> But there appars to be no +universal variant:
> 
> % port info bison
> bison @3.7.6_2 (devel)
> Sub-ports:bison-runtime
> 
> Description:  Bison is a general-purpose parser generator that 
> converts an annotated context-free grammar into a deterministic LR
>   or generalized LR (GLR) parser employing LALR(1) parser 
> tables. As an experimental feature, Bison can also generate
>   IELR(1) or canonical LR(1) parser tables. Once you are 
> proficient with Bison, you can use it to develop a wide range
>   of language parsers, from those used in simple desk 
> calculators to complex programming languages.
> Homepage: https://www.gnu.org/software/bison
> 
> Extract Dependencies: xz
> Library Dependencies: gettext, libiconv, m4
> Runtime Dependencies: bison-runtime
> Platforms:darwin
> License:  (GPL-3+ or Permissive)
> Maintainers:  none
> % port info --variants bison
> variants:
> 
> Perhaps these +universal request are a relic of the distant past? I have 
> migrated this MacPorts installation forward through several OS versions and 
> multiple computers. It might be that some data originated on a PowerPC mac 
> long ago, when +universal was significant.
> 
> I have on MacPorts 2.7.1 and macOS 10.14 Mojave (just upgrade from 10.13 High 
> Sierra) and a 7-year-old Mac with an intel CPU.
> 
> The buildUniversal wiki page[2] seems to be 8 years old and not relevant to 
> my situation.
> 
> Q1. What does a `+universal` variant request do, on MacPorts 2.7.1 and macOS 
> 10.14 Mojave and a Mac with an intel CPU, if the port does not advertise a 
> `+universal` variant?
> 
> Q2. Is there a `+universal` variant which is built in to MacPorts, even if 
> the port does not advertise a `+universal` variant? MacPorts Guide, 5. 
> Portfile Reference, 5.5.1. User-Selected Variants[3] seems to imply "yes".
> 
> Q3. Are there ports which have a `+universal` variant which is important for 
> my system? How do I find this out, and understand the significance?
> 
> Q4. Should I edit my list of installed ports to remove the `+universal` from 
> the port identifier and requested_variants keyword? For instance, should I 
> change the bison entry from:
> 
> bison @3.7.6_1+universal requested_variants='+universal' platform='darwin 17' 
> archs='x86_64' date='2021-07-04T14:08:44-0700'
> bison @3.7.6_2+universal (active) requested_variants='+universal' 
> platform='darwin 17' archs='x86_64' date='2021-08-12T18:44:11-0700'
> 
> into:
> 
> bison @3.7.6_1 requested_variants='' platform='darwin 17' archs='x86_64' 
> date='2021-07-04T14:08:44-0700'
> bison @3.7.6_2 (active) requested_variants='' platform='darwin 17' 
> archs='x86_64' date='2021-08-12T18:44:11-0700'
> 
> Note: this list of installed ports had some entries with `archs='i386 
> x86_64'`. I already got rid of the `i386` arch entry.
> 
> [1] https://trac.macports.org/wiki/Migration
> [2] https://trac.macports.org/wiki/howto/buildUniversal
> [3] https://guide.macports.org/chunked/reference.variants.html

"Universal" means "build for more than one architecture". Most users don't need 
this for most ports, since most users are only installing their ports on one 
machine (one architecture) to use them on that one machine.

On Mac OS X 10.4 and 10.5, the default set of universal architectures is ppc 
i386.

On Mac OS X 10.6 through macOS 10.13, the default is i386 x86_64.

In macOS 10.14 Apple removed the ability to build i386 software so it is not 
possible to build universal in a default MacPorts install. (There are some 
complicated steps that a couple MacPorts users have identified that may allow 
building universal on 10.14.)

On macOS 10.15 Apple removed the ability to run i386 software so it is not 
possible to build universal.

On macOS 11 and later, the default set of universal architectures is x86_64 
arm64.

In MacPorts 2.7.0, significant changes were made to the universal variant 
feature so that MacPorts would not display the universal variant if it were not 
possible to use it on the current system. The default universal_archs on 10.14 
or 10.15 are set to the single value x86_64, and MacPorts base was enhanced so 
that if the universal_archs contain only a single value, then you will not see 
univers

Re: Conflicty between MacPorts and Anaconda

[Ryan Schmidt]

On Aug 30, 2021, at 09:32, Gerben Wierda wrote:
> 
> I had to install Anaconda (Python environment) to collaborate with someone. I 
> installed, but it adapted my shell environment in such a way that I’ve lost 
> MacPorts (and LMTX ConTeXt). Does anybody have experience with the 
> combination of Anaconda and MacPorts and what the correct way is to use them 
> side by side?

I don't know anything about Anaconda...

When you say you've "lost MacPorts" does that mean that when you type "port" 
something it says the command is not found? If so, that means that your PATH 
environment variable is not set up correctly. When you installed MacPorts, it 
edited your shell startup script (which varies depending on which SHELL you are 
using) to add the MacPorts paths /opt/local/bin and /opt/local/sbin to PATH, 
while preserving any other additions you made. Maybe the Anaconda installer 
also modified the PATH in that same shell startup file but did not preserve 
your other PATH modifications. Or if you are using the Bash shell, which 
supports I think three possible startup files, maybe Anaconda edited a 
different one, one which takes precedence and causes Bash to ignore the other 
startup file that contained your MacPorts PATH settings.

Re: Big Sur on M1 - bind9 named daemon don't run

[Ryan Schmidt]

On Aug 25, 2021, at 02:00, FritzS GMX wrote:

> after migration from my profile & apps from ElCapitan to Big Sur I 
> reinstalled all the MacPorts programs,
> bind9 are new compiled on my MacMini M1 too.
> 
> But the named daemon don't run. 
> 
> All this commands don’t work:
> 
> sudo launchctl load -wF /Library/LaunchDaemons/org.macports.bind9.plist
> 
> sudo /opt/local/bin/port load bind9
> 
> sudo /opt/local/sbin/rndc reload
> 
> What must I do that the named daemon runs?

Why don't the above commands work? What happens?

If you were expecting a process to be running after running those commands, and 
that process is not running, is it crashing? Is the OS creating crash logs in 
the usual directory? If so, show us one. Or, if no crash logs, does the Console 
indicate that the process is being restarted every 10 seconds and immediately 
quitting itself? Does the process write its own log file, and if so, does it 
contain anything explaining why it isn't staying running?


> Ist that a way for BigSur 11.5.2 on a Mac mini (M1, 2020)?
> https://trac.macports.org/wiki/howto/ShareArchives2

I'm not sure what the documentation about how to share archives between 
machines has to do with your present problem.

Re: Specify port for file dependency

[g5pw]

That would be `port install --unrequested pango-devel`

> On 31 Aug 2021, at 02:33, Ruben Di Battista  wrote:
> 
> Yeah, no thanks for your help. I appreciate! 
> 
> What I meant is at runtime, on the command line. 
> 
> How do I tell "I want to install gdl3, but using `pango-devel` to provide 
> libpango instead of `pango`?
> 
> I might install pango-devel manually, but that would make pango-devel a 
> requested port.