From ryandesign at macports.org Wed Dec 1 06:00:40 2021 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed, 1 Dec 2021 00:00:40 -0600 Subject: is macports getting rusty? In-Reply-To: <72A87175-BD58-4DB8-AB4A-3DF8A168078D@rochester.rr.com> References: <72A87175-BD58-4DB8-AB4A-3DF8A168078D@rochester.rr.com> Message-ID: <718A4DB2-62D8-4F9A-973A-A2B4E081B2B9@macports.org> On Nov 30, 2021, at 14:47, Christopher Nielsen wrote: > Back in May, @ryandesign mentioned that we have the option of upgrading our buildbot farm with more powerful CPUs. Said farm is currently hosted on Xserves, and since the CPUs are socketed, it?s reasonably straightforward. The new CPU generation is available in hex-core versions which would be a 50% improvement over the quad-core CPUs we have now. And the new CPU generation is made using a newer process with smaller traces, which will result in faster performance at the same speed rating. It's not entirely as straightforward as just replacing the CPUs though, because the newer CPU generation is not compatible with Xserve firmware. It would require replacing the Xserve firmware with Mac Pro firmware, which is possible at the expense of some Xserve functionality, which is an acceptable tradeoff. There's also the matter that the Xserve requires lidless CPUs which reduces the number of places from which one can purchase a CPU since not everybody sells lidless versions, or requires one to purchase a standard CPU and delid the CPU oneself or send it to someone else to have them do it for a fee. I also still haven't made a decision with regard to which CPU speed to seek out. The Xserve shipped in three CPU speed variants but Intel offers something like a dozen different CPU speeds. The choice is constrained by the power consumption of each different speed CPU and the thermal limits of the Xserve. Some of our builds spend more time on disk tasks than CPU tasks. We could increase the speed with which we can produce builds by optimizing mpbb to avoid unnecessary disk work, including unnecessary activations and deactivations of dependencies. See https://trac.macports.org/ticket/62621 for some thoughts on that. From ryandesign at macports.org Wed Dec 1 06:09:18 2021 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed, 1 Dec 2021 00:09:18 -0600 Subject: What is up with perl5.26 on Snow Leo? In-Reply-To: <6e56b23f-b65d-ecee-651d-a7645ed27b79@gmail.com> References: <022eacc2-8019-7d6f-f565-1b32fd344e09@gmail.com> <612FD7FD-F9BB-40F2-BD46-5E530C765571@macports.org> <51a7b1c4-69f3-28f0-f836-5e5292880801@mathiesen.info> <6e56b23f-b65d-ecee-651d-a7645ed27b79@gmail.com> Message-ID: <643EE790-3B31-419D-BBAA-86E326286072@macports.org> On Nov 29, 2021, at 20:21, Uli Wienands wrote: > Well, I wonder whether someone did something within the last day or two. I just tried it again, and lo-and-behold, perl5.26 installed just fine & now MacPorts is getting to work on the backlog of things that I could not update because of this problem. > > This after I just found out (in debug mode) that the perl5.26 port actually was not able to get its files; the fetch errored out with a 404 error for all attempts. What is odd is that it proceeded to do a bunch of things after that & even went to the destroot phase. I would love to send the log, but the renewed attempt was to generate the log so I could pack it up & send it, only for now the install succeeded making this moot. > > So, my thanks go out to whomever fixed this. Yes thanks very much to Josh who fixed it here: https://github.com/macports/macports-ports/commit/26dcf67f5b33a443b278a9e5382f1a18dea32d32 There had also been a ticket about it: https://trac.macports.org/ticket/63248 No need for a log since the problem is solved. What you presumably mean is that MacPorts encountered a 404 error trying to download a precompiled archive, and therefore it fetched the source (or MacPorts had already fetched the source for you before) and built it from source on your system. This isn't odd; it's how MacPorts is designed to work. A precompiled archive may simply not have been produced yet at the time you tried to install it. The archive has been produced now (you can see at http://packages.macports.org/perl5.26/ that they were built for darwin 10 on 11/28 at 10 am (x86_64) and 7 pm (i386) UTC), so if you were to try to install it now, you should receive that archive instead of needing to build from source. From wienands at gmail.com Wed Dec 1 14:19:19 2021 From: wienands at gmail.com (Uli Wienands) Date: Wed, 1 Dec 2021 08:19:19 -0600 Subject: What is up with perl5.26 on Snow Leo? In-Reply-To: <643EE790-3B31-419D-BBAA-86E326286072@macports.org> References: <022eacc2-8019-7d6f-f565-1b32fd344e09@gmail.com> <612FD7FD-F9BB-40F2-BD46-5E530C765571@macports.org> <51a7b1c4-69f3-28f0-f836-5e5292880801@mathiesen.info> <6e56b23f-b65d-ecee-651d-a7645ed27b79@gmail.com> <643EE790-3B31-419D-BBAA-86E326286072@macports.org> Message-ID: <16089584-10f0-0b65-c3ad-2748ca11ee8a@gmail.com> Well, I am familiar with the fall-back of fetching the distfiles. In my case, it did NOT fetch the distfiles. Went straight to "staging... to destroot". Anyway, this problem seems fixed, Thanks? much, Josh and all. Uli On 12/1/21 12:09 AM, Ryan Schmidt wrote: > > On Nov 29, 2021, at 20:21, Uli Wienands wrote: > >> Well, I wonder whether someone did something within the last day or two. I just tried it again, and lo-and-behold, perl5.26 installed just fine & now MacPorts is getting to work on the backlog of things that I could not update because of this problem. >> >> This after I just found out (in debug mode) that the perl5.26 port actually was not able to get its files; the fetch errored out with a 404 error for all attempts. What is odd is that it proceeded to do a bunch of things after that & even went to the destroot phase. I would love to send the log, but the renewed attempt was to generate the log so I could pack it up & send it, only for now the install succeeded making this moot. >> >> So, my thanks go out to whomever fixed this. > Yes thanks very much to Josh who fixed it here: > > https://github.com/macports/macports-ports/commit/26dcf67f5b33a443b278a9e5382f1a18dea32d32 > > There had also been a ticket about it: > > https://trac.macports.org/ticket/63248 > > No need for a log since the problem is solved. > > > What you presumably mean is that MacPorts encountered a 404 error trying to download a precompiled archive, and therefore it fetched the source (or MacPorts had already fetched the source for you before) and built it from source on your system. This isn't odd; it's how MacPorts is designed to work. A precompiled archive may simply not have been produced yet at the time you tried to install it. The archive has been produced now (you can see at http://packages.macports.org/perl5.26/ that they were built for darwin 10 on 11/28 at 10 am (x86_64) and 7 pm (i386) UTC), so if you were to try to install it now, you should receive that archive instead of needing to build from source. > > From dave at horsfall.org Wed Dec 8 22:42:22 2021 From: dave at horsfall.org (Dave Horsfall) Date: Thu, 9 Dec 2021 09:42:22 +1100 (EST) Subject: Cannot build libb2 Message-ID: MacBook Pro (13-inch, Mid 2010), macOS High Sierra 10.13.6. I finally got around to installing Xcode 10.1 and matching CLT, then started to rebuild MacPorts, dutifully following the instructions in the Migration Guide. It karked it when building "libb2" (config.log attached); here's the interesting bit: configure:4721: checking whether byte ordering is bigendian configure:4737: /usr/bin/clang -c -pipe -O3 -arch x86_64 -arch i386 -I/opt/local /include conftest.c >&5 configure:4737: $? = 0 configure:4936: result: universal configure:4947: error: universal endianness not supported I don't where it got "+universal" from; *I* certainly didn't ask for it... I couldn't find any references when poking around; anyone else seen this before I report it as a bug? Thanks. -- Dave -------------- next part -------------- This file contains any messages produced by compilers while running configure, to aid debugging if configure makes a mistake. It was created by libb2 configure 0.98.1, which was generated by GNU Autoconf 2.71. Invocation command line was $ ./configure --prefix=/opt/local --disable-dependency-tracking --enable-native=no --disable-openmp ## --------- ## ## Platform. ## ## --------- ## hostname = mackie.kfu uname -m = x86_64 uname -r = 17.7.0 uname -s = Darwin uname -v = Darwin Kernel Version 17.7.0: Fri Oct 30 13:34:27 PDT 2020; root:xnu-4570.71.82.8~1/RELEASE_X86_64 /usr/bin/uname -p = i386 /bin/uname -X = unknown /bin/arch = unknown /usr/bin/arch -k = unknown /usr/convex/getsysinfo = unknown /usr/bin/hostinfo = Mach kernel version: Darwin Kernel Version 17.7.0: Fri Oct 30 13:34:27 PDT 2020; root:xnu-4570.71.82.8~1/RELEASE_X86_64 Kernel configured for up to 2 processors. 2 processors are physically available. 2 processors are logically available. Processor type: i486 (Intel 80486) Processors active: 0 1 Primary memory available: 8.00 gigabytes Default processor set: 414 tasks, 1868 threads, 2 processors Load average: 4.07, Mach factor: 0.44 /bin/machine = unknown /usr/bin/oslevel = unknown /bin/universe = unknown PATH: /opt/local/bin/ PATH: /opt/local/sbin/ PATH: /bin/ PATH: /sbin/ PATH: /usr/bin/ PATH: /usr/sbin/ ## ----------- ## ## Core tests. ## ## ----------- ## configure:2532: looking for aux files: config.guess config.sub ltmain.sh compile missing install-sh configure:2545: trying ./ configure:2574: ./config.guess found configure:2574: ./config.sub found configure:2574: ./ltmain.sh found configure:2574: ./compile found configure:2574: ./missing found configure:2556: ./install-sh found configure:2706: checking for a BSD-compatible install configure:2779: result: /usr/bin/install -c configure:2790: checking whether build environment is sane configure:2845: result: yes configure:3004: checking for a race-free mkdir -p configure:3048: result: ./install-sh -c -d configure:3055: checking for gawk configure:3090: result: no configure:3055: checking for mawk configure:3090: result: no configure:3055: checking for nawk configure:3090: result: no configure:3055: checking for awk configure:3076: found /usr/bin/awk configure:3087: result: awk configure:3098: checking whether make sets $(MAKE) configure:3121: result: yes configure:3151: checking whether make supports nested variables configure:3169: result: yes configure:3378: checking for gcc configure:3410: result: /usr/bin/clang configure:3763: checking for C compiler version configure:3772: /usr/bin/clang --version >&5 Apple LLVM version 10.0.0 (clang-1000.10.44.4) Target: x86_64-apple-darwin17.7.0 Thread model: posix InstalledDir: /Library/Developer/CommandLineTools/usr/bin configure:3783: $? = 0 configure:3772: /usr/bin/clang -v >&5 Apple LLVM version 10.0.0 (clang-1000.10.44.4) Target: x86_64-apple-darwin17.7.0 Thread model: posix InstalledDir: /Library/Developer/CommandLineTools/usr/bin configure:3783: $? = 0 configure:3772: /usr/bin/clang -V >&5 clang: error: argument to '-V' is missing (expected 1 value) clang: error: no input files configure:3783: $? = 1 configure:3772: /usr/bin/clang -qversion >&5 clang: error: unknown argument: '-qversion' clang: error: no input files configure:3783: $? = 1 configure:3772: /usr/bin/clang -version >&5 clang: error: unknown argument: '-version' clang: error: no input files configure:3783: $? = 1 configure:3803: checking whether the C compiler works configure:3825: /usr/bin/clang -pipe -O3 -arch x86_64 -arch i386 -I/opt/local/include -L/opt/local/lib -Wl,-headerpad_max_install_names -arch x86_64 -arch i386 conftest.c >&5 ld: warning: The i386 architecture is deprecated for macOS (remove from the Xcode build setting: ARCHS) configure:3829: $? = 0 configure:3879: result: yes configure:3882: checking for C compiler default output file name configure:3884: result: a.out configure:3890: checking for suffix of executables configure:3897: /usr/bin/clang -o conftest -pipe -O3 -arch x86_64 -arch i386 -I/opt/local/include -L/opt/local/lib -Wl,-headerpad_max_install_names -arch x86_64 -arch i386 conftest.c >&5 ld: warning: The i386 architecture is deprecated for macOS (remove from the Xcode build setting: ARCHS) configure:3901: $? = 0 configure:3924: result: configure:3946: checking whether we are cross compiling configure:3954: /usr/bin/clang -o conftest -pipe -O3 -arch x86_64 -arch i386 -I/opt/local/include -L/opt/local/lib -Wl,-headerpad_max_install_names -arch x86_64 -arch i386 conftest.c >&5 ld: warning: The i386 architecture is deprecated for macOS (remove from the Xcode build setting: ARCHS) configure:3958: $? = 0 configure:3965: ./conftest configure:3969: $? = 0 configure:3984: result: no configure:3989: checking for suffix of object files configure:4012: /usr/bin/clang -c -pipe -O3 -arch x86_64 -arch i386 -I/opt/local/include conftest.c >&5 configure:4016: $? = 0 configure:4038: result: o configure:4042: checking whether the compiler supports GNU C configure:4062: /usr/bin/clang -c -pipe -O3 -arch x86_64 -arch i386 -I/opt/local/include conftest.c >&5 configure:4062: $? = 0 configure:4072: result: yes configure:4083: checking whether /usr/bin/clang accepts -g configure:4104: /usr/bin/clang -c -g -I/opt/local/include conftest.c >&5 configure:4104: $? = 0 configure:4148: result: yes configure:4168: checking for /usr/bin/clang option to enable C11 features configure:4183: /usr/bin/clang -c -pipe -O3 -arch x86_64 -arch i386 -I/opt/local/include conftest.c >&5 configure:4183: $? = 0 configure:4201: result: none needed configure:4317: checking whether /usr/bin/clang understands -c and -o together configure:4340: /usr/bin/clang -c conftest.c -o conftest2.o configure:4343: $? = 0 configure:4340: /usr/bin/clang -c conftest.c -o conftest2.o configure:4343: $? = 0 configure:4355: result: yes configure:4375: checking whether make supports the include directive configure:4390: make -f confmf.GNU && cat confinc.out this is the am__doit target configure:4393: $? = 0 configure:4412: result: yes (GNU style) configure:4438: checking dependency style of /usr/bin/clang configure:4550: result: none configure:4568: checking for explicit_bzero configure:4568: /usr/bin/clang -o conftest -pipe -O3 -arch x86_64 -arch i386 -I/opt/local/include -L/opt/local/lib -Wl,-headerpad_max_install_names -arch x86_64 -arch i386 conftest.c >&5 Undefined symbols for architecture x86_64: "_explicit_bzero", referenced from: _main in conftest-ec5ab5.o ld: symbol(s) not found for architecture x86_64 clang: error: linker command failed with exit code 1 (use -v to see invocation) configure:4568: $? = 1 configure: failed program was: | /* confdefs.h */ | #define PACKAGE_NAME "libb2" | #define PACKAGE_TARNAME "libb2" | #define PACKAGE_VERSION "0.98.1" | #define PACKAGE_STRING "libb2 0.98.1" | #define PACKAGE_BUGREPORT "contact at blake2.net" | #define PACKAGE_URL "https://blake2.net" | #define PACKAGE "libb2" | #define VERSION "0.98.1" | /* end confdefs.h. */ | /* Define explicit_bzero to an innocuous variant, in case declares explicit_bzero. | For example, HP-UX 11i declares gettimeofday. */ | #define explicit_bzero innocuous_explicit_bzero | | /* System header to define __stub macros and hopefully few prototypes, | which can conflict with char explicit_bzero (); below. */ | | #include | #undef explicit_bzero | | /* Override any GCC internal prototype to avoid an error. | Use char because int might match the return type of a GCC | builtin and then its argument prototype would still apply. */ | #ifdef __cplusplus | extern "C" | #endif | char explicit_bzero (); | /* The GNU C library defines this for functions which it implements | to always fail with ENOSYS. Some functions are actually named | something starting with __ and the normal name is an alias. */ | #if defined __stub_explicit_bzero || defined __stub___explicit_bzero | choke me | #endif | | int | main (void) | { | return explicit_bzero (); | ; | return 0; | } configure:4568: result: no configure:4575: checking for explicit_memset configure:4575: /usr/bin/clang -o conftest -pipe -O3 -arch x86_64 -arch i386 -I/opt/local/include -L/opt/local/lib -Wl,-headerpad_max_install_names -arch x86_64 -arch i386 conftest.c >&5 Undefined symbols for architecture x86_64: "_explicit_memset", referenced from: _main in conftest-1c8a64.o ld: symbol(s) not found for architecture x86_64 clang: error: linker command failed with exit code 1 (use -v to see invocation) configure:4575: $? = 1 configure: failed program was: | /* confdefs.h */ | #define PACKAGE_NAME "libb2" | #define PACKAGE_TARNAME "libb2" | #define PACKAGE_VERSION "0.98.1" | #define PACKAGE_STRING "libb2 0.98.1" | #define PACKAGE_BUGREPORT "contact at blake2.net" | #define PACKAGE_URL "https://blake2.net" | #define PACKAGE "libb2" | #define VERSION "0.98.1" | /* end confdefs.h. */ | /* Define explicit_memset to an innocuous variant, in case declares explicit_memset. | For example, HP-UX 11i declares gettimeofday. */ | #define explicit_memset innocuous_explicit_memset | | /* System header to define __stub macros and hopefully few prototypes, | which can conflict with char explicit_memset (); below. */ | | #include | #undef explicit_memset | | /* Override any GCC internal prototype to avoid an error. | Use char because int might match the return type of a GCC | builtin and then its argument prototype would still apply. */ | #ifdef __cplusplus | extern "C" | #endif | char explicit_memset (); | /* The GNU C library defines this for functions which it implements | to always fail with ENOSYS. Some functions are actually named | something starting with __ and the normal name is an alias. */ | #if defined __stub_explicit_memset || defined __stub___explicit_memset | choke me | #endif | | int | main (void) | { | return explicit_memset (); | ; | return 0; | } configure:4575: result: no configure:4582: checking for memset_s configure:4582: /usr/bin/clang -o conftest -pipe -O3 -arch x86_64 -arch i386 -I/opt/local/include -L/opt/local/lib -Wl,-headerpad_max_install_names -arch x86_64 -arch i386 conftest.c >&5 ld: warning: The i386 architecture is deprecated for macOS (remove from the Xcode build setting: ARCHS) configure:4582: $? = 0 configure:4582: result: yes configure:4593: checking for stdio.h configure:4593: /usr/bin/clang -c -pipe -O3 -arch x86_64 -arch i386 -I/opt/local/include conftest.c >&5 configure:4593: $? = 0 configure:4593: result: yes configure:4593: checking for stdlib.h configure:4593: /usr/bin/clang -c -pipe -O3 -arch x86_64 -arch i386 -I/opt/local/include conftest.c >&5 configure:4593: $? = 0 configure:4593: result: yes configure:4593: checking for string.h configure:4593: /usr/bin/clang -c -pipe -O3 -arch x86_64 -arch i386 -I/opt/local/include conftest.c >&5 configure:4593: $? = 0 configure:4593: result: yes configure:4593: checking for inttypes.h configure:4593: /usr/bin/clang -c -pipe -O3 -arch x86_64 -arch i386 -I/opt/local/include conftest.c >&5 configure:4593: $? = 0 configure:4593: result: yes configure:4593: checking for stdint.h configure:4593: /usr/bin/clang -c -pipe -O3 -arch x86_64 -arch i386 -I/opt/local/include conftest.c >&5 configure:4593: $? = 0 configure:4593: result: yes configure:4593: checking for strings.h configure:4593: /usr/bin/clang -c -pipe -O3 -arch x86_64 -arch i386 -I/opt/local/include conftest.c >&5 configure:4593: $? = 0 configure:4593: result: yes configure:4593: checking for sys/stat.h configure:4593: /usr/bin/clang -c -pipe -O3 -arch x86_64 -arch i386 -I/opt/local/include conftest.c >&5 configure:4593: $? = 0 configure:4593: result: yes configure:4593: checking for sys/types.h configure:4593: /usr/bin/clang -c -pipe -O3 -arch x86_64 -arch i386 -I/opt/local/include conftest.c >&5 configure:4593: $? = 0 configure:4593: result: yes configure:4593: checking for unistd.h configure:4593: /usr/bin/clang -c -pipe -O3 -arch x86_64 -arch i386 -I/opt/local/include conftest.c >&5 configure:4593: $? = 0 configure:4593: result: yes configure:4618: checking for stddef.h configure:4618: /usr/bin/clang -c -pipe -O3 -arch x86_64 -arch i386 -I/opt/local/include conftest.c >&5 configure:4618: $? = 0 configure:4618: result: yes configure:4624: checking for stdint.h configure:4624: result: yes configure:4630: checking for stdlib.h configure:4630: result: yes configure:4636: checking for string.h configure:4636: result: yes configure:4721: checking whether byte ordering is bigendian configure:4737: /usr/bin/clang -c -pipe -O3 -arch x86_64 -arch i386 -I/opt/local/include conftest.c >&5 configure:4737: $? = 0 configure:4936: result: universal configure:4947: error: universal endianness not supported ## ---------------- ## ## Cache variables. ## ## ---------------- ## ac_cv_c_bigendian=universal ac_cv_c_compiler_gnu=yes ac_cv_env_CC_set=set ac_cv_env_CC_value=/usr/bin/clang ac_cv_env_CFLAGS_set=set ac_cv_env_CFLAGS_value='-pipe -O3 -arch x86_64 -arch i386' ac_cv_env_CPPFLAGS_set=set ac_cv_env_CPPFLAGS_value=-I/opt/local/include ac_cv_env_LDFLAGS_set=set ac_cv_env_LDFLAGS_value='-L/opt/local/lib -Wl,-headerpad_max_install_names -arch x86_64 -arch i386' ac_cv_env_LIBS_set= ac_cv_env_LIBS_value= ac_cv_env_LT_SYS_LIBRARY_PATH_set= ac_cv_env_LT_SYS_LIBRARY_PATH_value= ac_cv_env_build_alias_set= ac_cv_env_build_alias_value= ac_cv_env_host_alias_set= ac_cv_env_host_alias_value= ac_cv_env_target_alias_set= ac_cv_env_target_alias_value= ac_cv_func_explicit_bzero=no ac_cv_func_explicit_memset=no ac_cv_func_memset_s=yes ac_cv_header_inttypes_h=yes ac_cv_header_stddef_h=yes ac_cv_header_stdint_h=yes ac_cv_header_stdio_h=yes ac_cv_header_stdlib_h=yes ac_cv_header_string_h=yes ac_cv_header_strings_h=yes ac_cv_header_sys_stat_h=yes ac_cv_header_sys_types_h=yes ac_cv_header_unistd_h=yes ac_cv_objext=o ac_cv_prog_AWK=awk ac_cv_prog_ac_ct_CC=/usr/bin/clang ac_cv_prog_cc_c11= ac_cv_prog_cc_g=yes ac_cv_prog_cc_stdc= ac_cv_prog_make_make_set=yes am_cv_CC_dependencies_compiler_type=none am_cv_make_support_nested_variables=yes am_cv_prog_cc_c_o=yes ## ----------------- ## ## Output variables. ## ## ----------------- ## ACLOCAL='${SHELL} '\''/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_libb2/libb2/work/libb2-0.98.1/missing'\'' aclocal-1.16' AMDEPBACKSLASH='' AMDEP_FALSE='' AMDEP_TRUE='#' AMTAR='$${TAR-tar}' AM_BACKSLASH='\' AM_DEFAULT_V='$(AM_DEFAULT_VERBOSITY)' AM_DEFAULT_VERBOSITY='1' AM_V='$(V)' AR='' AUTOCONF='${SHELL} '\''/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_libb2/libb2/work/libb2-0.98.1/missing'\'' autoconf' AUTOHEADER='${SHELL} '\''/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_libb2/libb2/work/libb2-0.98.1/missing'\'' autoheader' AUTOMAKE='${SHELL} '\''/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_libb2/libb2/work/libb2-0.98.1/missing'\'' automake-1.16' AWK='awk' B2_LIBRARY_VERSION='1:4:0' CC='/usr/bin/clang' CCDEPMODE='depmode=none' CFLAGS='-pipe -O3 -arch x86_64 -arch i386' CPPFLAGS='-I/opt/local/include' CSCOPE='cscope' CTAGS='ctags' CYGPATH_W='echo' DEFS='' DEPDIR='.deps' DLLTOOL='' DSYMUTIL='' DUMPBIN='' ECHO_C='\c' ECHO_N='' ECHO_T='' EGREP='' ETAGS='etags' EXEEXT='' FGREP='' GREP='' INSTALL_DATA='${INSTALL} -m 644' INSTALL_PROGRAM='${INSTALL}' INSTALL_SCRIPT='${INSTALL}' INSTALL_STRIP_PROGRAM='$(install_sh) -c -s' LD='' LDFLAGS='-L/opt/local/lib -Wl,-headerpad_max_install_names -arch x86_64 -arch i386' LIBOBJS='' LIBS='' LIBTOOL='' LIPO='' LN_S='' LTLIBOBJS='' LT_SYS_LIBRARY_PATH='' MAKEINFO='${SHELL} '\''/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_libb2/libb2/work/libb2-0.98.1/missing'\'' makeinfo' MANIFEST_TOOL='' MKDIR_P='./install-sh -c -d' NM='' NMEDIT='' OBJDUMP='' OBJEXT='o' OPENMP_CFLAGS='' OTOOL64='' OTOOL='' PACKAGE='libb2' PACKAGE_BUGREPORT='contact at blake2.net' PACKAGE_NAME='libb2' PACKAGE_STRING='libb2 0.98.1' PACKAGE_TARNAME='libb2' PACKAGE_URL='https://blake2.net' PACKAGE_VERSION='0.98.1' PATH_SEPARATOR=':' RANLIB='' SED='' SET_MAKE='' SHELL='/bin/sh' SIMD_FLAGS='' STRIP='' USE_FAT_FALSE='' USE_FAT_TRUE='' USE_SSE_FALSE='' USE_SSE_TRUE='' VERSION='0.98.1' ac_ct_AR='' ac_ct_CC='/usr/bin/clang' ac_ct_DUMPBIN='' am__EXEEXT_FALSE='' am__EXEEXT_TRUE='' am__fastdepCC_FALSE='' am__fastdepCC_TRUE='#' am__include='include' am__isrc='' am__leading_dot='.' am__nodep='' am__quote='' am__tar='$${TAR-tar} chof - "$$tardir"' am__untar='$${TAR-tar} xf -' bindir='${exec_prefix}/bin' build='' build_alias='' build_cpu='' build_os='' build_vendor='' datadir='${datarootdir}' datarootdir='${prefix}/share' docdir='${datarootdir}/doc/${PACKAGE_TARNAME}' dvidir='${docdir}' exec_prefix='NONE' host='' host_alias='' host_cpu='' host_os='' host_vendor='' htmldir='${docdir}' includedir='${prefix}/include' infodir='${datarootdir}/info' install_sh='${SHELL} /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_libb2/libb2/work/libb2-0.98.1/install-sh' libdir='${exec_prefix}/lib' libexecdir='${exec_prefix}/libexec' localedir='${datarootdir}/locale' localstatedir='${prefix}/var' mandir='${datarootdir}/man' mkdir_p='$(MKDIR_P)' oldincludedir='/usr/include' pdfdir='${docdir}' pkgconfigdir='' prefix='/opt/local' program_transform_name='s,x,x,' psdir='${docdir}' runstatedir='${localstatedir}/run' sbindir='${exec_prefix}/sbin' sharedstatedir='${prefix}/com' sysconfdir='${prefix}/etc' target_alias='' ## ----------- ## ## confdefs.h. ## ## ----------- ## /* confdefs.h */ #define PACKAGE_NAME "libb2" #define PACKAGE_TARNAME "libb2" #define PACKAGE_VERSION "0.98.1" #define PACKAGE_STRING "libb2 0.98.1" #define PACKAGE_BUGREPORT "contact at blake2.net" #define PACKAGE_URL "https://blake2.net" #define PACKAGE "libb2" #define VERSION "0.98.1" #define HAVE_MEMSET_S 1 #define HAVE_STDIO_H 1 #define HAVE_STDLIB_H 1 #define HAVE_STRING_H 1 #define HAVE_INTTYPES_H 1 #define HAVE_STDINT_H 1 #define HAVE_STRINGS_H 1 #define HAVE_SYS_STAT_H 1 #define HAVE_SYS_TYPES_H 1 #define HAVE_UNISTD_H 1 #define STDC_HEADERS 1 #define HAVE_STDDEF_H 1 #define HAVE_STDINT_H 1 #define HAVE_STDLIB_H 1 #define HAVE_STRING_H 1 configure: exit 1 From stevan.tiefert at icloud.com Thu Dec 9 14:59:40 2021 From: stevan.tiefert at icloud.com (Stevan Tiefert) Date: Thu, 9 Dec 2021 15:59:40 +0100 Subject: mozjs60 doesn't want to install Message-ID: Hello, if I execute following: sudo port install mozjs60 I got this error: user at computer ~ % sudo port install mozjs60 Password: ---> Computing dependencies for mozjs60 ---> Fetching archive for mozjs60 ---> Attempting to fetch mozjs60-60.8.0_0.darwin_21.x86_64.tbz2 from https://packages.macports.org/mozjs60 ---> Attempting to fetch mozjs60-60.8.0_0.darwin_21.x86_64.tbz2 from https://nue.de.packages.macports.org/mozjs60 ---> Attempting to fetch mozjs60-60.8.0_0.darwin_21.x86_64.tbz2 from https://fra.de.packages.macports.org/mozjs60 ---> Configuring mozjs60 Error: Failed to configure mozjs60: consult /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_mozjs60/mozjs60/work/mozjs-60.8.0/js/src/obj/config.log Error: Failed to configure mozjs60: configure failure: command execution failed Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_mozjs60/mozjs60/main.log for details. Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug. Error: Processing of port mozjs60 failed user at computer ~ % What should I do to install it? With regards Stevan Tiefert -------------- next part -------------- An HTML attachment was scrubbed... URL: From jonesc at hep.phy.cam.ac.uk Thu Dec 9 15:10:53 2021 From: jonesc at hep.phy.cam.ac.uk (Christopher Jones) Date: Thu, 9 Dec 2021 15:10:53 +0000 Subject: mozjs60 doesn't want to install In-Reply-To: References: Message-ID: Follow the instructions given to you below. i,e, https://guide.macports.org/#project.tickets > On 9 Dec 2021, at 2:59 pm, Stevan Tiefert via macports-users wrote: > > Hello, > > if I execute following: > > sudo port install mozjs60 > > I got this error: > > user at computer ~ % sudo port install mozjs60 > Password: > ---> Computing dependencies for mozjs60 > ---> Fetching archive for mozjs60 > ---> Attempting to fetch mozjs60-60.8.0_0.darwin_21.x86_64.tbz2 from https://packages.macports.org/mozjs60 > ---> Attempting to fetch mozjs60-60.8.0_0.darwin_21.x86_64.tbz2 from https://nue.de.packages.macports.org/mozjs60 > ---> Attempting to fetch mozjs60-60.8.0_0.darwin_21.x86_64.tbz2 from https://fra.de.packages.macports.org/mozjs60 > ---> Configuring mozjs60 > Error: Failed to configure mozjs60: consult /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_mozjs60/mozjs60/work/mozjs-60.8.0/js/src/obj/config.log > Error: Failed to configure mozjs60: configure failure: command execution failed > Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_mozjs60/mozjs60/main.log for details. > Error: Follow https://guide.macports.org/#project.tickets if you believe there > is a bug. > Error: Processing of port mozjs60 failed > user at computer ~ % > > What should I do to install it? > > With regards > Stevan Tiefert -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 1930 bytes Desc: not available URL: From stevan.tiefert at icloud.com Thu Dec 9 15:33:45 2021 From: stevan.tiefert at icloud.com (Stevan Tiefert) Date: Thu, 9 Dec 2021 16:33:45 +0100 Subject: mozjs60 doesn't want to install [SOLVED] In-Reply-To: References: Message-ID: <238CCDDC-1E90-401C-A9FA-10BE3453657A@icloud.com> I?ve seen this issue on https://trac.macports.org/ticket/61606 . This problem is about 10 months old and not repaired yet. Thanks Christoper Jones! > Am 09.12.2021 um 16:10 schrieb Christopher Jones : > > > Follow the instructions given to you below. i,e, > > https://guide.macports.org/#project.tickets > > >> On 9 Dec 2021, at 2:59 pm, Stevan Tiefert via macports-users > wrote: >> >> Hello, >> >> if I execute following: >> >> sudo port install mozjs60 >> >> I got this error: >> >> user at computer ~ % sudo port install mozjs60 >> Password: >> ---> Computing dependencies for mozjs60 >> ---> Fetching archive for mozjs60 >> ---> Attempting to fetch mozjs60-60.8.0_0.darwin_21.x86_64.tbz2 from https://packages.macports.org/mozjs60 >> ---> Attempting to fetch mozjs60-60.8.0_0.darwin_21.x86_64.tbz2 from https://nue.de.packages.macports.org/mozjs60 >> ---> Attempting to fetch mozjs60-60.8.0_0.darwin_21.x86_64.tbz2 from https://fra.de.packages.macports.org/mozjs60 >> ---> Configuring mozjs60 >> Error: Failed to configure mozjs60: consult /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_mozjs60/mozjs60/work/mozjs-60.8.0/js/src/obj/config.log >> Error: Failed to configure mozjs60: configure failure: command execution failed >> Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_mozjs60/mozjs60/main.log for details. >> Error: Follow https://guide.macports.org/#project.tickets if you believe there >> is a bug. >> Error: Processing of port mozjs60 failed >> user at computer ~ % >> >> What should I do to install it? >> >> With regards >> Stevan Tiefert > -------------- next part -------------- An HTML attachment was scrubbed... URL: From seaquench at protonmail.com Thu Dec 9 18:53:20 2021 From: seaquench at protonmail.com (SeaQuench) Date: Thu, 09 Dec 2021 18:53:20 +0000 Subject: python ports depend on openssl not in index Message-ID: <2J_PhAvKOoU6z5ctyKPOiuGslZnviWp5R-pR7zuHHRuE4kLpqWxOmLBAMKJ4Kl60h21lD6RF0u4WX5CjvyP5FK_5Mqp4frmYrHId9-0tPgs=@protonmail.com> After applying an update to MacOS last August, the python ports are reporting a dependency on either openssl11 or openssl3, neither of which are to be found in the (local?) index for MacPorts, according to the error I have received, copied below. While I am prompted to report a bug, I presume I am not in a novel situation. Could someone advise me as to how to proceed? I am running MacPorts 2.6.2 on MacOS 10.15.7 with XCode 12.4 installed. $ sudo port install python39 > Warning: No port openssl3 found in the index. > ---> Computing dependencies for openssl > Error: Dependency 'openssl3' not found. > Error: Unable to execute port: upgrade openssl failed $ sudo port install openssl > ---> Computing dependencies for openssl > Error: Dependency 'openssl3' not found. > Error: Follow https://guide.macports.org/#project.tickets to report a bug. > Error: Processing of port openssl failed $ sudo port -n upgrade --force python38 > --->Computing dependencies for python38 > --->Fetching archive for python38 > --->Attempting to fetch python38-3.8.12_4+optimizations.darwin_19.x86_64.tbz2 from https://packages.macports.org/python38 > --->Attempting to fetch python38-3.8.12_4+optimizations.darwin_19.x86_64.tbz2.rmd160 from https://packages.macports.org/python38 > --->Installing python38 @3.8.12_4+optimizations > --->Cleaning python38 > --->Computing dependencies for python38 > --->Deactivating python38 @3.8.11_0 > --->Cleaning python38 > --->Activating python38 @3.8.12_4+optimizations > --->Cleaning python38 > --->Updating database of binaries > --->Scanning binaries for linking errors > --->Found 18 broken files, matching files to ports > --->Found 4 broken ports, determining rebuild order > You can always run 'port rev-upgrade' again to fix errors. > The following ports will be rebuilt: > python38 @3.8.12+optimizations > python39 @3.9.6 > glib2 @2.58.3+x11 > gobject-introspection @1.60.2 > Continue? [Y/n]: y > Warning: No port openssl3 found in the index. > --->Computing dependencies for openssl > Error: Dependency 'openssl3' not found. > Error: rev-upgrade failed: Error rebuilding python38 > Error: Follow https://guide.macports.org/#project.tickets to report a bug. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jonesc at hep.phy.cam.ac.uk Thu Dec 9 19:47:39 2021 From: jonesc at hep.phy.cam.ac.uk (Chris Jones) Date: Thu, 9 Dec 2021 19:47:39 +0000 Subject: python ports depend on openssl not in index In-Reply-To: <2J_PhAvKOoU6z5ctyKPOiuGslZnviWp5R-pR7zuHHRuE4kLpqWxOmLBAMKJ4Kl60h21lD6RF0u4WX5CjvyP5FK_5Mqp4frmYrHId9-0tPgs=@protonmail.com> References: <2J_PhAvKOoU6z5ctyKPOiuGslZnviWp5R-pR7zuHHRuE4kLpqWxOmLBAMKJ4Kl60h21lD6RF0u4WX5CjvyP5FK_5Mqp4frmYrHId9-0tPgs=@protonmail.com> Message-ID: Did you follow the migration guide when moving to a new major os version ? https://trac.macports.org/wiki/Migration If not, follow it now, to wipe out your ports and reinstall them correctly for the new os. If you did, your ports tree seems to be very out of date. Then try, > sudo port selfupdate > sudo port sync > sudo port upgrade outdated Chris > On 9 Dec 2021, at 6:53 pm, SeaQuench via macports-users wrote: > > ? > After applying an update to MacOS last August, the python ports are reporting a dependency on either openssl11 or openssl3, neither of which are to be found in the (local?) index for MacPorts, according to the error I have received, copied below. While I am prompted to report a bug, I presume I am not in a novel situation. Could someone advise me as to how to proceed? I am running MacPorts 2.6.2 on MacOS 10.15.7 with XCode 12.4 installed. > > $ sudo port install python39 > Warning: No port openssl3 found in the index. > ---> Computing dependencies for openssl > Error: Dependency 'openssl3' not found. > Error: Unable to execute port: upgrade openssl failed > $ sudo port install openssl > ---> Computing dependencies for openssl > Error: Dependency 'openssl3' not found. > Error: Follow https://guide.macports.org/#project.tickets to report a bug. > Error: Processing of port openssl failed > $ sudo port -n upgrade --force python38 > ---> Computing dependencies for python38 > ---> Fetching archive for python38 > ---> Attempting to fetch python38-3.8.12_4+optimizations.darwin_19.x86_64.tbz2 from https://packages.macports.org/python38 > ---> Attempting to fetch python38-3.8.12_4+optimizations.darwin_19.x86_64.tbz2.rmd160 from https://packages.macports.org/python38 > ---> Installing python38 @3.8.12_4+optimizations > ---> Cleaning python38 > ---> Computing dependencies for python38 > ---> Deactivating python38 @3.8.11_0 > ---> Cleaning python38 > ---> Activating python38 @3.8.12_4+optimizations > ---> Cleaning python38 > ---> Updating database of binaries > ---> Scanning binaries for linking errors > ---> Found 18 broken files, matching files to ports > ---> Found 4 broken ports, determining rebuild order > You can always run 'port rev-upgrade' again to fix errors. > The following ports will be rebuilt: > python38 @3.8.12+optimizations > python39 @3.9.6 > glib2 @2.58.3+x11 > gobject-introspection @1.60.2 > Continue? [Y/n]: y > Warning: No port openssl3 found in the index. > ---> Computing dependencies for openssl > Error: Dependency 'openssl3' not found. > Error: rev-upgrade failed: Error rebuilding python38 > Error: Follow https://guide.macports.org/#project.tickets to report a bug. > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jmr at macports.org Fri Dec 10 03:39:14 2021 From: jmr at macports.org (Joshua Root) Date: Fri, 10 Dec 2021 14:39:14 +1100 Subject: python ports depend on openssl not in index In-Reply-To: <2J_PhAvKOoU6z5ctyKPOiuGslZnviWp5R-pR7zuHHRuE4kLpqWxOmLBAMKJ4Kl60h21lD6RF0u4WX5CjvyP5FK_5Mqp4frmYrHId9-0tPgs=@protonmail.com> References: <2J_PhAvKOoU6z5ctyKPOiuGslZnviWp5R-pR7zuHHRuE4kLpqWxOmLBAMKJ4Kl60h21lD6RF0u4WX5CjvyP5FK_5Mqp4frmYrHId9-0tPgs=@protonmail.com> Message-ID: SeaQuench wrote: > After applying an update to MacOS last August, the python ports are reporting a dependency on either openssl11 or openssl3, neither of which are to be found in the (local?) index for MacPorts, according to the error I have received, copied below. While I am prompted to report a bug, I presume I am not in a novel situation. Could someone advise me as to how to proceed? I am running MacPorts 2.6.2 on MacOS 10.15.7 with XCode 12.4 installed. The primary problem here is that you are running MacPorts 2.6.2 (released in 2019). The current ports are not going to work with an old version of base. You need to update to 2.7.1, and the other problems will likely be resolved by that. - Josh From ryandesign at macports.org Fri Dec 10 08:28:24 2021 From: ryandesign at macports.org (Ryan Schmidt) Date: Fri, 10 Dec 2021 02:28:24 -0600 Subject: Cannot build libb2 In-Reply-To: References: Message-ID: <4C226EA1-952F-4E70-90D9-F8D2DC6989FB@macports.org> On Dec 8, 2021, at 16:42, Dave Horsfall wrote: > MacBook Pro (13-inch, Mid 2010), macOS High Sierra 10.13.6. > > I finally got around to installing Xcode 10.1 and matching CLT, then > started to rebuild MacPorts, dutifully following the instructions in the > Migration Guide. > > It karked it when building "libb2" (config.log attached); here's the > interesting bit: > > configure:4721: checking whether byte ordering is bigendian > configure:4737: /usr/bin/clang -c -pipe -O3 -arch x86_64 -arch i386 -I/opt/local > /include conftest.c >&5 > configure:4737: $? = 0 > configure:4936: result: universal > configure:4947: error: universal endianness not supported > > I don't where it got "+universal" from; *I* certainly didn't ask for it... > > I couldn't find any references when poking around; anyone else seen this > before I report it as a bug? The "-arch x86_64 -arch i386" in the log does seem to indicate MacPorts is doing a universal build. The ways that could happen: * You specified +universal on the command line * You specified +universal in variants.conf * You installed a port that, because it does not support your machine's native architecture, requires its dependencies to be installed universal. If libb2 does not build universal, then that is certainly something we should fix. A bug has already been filed about it: https://trac.macports.org/ticket/64148 If you want to explore why libb2 is building universal when you don't intend that, show us what command you ran and the output. Specifically, we'd want to know which port you are trying to install or upgrade when libb2 gets build universal. From jonesc at hep.phy.cam.ac.uk Fri Dec 10 08:29:55 2021 From: jonesc at hep.phy.cam.ac.uk (Chris Jones) Date: Fri, 10 Dec 2021 08:29:55 +0000 Subject: python ports depend on openssl not in index In-Reply-To: <6ka4vAHxC1FypGcxmcw1MBr1KyplHKA3_RgHPvz74ArBDv-0Q3emV5gs0hW1tnqVinpPZTjw-jjMuNtp9PYxBSC4VM4KuOCTDuETULIaae0=@protonmail.com> References: <6ka4vAHxC1FypGcxmcw1MBr1KyplHKA3_RgHPvz74ArBDv-0Q3emV5gs0hW1tnqVinpPZTjw-jjMuNtp9PYxBSC4VM4KuOCTDuETULIaae0=@protonmail.com> Message-ID: <4ACEB13C-941D-46CB-A072-88CD6FC3F4BF@hep.phy.cam.ac.uk> Hi, Please always remember to reply to the list. We need to see why you are not finding the openssl3 port, as that has been available for some time. Please run sudo port -d sync And post what you get back to the list Chris > On 9 Dec 2021, at 10:49 pm, SeaQuench wrote: > > ? > After downloading and installing the latest MacPorts for Catalina, I followed the instructions to migrate MacPorts: https://trac.macports.org/wiki/Migration > Reinstalling the ports went without issue until Step 3e: `sudo ./restore_ports.tcl myports.txt` > Executing that command resulted in the error I presented initially: > ---> Computing dependencies for python38 > Error: Dependency 'openssl3' not found. > ---> Computing dependencies for python39 > Error: Dependency 'openssl3' not found. > > Is that to be expected on a fresh install (before performing a sync)? I acknowledge that this outcome may result from the use of git versus rsync in keeping MacPorts up to date. I am behind a firewall, so i must use git to sync rather than use rsync. > https://trac.macports.org/wiki/howto/SyncingWithGit > If i substitute the command `sudo port -v sync` for the command `sudo port selfupdate` - as usual - I can now install openssl without error, and all dependencies are found after re-executing: `sudo ./restore_ports.tcl myports.txt` > > Any additional advice welcome. Thanks for the tip on migration, Chris! > > Sent with ProtonMail Secure Email. > > ??????? Original Message ??????? >> On Thursday, December 9th, 2021 at 2:47 PM, Chris Jones wrote: >> >> >> >> Did you follow the migration guide when moving to a new major os version ? >> >> https://trac.macports.org/wiki/Migration >> >> If not, follow it now, to wipe out your ports and reinstall them correctly for the new os. >> >> If you did, your ports tree seems to be very out of date. Then try, >> >> > sudo port selfupdate >> > sudo port sync >> > sudo port upgrade outdated >> >> Chris >> >>>> On 9 Dec 2021, at 6:53 pm, SeaQuench via macports-users wrote: >>> ? >>> >>> >>> After applying an update to MacOS last August, the python ports are reporting a dependency on either openssl11 or openssl3, neither of which are to be found in the (local?) index for MacPorts, according to the error I have received, copied below. While I am prompted to report a bug, I presume I am not in a novel situation. Could someone advise me as to how to proceed? I am running MacPorts 2.6.2 on MacOS 10.15.7 with XCode 12.4 installed. >>> $ sudo port install python39 >>> >>> >>> >>> >>> Warning: No port openssl3 found in the index. >>> ---> Computing dependencies for openssl >>> Error: Dependency 'openssl3' not found. >>> Error: Unable to execute port: upgrade openssl failed >>> >>> >>> >>> >>> $ sudo port install openssl >>> >>> >>> >>> >>> ---> Computing dependencies for openssl >>> Error: Dependency 'openssl3' not found. >>> Error: Follow https://guide.macports.org/#project.tickets to report a bug. >>> Error: Processing of port openssl failed >>> >>> >>> $ sudo port -n upgrade --force python38 >>> ---> Computing dependencies for python38 >>> ---> Fetching archive for python38 >>> ---> Attempting to fetch python38-3.8.12_4+optimizations.darwin_19.x86_64.tbz2 from https://packages.macports.org/python38 >>> ---> Attempting to fetch python38-3.8.12_4+optimizations.darwin_19.x86_64.tbz2.rmd160 from https://packages.macports.org/python38 >>> ---> Installing python38 @3.8.12_4+optimizations >>> ---> Cleaning python38 >>> ---> Computing dependencies for python38 >>> ---> Deactivating python38 @3.8.11_0 >>> ---> Cleaning python38 >>> ---> Activating python38 @3.8.12_4+optimizations >>> ---> Cleaning python38 >>> ---> Updating database of binaries >>> ---> Scanning binaries for linking errors >>> ---> Found 18 broken files, matching files to ports >>> ---> Found 4 broken ports, determining rebuild order >>> You can always run 'port rev-upgrade' again to fix errors. >>> The following ports will be rebuilt: >>> python38 @3.8.12+optimizations >>> python39 @3.9.6 >>> glib2 @2.58.3+x11 >>> gobject-introspection @1.60.2 >>> Continue? [Y/n]: y >>> Warning: No port openssl3 found in the index. >>> ---> Computing dependencies for openssl >>> Error: Dependency 'openssl3' not found. >>> Error: rev-upgrade failed: Error rebuilding python38 >>> Error: Follow https://guide.macports.org/#project.tickets to report a bug. >>> >>> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ryandesign at macports.org Fri Dec 10 08:35:02 2021 From: ryandesign at macports.org (Ryan Schmidt) Date: Fri, 10 Dec 2021 02:35:02 -0600 Subject: python ports depend on openssl not in index In-Reply-To: <4ACEB13C-941D-46CB-A072-88CD6FC3F4BF@hep.phy.cam.ac.uk> References: <6ka4vAHxC1FypGcxmcw1MBr1KyplHKA3_RgHPvz74ArBDv-0Q3emV5gs0hW1tnqVinpPZTjw-jjMuNtp9PYxBSC4VM4KuOCTDuETULIaae0=@protonmail.com> <4ACEB13C-941D-46CB-A072-88CD6FC3F4BF@hep.phy.cam.ac.uk> Message-ID: On Dec 10, 2021, at 02:29, Chris Jones wrote: > > On 9 Dec 2021, at 10:49 pm, SeaQuench wrote: >> >> ? >> After downloading and installing the latest MacPorts for Catalina, I followed the instructions to migrate MacPorts: https://trac.macports.org/wiki/Migration >> Reinstalling the ports went without issue until Step 3e: `sudo ./restore_ports.tcl myports.txt` >> Executing that command resulted in the error I presented initially: >> ---> Computing dependencies for python38 >> Error: Dependency 'openssl3' not found. >> ---> Computing dependencies for python39 >> Error: Dependency 'openssl3' not found. >> >> Is that to be expected on a fresh install (before performing a sync)? I acknowledge that this outcome may result from the use of git versus rsync in keeping MacPorts up to date. I am behind a firewall, so i must use git to sync rather than use rsync. >> https://trac.macports.org/wiki/howto/SyncingWithGit >> If i substitute the command `sudo port -v sync` for the command `sudo port selfupdate` - as usual - I can now install openssl without error, and all dependencies are found after re-executing: `sudo ./restore_ports.tcl myports.txt` > > We need to see why you are not finding the openssl3 port, as that has been available for some time. > > Please run > > sudo port -d sync > > And post what you get back to the list They already said that after running "sudo port sync", everything is working. "sudo port selfupdate" should selfupdate (update MacPorts base) and sync (update ports tree). If updating base failed for some reason, then it might not update the ports tree either. You mentioned being behind a firewall that prevents you from syncing with rsync. selfupdate has no option but to use rsync, so that would be a likely explanation for why selfupdate doesn't work for you, and why you should not use selfupdate and should instead (i) update MacPorts base manually when a new version is available, using an installer from our web site and (ii) sync to update ports. From audvare at gmail.com Fri Dec 10 12:57:39 2021 From: audvare at gmail.com (Andrew Udvare) Date: Fri, 10 Dec 2021 07:57:39 -0500 Subject: Sandbox issues with Swift Package Manager Message-ID: <4d8e9fbb-50db-f3d7-013b-db1290fda0cf@gmail.com> I am testing out how to build Xcode-based packages that use Swift Package Manager (SPM) and it seems even with 'hacks' to make Xcode not do any downloading of code, there's still some network activity (or something the sandbox is blocking) that I have not figured out. Example port: https://github.com/Tatsh/ports/tree/master/aqua/eul Try using this with `port -d destroot` to see everything. You will get this error: Resolve Package Graph sandbox-exec: sandbox_apply: Operation not permitted sandbox-exec: sandbox_apply: Operation not permitted sandbox-exec: sandbox_apply: Operation not permitted sandbox-exec: sandbox_apply: Operation not permitted cannot update Package.resolved file because automatic resolution is disabledxcodebuild: error: Could not resolve package dependencies: sandbox-exec: sandbox_apply: Operation not permitted sandbox-exec: sandbox_apply: Operation not permitted sandbox-exec: sandbox_apply: Operation not permitted sandbox-exec: sandbox_apply: Operation not permitted cannot update Package.resolved file because automatic resolution is disabled fatalError Thoughts on how this can be worked around? If anyone figures out what these blocked operations were I'd be very interested in knowing. Thanks Andrew -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From seaquench at protonmail.com Fri Dec 10 15:13:50 2021 From: seaquench at protonmail.com (SeaQuench) Date: Fri, 10 Dec 2021 15:13:50 +0000 Subject: python ports depend on openssl not in index In-Reply-To: References: <6ka4vAHxC1FypGcxmcw1MBr1KyplHKA3_RgHPvz74ArBDv-0Q3emV5gs0hW1tnqVinpPZTjw-jjMuNtp9PYxBSC4VM4KuOCTDuETULIaae0=@protonmail.com> <4ACEB13C-941D-46CB-A072-88CD6FC3F4BF@hep.phy.cam.ac.uk> Message-ID: Ryan is correct; I had been sync'ing my port index successfully, but MacPorts itself grew stale due to my being unable to run selfupdate. The MacPorts Migration Guide suggested a manual update (i.e. reinstall) which I believe got me going again. Thanks guys! ~SeaQuench ??????? Original Message ??????? On Friday, December 10th, 2021 at 3:35 AM, Ryan Schmidt wrote: > On Dec 10, 2021, at 02:29, Chris Jones wrote: > > > On 9 Dec 2021, at 10:49 pm, SeaQuench wrote: > > > > > After downloading and installing the latest MacPorts for Catalina, I followed the instructions to migrate MacPorts: https://trac.macports.org/wiki/Migration > > > > > > Reinstalling the ports went without issue until Step 3e: `sudo ./restore_ports.tcl myports.txt` > > > > > > Executing that command resulted in the error I presented initially: > > > > > > ---> Computing dependencies for python38 > > > > > > Error: Dependency 'openssl3' not found. > > > > > > ---> Computing dependencies for python39 > > > > > > Error: Dependency 'openssl3' not found. > > > > > > Is that to be expected on a fresh install (before performing a sync)? I acknowledge that this outcome may result from the use of git versus rsync in keeping MacPorts up to date. I am behind a firewall, so i must use git to sync rather than use rsync. > > > > > > https://trac.macports.org/wiki/howto/SyncingWithGit > > > > > > If i substitute the command `sudo port -v sync` for the command `sudo port selfupdate` - as usual - I can now install openssl without error, and all dependencies are found after re-executing: `sudo ./restore_ports.tcl myports.txt` > > > > We need to see why you are not finding the openssl3 port, as that has been available for some time. > > > > Please run > > > > sudo port -d sync > > > > And post what you get back to the list > > They already said that after running "sudo port sync", everything is working. > > "sudo port selfupdate" should selfupdate (update MacPorts base) and sync (update ports tree). If updating base failed for some reason, then it might not update the ports tree either. You mentioned being behind a firewall that prevents you from syncing with rsync. selfupdate has no option but to use rsync, so that would be a likely explanation for why selfupdate doesn't work for you, and why you should not use selfupdate and should instead (i) update MacPorts base manually when a new version is available, using an installer from our web site and (ii) sync to update ports. From jonesc at hep.phy.cam.ac.uk Fri Dec 10 15:24:15 2021 From: jonesc at hep.phy.cam.ac.uk (Christopher Jones) Date: Fri, 10 Dec 2021 15:24:15 +0000 Subject: python ports depend on openssl not in index In-Reply-To: References: <6ka4vAHxC1FypGcxmcw1MBr1KyplHKA3_RgHPvz74ArBDv-0Q3emV5gs0hW1tnqVinpPZTjw-jjMuNtp9PYxBSC4VM4KuOCTDuETULIaae0=@protonmail.com> <4ACEB13C-941D-46CB-A072-88CD6FC3F4BF@hep.phy.cam.ac.uk> Message-ID: Just to be clear, are you saying running > sudo port selfupdate ran without warnings or error, but did not actually update ? If thats the case we should file a bug against base as if the rsync fails it should indicate this to the user ? cheers Chris > On 10 Dec 2021, at 3:13 pm, SeaQuench wrote: > > Ryan is correct; I had been sync'ing my port index successfully, but MacPorts itself grew stale due to my being unable to run selfupdate. The MacPorts Migration Guide suggested a manual update (i.e. reinstall) which I believe got me going again. Thanks guys! ~SeaQuench > > ??????? Original Message ??????? > > On Friday, December 10th, 2021 at 3:35 AM, Ryan Schmidt wrote: > >> On Dec 10, 2021, at 02:29, Chris Jones wrote: >> >>> On 9 Dec 2021, at 10:49 pm, SeaQuench wrote: >>> >>>> After downloading and installing the latest MacPorts for Catalina, I followed the instructions to migrate MacPorts: https://trac.macports.org/wiki/Migration >>>> >>>> Reinstalling the ports went without issue until Step 3e: `sudo ./restore_ports.tcl myports.txt` >>>> >>>> Executing that command resulted in the error I presented initially: >>>> >>>> ---> Computing dependencies for python38 >>>> >>>> Error: Dependency 'openssl3' not found. >>>> >>>> ---> Computing dependencies for python39 >>>> >>>> Error: Dependency 'openssl3' not found. >>>> >>>> Is that to be expected on a fresh install (before performing a sync)? I acknowledge that this outcome may result from the use of git versus rsync in keeping MacPorts up to date. I am behind a firewall, so i must use git to sync rather than use rsync. >>>> >>>> https://trac.macports.org/wiki/howto/SyncingWithGit >>>> >>>> If i substitute the command `sudo port -v sync` for the command `sudo port selfupdate` - as usual - I can now install openssl without error, and all dependencies are found after re-executing: `sudo ./restore_ports.tcl myports.txt` >>> >>> We need to see why you are not finding the openssl3 port, as that has been available for some time. >>> >>> Please run >>> >>> sudo port -d sync >>> >>> And post what you get back to the list >> >> They already said that after running "sudo port sync", everything is working. >> >> "sudo port selfupdate" should selfupdate (update MacPorts base) and sync (update ports tree). If updating base failed for some reason, then it might not update the ports tree either. You mentioned being behind a firewall that prevents you from syncing with rsync. selfupdate has no option but to use rsync, so that would be a likely explanation for why selfupdate doesn't work for you, and why you should not use selfupdate and should instead (i) update MacPorts base manually when a new version is available, using an installer from our web site and (ii) sync to update ports. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 1930 bytes Desc: not available URL: From ryandesign at macports.org Fri Dec 10 17:24:01 2021 From: ryandesign at macports.org (Ryan Schmidt) Date: Fri, 10 Dec 2021 11:24:01 -0600 Subject: Trouble with upgrade outdated In-Reply-To: <1C586345-2EFA-45D9-837E-20079F01FC3F@gmail.com> References: <1C586345-2EFA-45D9-837E-20079F01FC3F@gmail.com> Message-ID: On Sep 28, 2021, at 15:31, Tobias Welti wrote: > I have trouble using port upgrade outdated since a few weeks ago. I just receive the following message: > ======= > $ sudo port upgrade outdated > Error: python39: Error executing universal: can't read "configure.sysroot": no such variable > Error: Unable to open port: Error evaluating variants > Error: Follow https://guide.macports.org/#project.tickets to report a bug. > > > ===== > > I have already tried to select the python3 version to python39, which completes without error. But the behaviour of upgrade outdated remains the same. > > Is there a known fix to this? Sorry for the late response to this. If you are still seeing this problem, I'd suggest first making sure you have the latest version of MacPorts, 2.7.1. Run `port version` to find out. Run `sudo port selfupdate` to upgrade MacPorts and the portfiles. If you still get the configure.sysroot error when upgrading outdated ports, get the debug output by using the `-d` flag: `sudo port -d upgrade outdated`, and show us the output of that. Hopefully that might shed some light on why it's happening. From mark at macports.org Fri Dec 10 18:01:09 2021 From: mark at macports.org (Mark Anderson) Date: Fri, 10 Dec 2021 13:01:09 -0500 Subject: Sandbox issues with Swift Package Manager In-Reply-To: <4d8e9fbb-50db-f3d7-013b-db1290fda0cf@gmail.com> References: <4d8e9fbb-50db-f3d7-013b-db1290fda0cf@gmail.com> Message-ID: SPM and Workspace builds need to be added to the XCode portgroup - it's something that I've been working on for a while. I'm a little surprised the sandbox is involved at all. Is it XCode's sandbox complaining? Or is it Terminal? Make sure the terminal has full disk access. ?Mark _______________________ Mark E. Anderson MacPorts Trac WikiPage GitHub Profile On Fri, Dec 10, 2021 at 7:57 AM Andrew Udvare wrote: > I am testing out how to build Xcode-based packages that use Swift > Package Manager (SPM) and it seems even with 'hacks' to make Xcode not > do any downloading of code, there's still some network activity (or > something the sandbox is blocking) that I have not figured out. > > Example port: https://github.com/Tatsh/ports/tree/master/aqua/eul > > Try using this with `port -d destroot` to see everything. You will get > this error: > > Resolve Package Graph > > sandbox-exec: sandbox_apply: Operation not permitted > > sandbox-exec: sandbox_apply: Operation not permitted > > sandbox-exec: sandbox_apply: Operation not permitted > > sandbox-exec: sandbox_apply: Operation not permitted > > cannot update Package.resolved file because automatic resolution is > disabledxcodebuild: error: Could not resolve package dependencies: > sandbox-exec: sandbox_apply: Operation not permitted > sandbox-exec: sandbox_apply: Operation not permitted > sandbox-exec: sandbox_apply: Operation not permitted > sandbox-exec: sandbox_apply: Operation not permitted > cannot update Package.resolved file because automatic resolution is > disabled > fatalError > > Thoughts on how this can be worked around? If anyone figures out what > these blocked operations were I'd be very interested in knowing. > > Thanks > Andrew > -------------- next part -------------- An HTML attachment was scrubbed... URL: From seaquench at protonmail.com Fri Dec 10 19:18:10 2021 From: seaquench at protonmail.com (SeaQuench) Date: Fri, 10 Dec 2021 19:18:10 +0000 Subject: python ports depend on openssl not in index In-Reply-To: References: <6ka4vAHxC1FypGcxmcw1MBr1KyplHKA3_RgHPvz74ArBDv-0Q3emV5gs0hW1tnqVinpPZTjw-jjMuNtp9PYxBSC4VM4KuOCTDuETULIaae0=@protonmail.com> <4ACEB13C-941D-46CB-A072-88CD6FC3F4BF@hep.phy.cam.ac.uk> Message-ID: I am behind a firewall, so this is the following is predictable: $ sudo port -v selfupdate ---> Updating MacPorts base sources using rsync rsync: failed to connect to rsync.macports.org: Operation timed out (60) rsync error: error in socket IO (code 10) at /AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/rsync/rsync-54.120.1/rsync/clientserver.c(106) [receiver=2.6.9] Command failed: /usr/bin/rsync -rtzvl --delete-after rsync://rsync.macports.org/macports/release/tarballs/base.tar /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs Exit code: 10 Error: Error synchronizing MacPorts sources: command execution failed ??????? Original Message ??????? On Friday, December 10th, 2021 at 10:24 AM, Christopher Jones wrote: > Just to be clear, are you saying running > > > sudo port selfupdate > > ran without warnings or error, but did not actually update ? If thats the case we should file a bug against base as if the rsync fails it should indicate this to the user ? > > cheers Chris > > > On 10 Dec 2021, at 3:13 pm, SeaQuench seaquench at protonmail.com wrote: > > > > Ryan is correct; I had been sync'ing my port index successfully, but MacPorts itself grew stale due to my being unable to run selfupdate. The MacPorts Migration Guide suggested a manual update (i.e. reinstall) which I believe got me going again. Thanks guys! ~SeaQuench > > > > ??????? Original Message ??????? > > > > On Friday, December 10th, 2021 at 3:35 AM, Ryan Schmidt ryandesign at macports.org wrote: > > > > > On Dec 10, 2021, at 02:29, Chris Jones wrote: > > > > > > > On 9 Dec 2021, at 10:49 pm, SeaQuench wrote: > > > > > > > > > After downloading and installing the latest MacPorts for Catalina, I followed the instructions to migrate MacPorts: https://trac.macports.org/wiki/Migration > > > > > > > > > > Reinstalling the ports went without issue until Step 3e: `sudo ./restore_ports.tcl myports.txt` > > > > > > > > > > Executing that command resulted in the error I presented initially: > > > > > > > > > > ---> Computing dependencies for python38 > > > > > > > > > > Error: Dependency 'openssl3' not found. > > > > > > > > > > ---> Computing dependencies for python39 > > > > > > > > > > Error: Dependency 'openssl3' not found. > > > > > > > > > > Is that to be expected on a fresh install (before performing a sync)? I acknowledge that this outcome may result from the use of git versus rsync in keeping MacPorts up to date. I am behind a firewall, so i must use git to sync rather than use rsync. > > > > > > > > > > https://trac.macports.org/wiki/howto/SyncingWithGit > > > > > > > > > > If i substitute the command `sudo port -v sync` for the command `sudo port selfupdate` - as usual - I can now install openssl without error, and all dependencies are found after re-executing: `sudo ./restore_ports.tcl myports.txt` > > > > > > > > We need to see why you are not finding the openssl3 port, as that has been available for some time. > > > > > > > > Please run > > > > > > > > sudo port -d sync > > > > > > > > And post what you get back to the list > > > > > > They already said that after running "sudo port sync", everything is working. > > > > > > "sudo port selfupdate" should selfupdate (update MacPorts base) and sync (update ports tree). If updating base failed for some reason, then it might not update the ports tree either. You mentioned being behind a firewall that prevents you from syncing with rsync. selfupdate has no option but to use rsync, so that would be a likely explanation for why selfupdate doesn't work for you, and why you should not use selfupdate and should instead (i) update MacPorts base manually when a new version is available, using an installer from our web site and (ii) sync to update ports. From jonesc at hep.phy.cam.ac.uk Fri Dec 10 19:21:07 2021 From: jonesc at hep.phy.cam.ac.uk (Chris Jones) Date: Fri, 10 Dec 2021 19:21:07 +0000 Subject: python ports depend on openssl not in index In-Reply-To: References: Message-ID: <72B1059B-934C-4B90-9367-E085FB16C3FA@hep.phy.cam.ac.uk> Hi, Yes, the error is expected. What i am asking is if you get any indication or not that there was an issue when you run without the verbose flag. If not, then i think thats a bug we should address. Chris > On 10 Dec 2021, at 7:18 pm, SeaQuench wrote: > > ?I am behind a firewall, so this is the following is predictable: > > $ sudo port -v selfupdate > ---> Updating MacPorts base sources using rsync > rsync: failed to connect to rsync.macports.org: Operation timed out (60) > rsync error: error in socket IO (code 10) at /AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/rsync/rsync-54.120.1/rsync/clientserver.c(106) [receiver=2.6.9] > Command failed: /usr/bin/rsync -rtzvl --delete-after rsync://rsync.macports.org/macports/release/tarballs/base.tar /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs > Exit code: 10 > Error: Error synchronizing MacPorts sources: command execution failed > > ??????? Original Message ??????? > >> On Friday, December 10th, 2021 at 10:24 AM, Christopher Jones wrote: >> >> Just to be clear, are you saying running >> >>> sudo port selfupdate >> >> ran without warnings or error, but did not actually update ? If thats the case we should file a bug against base as if the rsync fails it should indicate this to the user ? >> >> cheers Chris >> >>>> On 10 Dec 2021, at 3:13 pm, SeaQuench seaquench at protonmail.com wrote: >>> >>> Ryan is correct; I had been sync'ing my port index successfully, but MacPorts itself grew stale due to my being unable to run selfupdate. The MacPorts Migration Guide suggested a manual update (i.e. reinstall) which I believe got me going again. Thanks guys! ~SeaQuench >>> >>> ??????? Original Message ??????? >>> >>>> On Friday, December 10th, 2021 at 3:35 AM, Ryan Schmidt ryandesign at macports.org wrote: >>> >>>> On Dec 10, 2021, at 02:29, Chris Jones wrote: >>>> >>>>> On 9 Dec 2021, at 10:49 pm, SeaQuench wrote: >>>>> >>>>>> After downloading and installing the latest MacPorts for Catalina, I followed the instructions to migrate MacPorts: https://trac.macports.org/wiki/Migration >>>>>> >>>>>> Reinstalling the ports went without issue until Step 3e: `sudo ./restore_ports.tcl myports.txt` >>>>>> >>>>>> Executing that command resulted in the error I presented initially: >>>>>> >>>>>> ---> Computing dependencies for python38 >>>>>> >>>>>> Error: Dependency 'openssl3' not found. >>>>>> >>>>>> ---> Computing dependencies for python39 >>>>>> >>>>>> Error: Dependency 'openssl3' not found. >>>>>> >>>>>> Is that to be expected on a fresh install (before performing a sync)? I acknowledge that this outcome may result from the use of git versus rsync in keeping MacPorts up to date. I am behind a firewall, so i must use git to sync rather than use rsync. >>>>>> >>>>>> https://trac.macports.org/wiki/howto/SyncingWithGit >>>>>> >>>>>> If i substitute the command `sudo port -v sync` for the command `sudo port selfupdate` - as usual - I can now install openssl without error, and all dependencies are found after re-executing: `sudo ./restore_ports.tcl myports.txt` >>>>> >>>>> We need to see why you are not finding the openssl3 port, as that has been available for some time. >>>>> >>>>> Please run >>>>> >>>>> sudo port -d sync >>>>> >>>>> And post what you get back to the list >>>> >>>> They already said that after running "sudo port sync", everything is working. >>>> >>>> "sudo port selfupdate" should selfupdate (update MacPorts base) and sync (update ports tree). If updating base failed for some reason, then it might not update the ports tree either. You mentioned being behind a firewall that prevents you from syncing with rsync. selfupdate has no option but to use rsync, so that would be a likely explanation for why selfupdate doesn't work for you, and why you should not use selfupdate and should instead (i) update MacPorts base manually when a new version is available, using an installer from our web site and (ii) sync to update ports. From stephen.langer at nist.gov Fri Dec 10 19:51:27 2021 From: stephen.langer at nist.gov (Langer, Stephen A. (Fed)) Date: Fri, 10 Dec 2021 19:51:27 +0000 Subject: gtk3 problem Message-ID: <575A4954-7C02-4DA7-963A-D0A71C258CE3@contoso.com> Hi -- Is anyone running gtk3 programs on an M1 or on Monterey? The following simple script crashes on ?an M1 Mini with Monterey, when run with python 2.7: import gi gi.require_version("Gtk", "3.0") from gi.repository import Gtk window = Gtk.Window(Gtk.WindowType.TOPLEVEL, title="test") The error message is "Trace/BPT trap: 5". The same program runs without error on an Intel CPU and Big Sur. Unfortunately I can't change the OS on either machine so I can't tell if the problem is due to the OS or the processor, or both. Thanks. -- Steve From seaquench at protonmail.com Fri Dec 10 20:07:32 2021 From: seaquench at protonmail.com (SeaQuench) Date: Fri, 10 Dec 2021 20:07:32 +0000 Subject: python ports depend on openssl not in index In-Reply-To: <72B1059B-934C-4B90-9367-E085FB16C3FA@hep.phy.cam.ac.uk> References: <72B1059B-934C-4B90-9367-E085FB16C3FA@hep.phy.cam.ac.uk> Message-ID: Output of selfupdate as requested: $ sudo port selfupdate ---> Updating MacPorts base sources using rsync Error: Error synchronizing MacPorts sources: command execution failed Please run `port -v selfupdate' for details. Error: /opt/local/bin/port: port selfupdate failed: Error synchronizing MacPorts sources: command execution failed [To be clear, I consider my problem to be resolved, thanks.] ??????? Original Message ??????? On Friday, December 10th, 2021 at 2:21 PM, Chris Jones wrote: > Hi, > > Yes, the error is expected. What i am asking is if you get any indication or not that there was an issue when you run without the verbose flag. If not, then i think thats a bug we should address. > > Chris > > > On 10 Dec 2021, at 7:18 pm, SeaQuench seaquench at protonmail.com wrote: > > > > I am behind a firewall, so this is the following is predictable: > > > > $ sudo port -v selfupdate > > > > ---> Updating MacPorts base sources using rsync > > > > rsync: failed to connect to rsync.macports.org: Operation timed out (60) > > > > rsync error: error in socket IO (code 10) at /AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/rsync/rsync-54.120.1/rsync/clientserver.c(106) [receiver=2.6.9] > > > > Command failed: /usr/bin/rsync -rtzvl --delete-after rsync://rsync.macports.org/macports/release/tarballs/base.tar /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs > > > > Exit code: 10 > > > > Error: Error synchronizing MacPorts sources: command execution failed > > > > ??????? Original Message ??????? > > > > > On Friday, December 10th, 2021 at 10:24 AM, Christopher Jones jonesc at hep.phy.cam.ac.uk wrote: > > > > > > Just to be clear, are you saying running > > > > > > > sudo port selfupdate > > > > > > ran without warnings or error, but did not actually update ? If thats the case we should file a bug against base as if the rsync fails it should indicate this to the user ? > > > > > > cheers Chris > > > > > > > > On 10 Dec 2021, at 3:13 pm, SeaQuench seaquench at protonmail.com wrote: > > > > > > > > Ryan is correct; I had been sync'ing my port index successfully, but MacPorts itself grew stale due to my being unable to run selfupdate. The MacPorts Migration Guide suggested a manual update (i.e. reinstall) which I believe got me going again. Thanks guys! ~SeaQuench > > > > > > > > ??????? Original Message ??????? > > > > > > > > > On Friday, December 10th, 2021 at 3:35 AM, Ryan Schmidt ryandesign at macports.org wrote: > > > > > > > > > On Dec 10, 2021, at 02:29, Chris Jones wrote: > > > > > > > > > > > On 9 Dec 2021, at 10:49 pm, SeaQuench wrote: > > > > > > > > > > > > > After downloading and installing the latest MacPorts for Catalina, I followed the instructions to migrate MacPorts: https://trac.macports.org/wiki/Migration > > > > > > > > > > > > > > Reinstalling the ports went without issue until Step 3e: `sudo ./restore_ports.tcl myports.txt` > > > > > > > > > > > > > > Executing that command resulted in the error I presented initially: > > > > > > > > > > > > > > ---> Computing dependencies for python38 > > > > > > > > > > > > > > Error: Dependency 'openssl3' not found. > > > > > > > > > > > > > > ---> Computing dependencies for python39 > > > > > > > > > > > > > > Error: Dependency 'openssl3' not found. > > > > > > > > > > > > > > Is that to be expected on a fresh install (before performing a sync)? I acknowledge that this outcome may result from the use of git versus rsync in keeping MacPorts up to date. I am behind a firewall, so i must use git to sync rather than use rsync. > > > > > > > > > > > > > > https://trac.macports.org/wiki/howto/SyncingWithGit > > > > > > > > > > > > > > If i substitute the command `sudo port -v sync` for the command `sudo port selfupdate` - as usual - I can now install openssl without error, and all dependencies are found after re-executing: `sudo ./restore_ports.tcl myports.txt` > > > > > > > > > > > > We need to see why you are not finding the openssl3 port, as that has been available for some time. > > > > > > > > > > > > Please run > > > > > > > > > > > > sudo port -d sync > > > > > > > > > > > > And post what you get back to the list > > > > > > > > > > They already said that after running "sudo port sync", everything is working. > > > > > > > > > > "sudo port selfupdate" should selfupdate (update MacPorts base) and sync (update ports tree). If updating base failed for some reason, then it might not update the ports tree either. You mentioned being behind a firewall that prevents you from syncing with rsync. selfupdate has no option but to use rsync, so that would be a likely explanation for why selfupdate doesn't work for you, and why you should not use selfupdate and should instead (i) update MacPorts base manually when a new version is available, using an installer from our web site and (ii) sync to update ports. From jonesc at hep.phy.cam.ac.uk Fri Dec 10 20:09:17 2021 From: jonesc at hep.phy.cam.ac.uk (Chris Jones) Date: Fri, 10 Dec 2021 20:09:17 +0000 Subject: python ports depend on openssl not in index In-Reply-To: References: Message-ID: <31FE14EF-F6B8-408C-9637-468D502C3EBE@hep.phy.cam.ac.uk> > On 10 Dec 2021, at 8:07 pm, SeaQuench wrote: > > ?Output of selfupdate as requested: > > $ sudo port selfupdate > ---> Updating MacPorts base sources using rsync > Error: Error synchronizing MacPorts sources: command execution failed > Please run `port -v selfupdate' for details. > Error: /opt/local/bin/port: port selfupdate failed: Error synchronizing MacPorts sources: command execution failed > > [To be clear, I consider my problem to be resolved, thanks.] Yes, the above is clear, and I guess the reason behind this thread is you did not pay enough attention to it in the first case ;) Chris > > ??????? Original Message ??????? > >> On Friday, December 10th, 2021 at 2:21 PM, Chris Jones wrote: >> >> Hi, >> >> Yes, the error is expected. What i am asking is if you get any indication or not that there was an issue when you run without the verbose flag. If not, then i think thats a bug we should address. >> >> Chris >> >>>> On 10 Dec 2021, at 7:18 pm, SeaQuench seaquench at protonmail.com wrote: >>> >>> I am behind a firewall, so this is the following is predictable: >>> >>> $ sudo port -v selfupdate >>> >>> ---> Updating MacPorts base sources using rsync >>> >>> rsync: failed to connect to rsync.macports.org: Operation timed out (60) >>> >>> rsync error: error in socket IO (code 10) at /AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/rsync/rsync-54.120.1/rsync/clientserver.c(106) [receiver=2.6.9] >>> >>> Command failed: /usr/bin/rsync -rtzvl --delete-after rsync://rsync.macports.org/macports/release/tarballs/base.tar /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs >>> >>> Exit code: 10 >>> >>> Error: Error synchronizing MacPorts sources: command execution failed >>> >>> ??????? Original Message ??????? >>> >>>> On Friday, December 10th, 2021 at 10:24 AM, Christopher Jones jonesc at hep.phy.cam.ac.uk wrote: >>>> >>>> Just to be clear, are you saying running >>>> >>>>> sudo port selfupdate >>>> >>>> ran without warnings or error, but did not actually update ? If thats the case we should file a bug against base as if the rsync fails it should indicate this to the user ? >>>> >>>> cheers Chris >>>> >>>>>> On 10 Dec 2021, at 3:13 pm, SeaQuench seaquench at protonmail.com wrote: >>>>> >>>>> Ryan is correct; I had been sync'ing my port index successfully, but MacPorts itself grew stale due to my being unable to run selfupdate. The MacPorts Migration Guide suggested a manual update (i.e. reinstall) which I believe got me going again. Thanks guys! ~SeaQuench >>>>> >>>>> ??????? Original Message ??????? >>>>> >>>>>> On Friday, December 10th, 2021 at 3:35 AM, Ryan Schmidt ryandesign at macports.org wrote: >>>>> >>>>>> On Dec 10, 2021, at 02:29, Chris Jones wrote: >>>>>> >>>>>>> On 9 Dec 2021, at 10:49 pm, SeaQuench wrote: >>>>>>> >>>>>>>> After downloading and installing the latest MacPorts for Catalina, I followed the instructions to migrate MacPorts: https://trac.macports.org/wiki/Migration >>>>>>>> >>>>>>>> Reinstalling the ports went without issue until Step 3e: `sudo ./restore_ports.tcl myports.txt` >>>>>>>> >>>>>>>> Executing that command resulted in the error I presented initially: >>>>>>>> >>>>>>>> ---> Computing dependencies for python38 >>>>>>>> >>>>>>>> Error: Dependency 'openssl3' not found. >>>>>>>> >>>>>>>> ---> Computing dependencies for python39 >>>>>>>> >>>>>>>> Error: Dependency 'openssl3' not found. >>>>>>>> >>>>>>>> Is that to be expected on a fresh install (before performing a sync)? I acknowledge that this outcome may result from the use of git versus rsync in keeping MacPorts up to date. I am behind a firewall, so i must use git to sync rather than use rsync. >>>>>>>> >>>>>>>> https://trac.macports.org/wiki/howto/SyncingWithGit >>>>>>>> >>>>>>>> If i substitute the command `sudo port -v sync` for the command `sudo port selfupdate` - as usual - I can now install openssl without error, and all dependencies are found after re-executing: `sudo ./restore_ports.tcl myports.txt` >>>>>>> >>>>>>> We need to see why you are not finding the openssl3 port, as that has been available for some time. >>>>>>> >>>>>>> Please run >>>>>>> >>>>>>> sudo port -d sync >>>>>>> >>>>>>> And post what you get back to the list >>>>>> >>>>>> They already said that after running "sudo port sync", everything is working. >>>>>> >>>>>> "sudo port selfupdate" should selfupdate (update MacPorts base) and sync (update ports tree). If updating base failed for some reason, then it might not update the ports tree either. You mentioned being behind a firewall that prevents you from syncing with rsync. selfupdate has no option but to use rsync, so that would be a likely explanation for why selfupdate doesn't work for you, and why you should not use selfupdate and should instead (i) update MacPorts base manually when a new version is available, using an installer from our web site and (ii) sync to update ports. From audvare at gmail.com Fri Dec 10 22:12:17 2021 From: audvare at gmail.com (Andrew Udvare) Date: Fri, 10 Dec 2021 17:12:17 -0500 Subject: Sandbox issues with Swift Package Manager In-Reply-To: References: <4d8e9fbb-50db-f3d7-013b-db1290fda0cf@gmail.com> Message-ID: <050A5C9C-8FDE-4453-B221-D76D6236817C@gmail.com> > On 2021-12-10, at 13:01, Mark Anderson wrote: > > SPM and Workspace builds need to be added to the XCode portgroup - it's something that I've been working on for a while. > > I'm a little surprised the sandbox is involved at all. Is it XCode's sandbox complaining? Or is it Terminal? Make sure the terminal has full disk access. This is sandbox-exec(1) complaining. When I run the same xcodebuild command without MacPorts the build works fine in the same terminal. https://github.com/macports/macports-base/blob/master/src/port1.0/portsandbox.tcl From mark at macports.org Fri Dec 10 22:24:00 2021 From: mark at macports.org (Mark Anderson) Date: Fri, 10 Dec 2021 17:24:00 -0500 Subject: Sandbox issues with Swift Package Manager In-Reply-To: <050A5C9C-8FDE-4453-B221-D76D6236817C@gmail.com> References: <4d8e9fbb-50db-f3d7-013b-db1290fda0cf@gmail.com> <050A5C9C-8FDE-4453-B221-D76D6236817C@gmail.com> Message-ID: Ah ok , that's above my paygrade right now - I had no idea we were doing that. I've copied the dev list - I think the response will be better over there. ?Mark _______________________ Mark E. Anderson MacPorts Trac WikiPage GitHub Profile On Fri, Dec 10, 2021 at 5:12 PM Andrew Udvare wrote: > > > On 2021-12-10, at 13:01, Mark Anderson wrote: > > > > SPM and Workspace builds need to be added to the XCode portgroup - it's > something that I've been working on for a while. > > > > I'm a little surprised the sandbox is involved at all. Is it XCode's > sandbox complaining? Or is it Terminal? Make sure the terminal has full > disk access. > > This is sandbox-exec(1) complaining. When I run the same xcodebuild > command without MacPorts the build works fine in the same terminal. > > > https://github.com/macports/macports-base/blob/master/src/port1.0/portsandbox.tcl -------------- next part -------------- An HTML attachment was scrubbed... URL: From fgyamauti2 at gmail.com Sat Dec 11 05:11:01 2021 From: fgyamauti2 at gmail.com (fgyamauti2 fgyamauti2) Date: Sat, 11 Dec 2021 02:11:01 -0300 Subject: Can some ports install config files inside '/usr/local/etc'? Message-ID: Hi, Apparently some ports that I've installed are making directories inside '/usr/local/etc' with example configuration files. Still the installed ports themselves seem to only listen to stuff inside '/opt/local/etc'. For instance, I have an 'unbound' folder inside both. In the former, it contains 'unbound.config', while in the latter it contains 'root.key' and 'unsound.config-dist' (a file with contents identical to 'unbound.config'). That seems to happen to particular ports only, though. Anyone experiencing that? Are these folders really unnecessary? Thanks in advance, FY -------------- next part -------------- An HTML attachment was scrubbed... URL: From dluke at geeklair.net Sat Dec 11 05:23:20 2021 From: dluke at geeklair.net (Daniel J. Luke) Date: Sat, 11 Dec 2021 00:23:20 -0500 Subject: Can some ports install config files inside '/usr/local/etc'? In-Reply-To: References: Message-ID: <697FA684-AE7C-489C-A0A6-DF5468EFB643@geeklair.net> On Dec 11, 2021, at 12:11 AM, fgyamauti2 fgyamauti2 wrote: > Apparently some ports that I've installed are making directories inside '/usr/local/etc' with example configuration files. Still the installed ports themselves seem to only listen to stuff inside '/opt/local/etc'. They shouldn't be. > For instance, I have an 'unbound' folder inside both. In the former, it contains 'unbound.config', while in the latter it contains 'root.key' and 'unsound.config-dist' (a file with contents identical to 'unbound.config'). That seems to happen to particular ports only, though. Anyone experiencing that? Are these folders really unnecessary? On my system(s) the unbound port does not create anything in /usr/local/etc `port contents unbound` doesn't show any unusual files and I don't see any part of the portfile that would be doing that on your system. -- Daniel J. Luke From ralph at ml.seichter.de Sat Dec 11 05:43:17 2021 From: ralph at ml.seichter.de (Ralph Seichter) Date: Sat, 11 Dec 2021 06:43:17 +0100 Subject: Can some ports install config files inside '/usr/local/etc'? In-Reply-To: References: Message-ID: <87zgp766iy.fsf@ra.horus-it.com> * fgyamauti: > Apparently some ports that I've installed are making directories > inside '/usr/local/etc' with example configuration files. That seems unlikely. Have you perhaps installed both MacPorts and Homebrew on your Mac? AFAIK, Homebrew uses /usr/local/* to store its installation files. -Ralph From jonesc at hep.phy.cam.ac.uk Sat Dec 11 10:47:28 2021 From: jonesc at hep.phy.cam.ac.uk (Chris Jones) Date: Sat, 11 Dec 2021 10:47:28 +0000 Subject: Can some ports install config files inside '/usr/local/etc'? In-Reply-To: References: Message-ID: <85E910EA-8192-4F82-9160-67F91F8367CC@hep.phy.cam.ac.uk> Nothing in macports will be installing to /usr/local. If you have anything in that area it has been put there by some other means. Maybe homebrew?, but also a number of third party installers sometimes use this directory as well (which are the reasons why MacPorts specifically ignores this area). > On 11 Dec 2021, at 5:11 am, fgyamauti2 fgyamauti2 wrote: > > ? > Hi, > > Apparently some ports that I've installed are making directories inside '/usr/local/etc' with example configuration files. Still the installed ports themselves seem to only listen to stuff inside '/opt/local/etc'. > > For instance, I have an 'unbound' folder inside both. In the former, it contains 'unbound.config', while in the latter it contains 'root.key' and 'unsound.config-dist' (a file with contents identical to 'unbound.config'). That seems to happen to particular ports only, though. Anyone experiencing that? Are these folders really unnecessary? > > Thanks in advance, > FY > From ryandesign at macports.org Sat Dec 11 14:00:34 2021 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat, 11 Dec 2021 08:00:34 -0600 Subject: gtk3 problem In-Reply-To: <575A4954-7C02-4DA7-963A-D0A71C258CE3@contoso.com> References: <575A4954-7C02-4DA7-963A-D0A71C258CE3@contoso.com> Message-ID: On Dec 10, 2021, at 13:51, Langer, Stephen A. (Fed) wrote: > Is anyone running gtk3 programs on an M1 or on Monterey? The following simple script crashes on ?an M1 Mini with Monterey, when run with python 2.7: > > import gi > gi.require_version("Gtk", "3.0") > from gi.repository import Gtk > window = Gtk.Window(Gtk.WindowType.TOPLEVEL, title="test") > > The error message is "Trace/BPT trap: 5". > > The same program runs without error on an Intel CPU and Big Sur. Unfortunately I can't change the OS on either machine so I can't tell if the problem is due to the OS or the processor, or both. Probably the first diagnostic step should be to look into the crash report. If it doesn't help you figure out the problem, you could send it here; maybe someone here can decipher it. Look for the log in ~/Library/Logs/DiagnosticReports. From rlhamil at smart.net Sat Dec 11 17:24:51 2021 From: rlhamil at smart.net (Richard L. Hamilton) Date: Sat, 11 Dec 2021 12:24:51 -0500 Subject: Any ports use log4j 2? Message-ID: <631FEC42-D4B7-47F9-89E2-F4DB20E0B90A@smart.net> CVE-2021-44228 sounds kinda scary! -- eMail: mailto:rlhamil at smart.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From ryandesign at macports.org Sat Dec 11 18:34:43 2021 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat, 11 Dec 2021 12:34:43 -0600 Subject: Any ports use log4j 2? In-Reply-To: <631FEC42-D4B7-47F9-89E2-F4DB20E0B90A@smart.net> References: <631FEC42-D4B7-47F9-89E2-F4DB20E0B90A@smart.net> Message-ID: <00353945-2B8C-412F-87E1-5F2442D0F646@macports.org> On Dec 11, 2021, at 11:24, Richard L. Hamilton wrote: > CVE-2021-44228 sounds kinda scary! We appear to have a jakarta-log4j port but it is version 1.x, not 2. From perry at macports.org Sat Dec 11 19:27:20 2021 From: perry at macports.org (Perry Lee) Date: Sat, 11 Dec 2021 11:27:20 -0800 Subject: Any ports use log4j 2? In-Reply-To: <00353945-2B8C-412F-87E1-5F2442D0F646@macports.org> References: <631FEC42-D4B7-47F9-89E2-F4DB20E0B90A@smart.net> <00353945-2B8C-412F-87E1-5F2442D0F646@macports.org> Message-ID: On Sat, Dec 11, 2021, at 10:34 AM, Ryan Schmidt wrote: > On Dec 11, 2021, at 11:24, Richard L. Hamilton wrote: > >> CVE-2021-44228 sounds kinda scary! > > We appear to have a jakarta-log4j port but it is version 1.x, not 2. Log4j 1.x isn't affected by that CVE [1], though there is a vulnerability that depends on configuration, not user input [2]. [1] https://github.com/apache/logging-log4j2/pull/608#issuecomment-991387493 [2] https://github.com/apache/logging-log4j2/pull/608#issuecomment-991730650 From dave at horsfall.org Sat Dec 11 19:30:25 2021 From: dave at horsfall.org (Dave Horsfall) Date: Sun, 12 Dec 2021 06:30:25 +1100 (EST) Subject: Can some ports install config files inside '/usr/local/etc'? In-Reply-To: <85E910EA-8192-4F82-9160-67F91F8367CC@hep.phy.cam.ac.uk> References: <85E910EA-8192-4F82-9160-67F91F8367CC@hep.phy.cam.ac.uk> Message-ID: On Sat, 11 Dec 2021, Chris Jones wrote: > Nothing in macports will be installing to /usr/local. If you have > anything in that area it has been put there by some other means. Maybe > homebrew?, but also a number of third party installers sometimes use > this directory as well (which are the reasons why MacPorts specifically > ignores this area). The "/usr/local" tree is quite a common destination on other systems such as FreeBSD; I use it on the Mac to separate my own stuff from MacPorts' stuff as well. -- Dave From stephen.langer at nist.gov Sat Dec 11 21:15:07 2021 From: stephen.langer at nist.gov (Langer, Stephen A. (Fed)) Date: Sat, 11 Dec 2021 21:15:07 +0000 Subject: gtk3 problem In-Reply-To: References: <575A4954-7C02-4DA7-963A-D0A71C258CE3@contoso.com> Message-ID: <061B0F28-FFCB-417D-ACF4-694719921DFD@nist.gov> On 12/11/21, 9:00 AM, "Ryan Schmidt" wrote: On Dec 10, 2021, at 13:51, Langer, Stephen A. (Fed) wrote: > Is anyone running gtk3 programs on an M1 or on Monterey? The following simple script crashes on an M1 Mini with Monterey, when run with python 2.7: > > import gi > gi.require_version("Gtk", "3.0") > from gi.repository import Gtk > window = Gtk.Window(Gtk.WindowType.TOPLEVEL, title="test") > > The error message is "Trace/BPT trap: 5". > > The same program runs without error on an Intel CPU and Big Sur. Unfortunately I can't change the OS on either machine so I can't tell if the problem is due to the OS or the processor, or both. Probably the first diagnostic step should be to look into the crash report. If it doesn't help you figure out the problem, you could send it here; maybe someone here can decipher it. Look for the log in ~/Library/Logs/DiagnosticReports. I've attached the log file. It's not telling me anything useful, but I would be delighted to be educated. Thanks. -- Steve -------------- next part -------------- A non-text attachment was scrubbed... Name: Python-2021-12-11-160411.ips Type: application/octet-stream Size: 11824 bytes Desc: Python-2021-12-11-160411.ips URL: From fgyamauti2 at gmail.com Sun Dec 12 05:54:25 2021 From: fgyamauti2 at gmail.com (fgyamauti2 fgyamauti2) Date: Sun, 12 Dec 2021 02:54:25 -0300 Subject: Can some ports install config files inside '/usr/local/etc'? In-Reply-To: <85E910EA-8192-4F82-9160-67F91F8367CC@hep.phy.cam.ac.uk> References: <85E910EA-8192-4F82-9160-67F91F8367CC@hep.phy.cam.ac.uk> Message-ID: Thanks for the replies Nothing in macports will be installing to /usr/local. If you have anything > in that area it has been put there by some other means. Maybe homebrew?, > but also a number of third party installers sometimes use this directory as > well (which are the reasons why MacPorts specifically ignores this area). > As mentioned also by Chris in the above reply and Ralph in the previous one, I've had Homebrew installed only for a short amount of time. Still, however, unless I'm getting too old, I don't recall installing unbound through Homebrew (I used Homebrew for 2 days and uninstalled it in fear of screwing up something in TeXLive). So unless it's installed by default... Well, also I should mention that I've set unbound-control. The weird thing is that everything suspicious inside '/usr/local/etc' is a configuration file of stuff that is related to MacPorts. More precisely, I have suspicious folders named 'fonts' (from fontsconfig), 'gnutls', 'openldap', 'openssl at 1.1', 'pkcs11'. Now, when I search the name of each folder, there's always another folder with similar or equal name further inside '/opt/local/' (so something like 'opt/local/a/b/c/d/gnutls') and a folder related to macports is always on the path (for instance, 'macports' and 'rsync.macports.org'). Also, inside '/opt/local/lib' I have stuff from Python 3.9 and Python 3.10. But I've only installed these through MacPorts. That's weird. Well, I've installed pip through Python 3.10 and ensurepip. That still doesn't explain it, I suppose... -------------- next part -------------- An HTML attachment was scrubbed... URL: From gerben.wierda at rna.nl Sun Dec 12 23:18:56 2021 From: gerben.wierda at rna.nl (Gerben Wierda) Date: Mon, 13 Dec 2021 00:18:56 +0100 Subject: Use of java (specifically on older macOS) Message-ID: <8070C065-D372-4451-9B4F-48F39D6BFDDD@rna.nl> While looking at my systems because of the log4j security issues I noticed the following: I am running solr8 as part of my MacPorts mail server setup and it shows up like this: $ ps laxww|grep java 504 50615 50613 0 20 0 7594340 1316684 - S ?? 97:31.56 /usr/bin/java -server -Xms1g -Xmx1g -XX:+UseG1GC -XX:+PerfDisableSharedMem -XX:+ParallelRefProcEnabled -XX:MaxGCPauseMillis=250 -XX:+UseLargePages -XX:+AlwaysPreTouch -XX:+ExplicitGCInvokesConcurrent -Xlog:gc*:file=/opt/local/var/solr/logs/solr_gc.log:time,uptime:filecount=9,filesize=20M -Dsolr.jetty.inetaccess.includes= -Dsolr.jetty.inetaccess.excludes= -Dsolr.log.dir=/opt/local/var/solr/logs -Djetty.port=8983 -DSTOP.PORT=7983 -DSTOP.KEY=solrrocks -Duser.timezone=UTC -XX:-OmitStackTraceInFastThrow -XX:OnOutOfMemoryError=/opt/local/share/java/solr-8.9.0/bin/oom_solr.sh 8983 /opt/local/var/solr/logs -Djetty.home=/opt/local/share/java/solr-8.9.0/server -Dsolr.solr.home=/opt/local/var/solr -Dsolr.data.home=/opt/local/var/db/solr -Dsolr.install.dir=/opt/local/share/java/solr-8.9.0 -Dsolr.default.confdir=/opt/local/share/java/solr-8.9.0/server/solr/configsets/_default/conf -Xss256k -jar start.jar --module=http Which means that MacPorts solr8 runs using macOS native java and not one from MacPorts itself. I thought the MacPorts stuff was supposed to be fully independent (except for Xcode). $ java -version java version "12.0.2" 2019-07-16 Java(TM) SE Runtime Environment (build 12.0.2+10) Java HotSpot(TM) 64-Bit Server VM (build 12.0.2+10, mixed mode, sharing) $ ls -l /usr/bin/java lrwxr-xr-x 1 root wheel 74 Aug 10 2019 /usr/bin/java -> /System/Library/Frameworks/JavaVM.framework/Versions/Current/Commands/java $ ls -l /System/Library/Frameworks/JavaVM.framework/Versions/Current/Commands/java -rwxr-xr-x 1 root wheel 58336 Jul 11 07:48 /System/Library/Frameworks/JavaVM.framework/Versions/Current/Commands/java That java is starting to get old, the last update was the last Security Update from macOS Mojave I also have Oracle Java SE 8 installed: $ /Library/Internet\ Plug-Ins/JavaAppletPlugin.plugin/Contents/Home/bin/java -version java version "1.8.0_311" Java(TM) SE Runtime Environment (build 1.8.0_311-b11) Java HotSpot(TM) 64-Bit Server VM (build 25.311-b11, mixed mode) Basically, I am rather confused about java numbering. I know I have the latest Oracle Java install and that my macOS Mojave version had its last update in the summer of 2021. I am also somewhat confused about MacPorts using the standard macOS Java which has a higher number but is an older version. Can somebody enlighten me? And shouldn?t ports that use java not depend on a java that comes with (old, outdated) java?s in macOS? But install and use an open source version instead? Or use the one from Oracle if available? Gerben Wierda (LinkedIn ) R&A IT Strategy (main site) Book: Chess and the Art of Enterprise?Architecture Book: Mastering ArchiMate -------------- next part -------------- An HTML attachment was scrubbed... URL: From chrischavez at gmx.us Mon Dec 13 01:10:23 2021 From: chrischavez at gmx.us (Christopher Chavez) Date: Mon, 13 Dec 2021 02:10:23 +0100 Subject: Use of java (specifically on older macOS) In-Reply-To: <8070C065-D372-4451-9B4F-48F39D6BFDDD@rna.nl> References: <8070C065-D372-4451-9B4F-48F39D6BFDDD@rna.nl> Message-ID: Sent:?Monday, December 13, 2021 at 12:18 AM From:?"Gerben Wierda" > Which means that MacPorts solr8 runs using macOS native java and not one from MacPorts itself. I thought the MacPorts stuff was supposed to be fully independent (except for Xcode). The JDK ports are an exception in that they install to the usual system-wide location of /Library/Java/JavaVirtualMachines rather than in the MacPorts prefix. Presumably this is an unavoidable requirement for them to be usable system-wide on macOS. > $ java -version > java version "12.0.2" 2019-07-16 > Java(TM) SE Runtime Environment (build 12.0.2+10) > Java HotSpot(TM) 64-Bit Server VM (build 12.0.2+10, mixed mode, sharing) > ? > $ ls -l /usr/bin/java > lrwxr-xr-x? 1 root? wheel? 74 Aug 10? 2019 /usr/bin/java -> /System/Library/Frameworks/JavaVM.framework/Versions/Current/Commands/java > > $ ls -l /System/Library/Frameworks/JavaVM.framework/Versions/Current/Commands/java > -rwxr-xr-x? 1 root? wheel? 58336 Jul 11 07:48 /System/Library/Frameworks/JavaVM.framework/Versions/Current/Commands/java > > That java is starting to get old, the last update was the last Security Update from macOS Mojave Your Java 12 installation comes from somewhere else. Apple has not shipped Java with/for macOS for a long time. The java, javac, etc. commands present in system paths are merely wrappers which require a separately-installed Java runtime to do anything useful. > I also have Oracle Java SE 8 installed: > > $ /Library/Internet\ Plug-Ins/JavaAppletPlugin.plugin/Contents/Home/bin/java -version > java version "1.8.0_311" > Java(TM) SE Runtime Environment (build 1.8.0_311-b11) > Java HotSpot(TM) 64-Bit Server VM (build 25.311-b11, mixed mode) > > Basically, I am rather confused about java numbering. I know I have the latest Oracle Java install and that my macOS Mojave version had its last update in the summer of 2021. I am also somewhat confused about MacPorts using the standard macOS Java which has a higher number but is an older version. > > Can somebody enlighten me? macOS will reportedly pick the installation with the latest Java version, unless a specific Java version/installation is requested e.g. by the JAVA_HOME environment variable. > And shouldn?t ports that use java not depend on a java that comes with (old, outdated) java?s in macOS? But install and use an open source version instead? Or use the one from Oracle if available? Because JDK is not a lightweight dependency, it seems somewhat desirable for ports to be flexible when specifying a Java requirement, and allow using an already-installed JDK/JRE if compatible (including one not provided by MacPorts). The Java PortGroup allows specifying a required Java version (either a minimum version or an exact version), and a fallback JDK port to install if a compatible version isn?t already present (hopefully an LTS version: e.g. 8, 11, or 17 from OpenJDK; other vendors may have LTS for other versions). Christopher A. Chavez From ryandesign at macports.org Mon Dec 13 01:36:59 2021 From: ryandesign at macports.org (Ryan Schmidt) Date: Sun, 12 Dec 2021 19:36:59 -0600 Subject: Can some ports install config files inside '/usr/local/etc'? In-Reply-To: References: <85E910EA-8192-4F82-9160-67F91F8367CC@hep.phy.cam.ac.uk> Message-ID: On Dec 11, 2021, at 23:54, fgyamauti2 fgyamauti2 wrote: > The weird thing is that everything suspicious inside '/usr/local/etc' is a configuration file of stuff that is related to MacPorts. More precisely, I have suspicious folders named 'fonts' (from fontsconfig), 'gnutls', 'openldap', 'openssl at 1.1', 'pkcs11'. Now, when I search the name of each folder, there's always another folder with similar or equal name further inside '/opt/local/' (so something like 'opt/local/a/b/c/d/gnutls') MacPorts keeps the Portfiles of all (tens of thousands of) existing ports on your system in /opt/local/var/macports/sources. This collection is called the "ports tree". When you ask MacPorts to install something, it does so by following the recipe in the corresponding Portfile. Those Portfiles are what get updated when you run "sudo port sync" or "sudo port selfupdate". So it's not surprising at all that when you search your drive for a common software program name, you find a directory with that name within MacPorts. MacPorts hasn't ever installed any directory called "openssl at 1.1" as far as I know, but Homebrew does. MacPorts does use the convention "portname @version_revision+variants" when referring to ports, but that notation does not appear in directory names. From ryandesign at macports.org Mon Dec 13 01:42:16 2021 From: ryandesign at macports.org (Ryan Schmidt) Date: Sun, 12 Dec 2021 19:42:16 -0600 Subject: Use of java (specifically on older macOS) In-Reply-To: References: <8070C065-D372-4451-9B4F-48F39D6BFDDD@rna.nl> Message-ID: <85250320-38DC-4C10-9188-9861B4AEB9EF@macports.org> On Dec 12, 2021, at 19:10, Christopher Chavez wrote: >> And shouldn?t ports that use java not depend on a java that comes with (old, outdated) java?s in macOS? But install and use an open source version instead? Or use the one from Oracle if available? > > Because JDK is not a lightweight dependency, it seems somewhat desirable for ports to be flexible when specifying a Java requirement, and allow using an already-installed JDK/JRE if compatible (including one not provided by MacPorts). The Java PortGroup allows specifying a required Java version (either a minimum version or an exact version), and a fallback JDK port to install if a compatible version isn?t already present (hopefully an LTS version: e.g. 8, 11, or 17 from OpenJDK; other vendors may have LTS for other versions). The java portgroup and the ability to install java by using MacPorts are relatively new capabilities. Not that long ago, everything in MacPorts that required java required the user to have installed it manually first. This made sense back when java was provided with the OS, but as you say that hasn't been the case for over a decade. Probably not all java-using ports have yet been updated to use the java portgroup, with I'm not sure what consequences. From steve.t.smith at gmail.com Mon Dec 13 03:02:53 2021 From: steve.t.smith at gmail.com (Steven Smith) Date: Sun, 12 Dec 2021 22:02:53 -0500 Subject: Use of java (specifically on older macOS) In-Reply-To: <8070C065-D372-4451-9B4F-48F39D6BFDDD@rna.nl> References: <8070C065-D372-4451-9B4F-48F39D6BFDDD@rna.nl> Message-ID: Java figures out which version to use from JAVA_HOME or /Library/Java/JavaVirtualMachines. Are you sure that?s not a MacPorts version? My native macOS java binary runs the last LTS jdk from MacPorts: > sudo -u solr /usr/bin/java -version > openjdk version "11.0.13" 2021-10-19 > OpenJDK Runtime Environment Temurin-11.0.13+8 (build 11.0.13+8) > OpenJDK 64-Bit Server VM Temurin-11.0.13+8 (build 11.0.13+8, mixed mode) This is a simple path issue because `java` Is found in /usr/bin. If you want to use a MacPorts-installed binary, set up your paths appropriately. I?m not aware of any practical difference this would make. > port provides /Library/Java/JavaVirtualMachines/openjdk11-temurin/Contents/Home/bin/java > /Library/Java/JavaVirtualMachines/openjdk11-temurin/Contents/Home/bin/java is provided by: openjdk11-temurin > On Dec 12, 2021, at 18:19, Gerben Wierda via macports-users wrote: > > Which means that MacPorts solr8 runs using macOS native java and not one from MacPorts itself. I thought the MacPorts stuff was supposed to be fully independent (except for Xcode). From rlhamil at smart.net Mon Dec 13 03:12:26 2021 From: rlhamil at smart.net (Richard L. Hamilton) Date: Sun, 12 Dec 2021 22:12:26 -0500 Subject: Use of java (specifically on older macOS) In-Reply-To: References: <8070C065-D372-4451-9B4F-48F39D6BFDDD@rna.nl> Message-ID: BTW, in Xcode.app bundle (12.4), /Applications/Xcode.app/Contents/SharedFrameworks/ContentDeliveryServices.framework/Versions/A/itms/share/OSGi-Bundles/org.apache.logging.log4j.core-2.11.2.jar I imagine that will be getting updated not long after they realize it's there. > On Dec 12, 2021, at 22:02, Steven Smith wrote: > > Java figures out which version to use from JAVA_HOME or /Library/Java/JavaVirtualMachines. Are you sure that?s not a MacPorts version? > > My native macOS java binary runs the last LTS jdk from MacPorts: > >> sudo -u solr /usr/bin/java -version >> openjdk version "11.0.13" 2021-10-19 >> OpenJDK Runtime Environment Temurin-11.0.13+8 (build 11.0.13+8) >> OpenJDK 64-Bit Server VM Temurin-11.0.13+8 (build 11.0.13+8, mixed mode) > > > This is a simple path issue because `java` Is found in /usr/bin. If you want to use a MacPorts-installed binary, set up your paths appropriately. I?m not aware of any practical difference this would make. > >> port provides /Library/Java/JavaVirtualMachines/openjdk11-temurin/Contents/Home/bin/java >> /Library/Java/JavaVirtualMachines/openjdk11-temurin/Contents/Home/bin/java is provided by: openjdk11-temurin > > > >> On Dec 12, 2021, at 18:19, Gerben Wierda via macports-users wrote: >> >> Which means that MacPorts solr8 runs using macOS native java and not one from MacPorts itself. I thought the MacPorts stuff was supposed to be fully independent (except for Xcode). > -- eMail: mailto:rlhamil at smart.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From ryandesign at macports.org Mon Dec 13 18:08:36 2021 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon, 13 Dec 2021 12:08:36 -0600 Subject: gtk3 problem In-Reply-To: <061B0F28-FFCB-417D-ACF4-694719921DFD@nist.gov> References: <575A4954-7C02-4DA7-963A-D0A71C258CE3@contoso.com> <061B0F28-FFCB-417D-ACF4-694719921DFD@nist.gov> Message-ID: <5CCD008F-63BE-4FC0-84A2-C973677272A4@macports.org> On Dec 11, 2021, at 15:15, Langer, Stephen A. (Fed) wrote: > > On 12/11/21, 9:00 AM, Ryan Schmidt wrote: > >> On Dec 10, 2021, at 13:51, Langer, Stephen A. (Fed) wrote: >> >>> Is anyone running gtk3 programs on an M1 or on Monterey? The following simple script crashes on an M1 Mini with Monterey, when run with python 2.7: >>> >>> import gi >>> gi.require_version("Gtk", "3.0") >>> from gi.repository import Gtk >>> window = Gtk.Window(Gtk.WindowType.TOPLEVEL, title="test") >>> >>> The error message is "Trace/BPT trap: 5". >>> >>> The same program runs without error on an Intel CPU and Big Sur. Unfortunately I can't change the OS on either machine so I can't tell if the problem is due to the OS or the processor, or both. >> >> Probably the first diagnostic step should be to look into the crash report. If it doesn't help you figure out the problem, you could send it here; maybe someone here can decipher it. Look for the log in ~/Library/Logs/DiagnosticReports. > > I've attached the log file. It's not telling me anything useful, but I would be delighted to be educated. It says a buffer overflow was detected and it gives the stack trace showing what functions were called that led to the problem. I'm not an expert in python or gtk internals but maybe if you report it to the gtk developers they will know how to fix it. From rlhamil at smart.net Tue Dec 14 03:11:56 2021 From: rlhamil at smart.net (Richard L. Hamilton) Date: Mon, 13 Dec 2021 22:11:56 -0500 Subject: pwait? Message-ID: macOS does not have the "pwait" command that Linux and some other Unix versions have, which allows waiting on any process (not just a child), given the PID. There would definitely be uses for that, like dealing with a process that backgrounds itself when you wish it didn't, provided you have some way (if it writes a PID file, or if there would only be one instance, using pgrep) to get the PID of the backgrounded process. Turns out FreeBSD has an implementation that uses the kqueue mechanism, which macOS has. https://github.com/freebsd/freebsd-src/tree/master/bin/pwait The Makefile there is useless unless building as part of FreeBSD, but one can just cc pwait.c -o pwait and it will compile and work just fine. There's also a man page in the previously mentioned location. Wishing for a port...bit ugly when you can't use the supplied Makefile. Sadly, not volunteering myself. :-/ Given a trick in altering the URL a bit (replace tree/master with trunk), one can fetch just that directory rather than the whole FreeBSD tree: svn co https://github.com/freebsd/freebsd-src/trunk/bin/pwait -------------- next part -------------- An HTML attachment was scrubbed... URL: From gerben.wierda at rna.nl Tue Dec 14 14:36:21 2021 From: gerben.wierda at rna.nl (Gerben Wierda) Date: Tue, 14 Dec 2021 15:36:21 +0100 Subject: Any ports use log4j 2? In-Reply-To: <631FEC42-D4B7-47F9-89E2-F4DB20E0B90A@smart.net> References: <631FEC42-D4B7-47F9-89E2-F4DB20E0B90A@smart.net> Message-ID: It is super scary. Apache solr8 is vulnerable. There is no 0.8.11 yet. Mitigation required: ? (Linux/MacOS) Edit your solr.in.sh file to include: SOLR_OPTS="$SOLR_OPTS -Dlog4j2.formatMsgNoLookups=true" Gerben Wierda (LinkedIn ) R&A IT Strategy (main site) Book: Chess and the Art of Enterprise?Architecture Book: Mastering ArchiMate > On 11 Dec 2021, at 18:24, Richard L. Hamilton wrote: > > CVE-2021-44228 sounds kinda scary! > > -- > eMail: mailto:rlhamil at smart.net > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From gerben.wierda at rna.nl Tue Dec 14 14:49:02 2021 From: gerben.wierda at rna.nl (Gerben Wierda) Date: Tue, 14 Dec 2021 15:49:02 +0100 Subject: Any ports use log4j 2? In-Reply-To: References: <631FEC42-D4B7-47F9-89E2-F4DB20E0B90A@smart.net> Message-ID: I see in GitHub that the mitigation for apache-solr8 has already been added (together with the 0.8.11 update). Great work! Gerben Wierda (LinkedIn ) R&A IT Strategy (main site) Book: Chess and the Art of Enterprise?Architecture Book: Mastering ArchiMate > On 14 Dec 2021, at 15:36, Gerben Wierda via macports-users wrote: > > It is super scary. > > Apache solr8 is vulnerable. There is no 0.8.11 yet. Mitigation required: > > ? (Linux/MacOS) Edit your solr.in.sh file to include: SOLR_OPTS="$SOLR_OPTS -Dlog4j2.formatMsgNoLookups=true" > > > Gerben Wierda (LinkedIn ) > R&A IT Strategy (main site) > Book: Chess and the Art of Enterprise?Architecture > Book: Mastering ArchiMate > >> On 11 Dec 2021, at 18:24, Richard L. Hamilton > wrote: >> >> CVE-2021-44228 sounds kinda scary! >> >> -- >> eMail: mailto:rlhamil at smart.net >> >> >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From steve.t.smith at gmail.com Tue Dec 14 22:44:30 2021 From: steve.t.smith at gmail.com (Steven Smith) Date: Tue, 14 Dec 2021 17:44:30 -0500 Subject: Use of java (specifically on older macOS) In-Reply-To: <8070C065-D372-4451-9B4F-48F39D6BFDDD@rna.nl> References: <8070C065-D372-4451-9B4F-48F39D6BFDDD@rna.nl> Message-ID: <389C5211-60DD-48A6-93C2-1C308631A679@gmail.com> Please see https://github.com/macports/macports-ports/pull/13353 , which sets SOLR_JAVA_HOME to accomplish this. > On Dec 12, 2021, at 6:18 PM, Gerben Wierda via macports-users wrote: > > Which means that MacPorts solr8 runs using macOS native java and not one from MacPorts itself. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3898 bytes Desc: not available URL: From stephen.langer at nist.gov Wed Dec 15 00:04:00 2021 From: stephen.langer at nist.gov (Langer, Stephen A. (Fed)) Date: Wed, 15 Dec 2021 00:04:00 +0000 Subject: gtk3 problem In-Reply-To: <5CCD008F-63BE-4FC0-84A2-C973677272A4@macports.org> References: <575A4954-7C02-4DA7-963A-D0A71C258CE3@contoso.com> <061B0F28-FFCB-417D-ACF4-694719921DFD@nist.gov> <5CCD008F-63BE-4FC0-84A2-C973677272A4@macports.org> Message-ID: <6A651912-2223-4137-9F81-C038324CEF60@nist.gov> ?On 12/13/21, 1:08 PM, "Ryan Schmidt" wrote: On Dec 11, 2021, at 15:15, Langer, Stephen A. (Fed) wrote: > > On 12/11/21, 9:00 AM, Ryan Schmidt wrote: > >> On Dec 10, 2021, at 13:51, Langer, Stephen A. (Fed) wrote: >> >>> Is anyone running gtk3 programs on an M1 or on Monterey? The following simple script crashes on an M1 Mini with Monterey, when run with python 2.7: >>> >>> import gi >>> gi.require_version("Gtk", "3.0") >>> from gi.repository import Gtk >>> window = Gtk.Window(Gtk.WindowType.TOPLEVEL, title="test") >>> >>> The error message is "Trace/BPT trap: 5". >>> >>> The same program runs without error on an Intel CPU and Big Sur. Unfortunately I can't change the OS on either machine so I can't tell if the problem is due to the OS or the processor, or both. >> >> Probably the first diagnostic step should be to look into the crash report. If it doesn't help you figure out the problem, you could send it here; maybe someone here can decipher it. Look for the log in ~/Library/Logs/DiagnosticReports. > > I've attached the log file. It's not telling me anything useful, but I would be delighted to be educated. It says a buffer overflow was detected and it gives the stack trace showing what functions were called that led to the problem. I'm not an expert in python or gtk internals but maybe if you report it to the gtk developers they will know how to fix it. Ok, I'll try my luck with them. I thought that that particular combination of os, cpu, and ports would be common here, and someone could tell me if it works for them, so I'd know if there is something wrong with my setup. -- Steve From ryandesign at macports.org Wed Dec 15 01:12:28 2021 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue, 14 Dec 2021 19:12:28 -0600 Subject: pwait? In-Reply-To: References: Message-ID: <20309226-2CF1-4031-9421-84B41F6C24BD@macports.org> On Dec 13, 2021, at 21:11, Richard L. Hamilton wrote: > macOS does not have the "pwait" command that Linux and some other Unix versions have, which allows waiting on any process (not just a child), given the PID. There would definitely be uses for that, like dealing with a process that backgrounds itself when you wish it didn't, provided you have some way (if it writes a PID file, or if there would only be one instance, using pgrep) to get the PID of the backgrounded process. > > Turns out FreeBSD has an implementation that uses the kqueue mechanism, which macOS has. > > https://github.com/freebsd/freebsd-src/tree/master/bin/pwait > > The Makefile there is useless unless building as part of FreeBSD, but one can just > > cc pwait.c -o pwait > > and it will compile and work just fine. There's also a man page in the previously mentioned location. > > Wishing for a port...bit ugly when you can't use the supplied Makefile. Sadly, not volunteering myself. :-/ Added! Thanks for the suggestion. https://ports.macports.org/port/pwait From vaccari at units.it Wed Dec 15 11:37:35 2021 From: vaccari at units.it (VACCARI FRANCO) Date: Wed, 15 Dec 2021 11:37:35 +0000 Subject: ImageMagick failure to install Message-ID: <224170C6-70C7-4661-B124-850E28BD6219@ds.units.it> I?m configuring a new Mac Mini M1 running Mac OS 12.1 and Xcode 13.2, and installing the usual packages I need. When dealing with ImageMagick I get the following error: mm02:~ sudo port install imagemagick ---> Computing dependencies for ImageMagick Error: Can't install libgcc-devel because conflicting ports are active: libgcc Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug. Error: Processing of port imagemagick failed mm02:~ I believe that deactivating libgcc would break packages already installed that depend on it. Is it so, or can I deactivate libgcc and later activate it again? Thanks Franco From jonesc at hep.phy.cam.ac.uk Wed Dec 15 11:51:05 2021 From: jonesc at hep.phy.cam.ac.uk (Christopher Jones) Date: Wed, 15 Dec 2021 11:51:05 +0000 Subject: ImageMagick failure to install In-Reply-To: <224170C6-70C7-4661-B124-850E28BD6219@ds.units.it> References: <224170C6-70C7-4661-B124-850E28BD6219@ds.units.it> Message-ID: <8CDA8EE0-6778-4863-ADC9-47EC119E4886@hep.phy.cam.ac.uk> Hi, gcc-devel is the (current) preferred gcc compiler on Apple silicon at the moment, as none of the released gcc versions are fully stable on this platform. gcc-devel requires libgcc-devel as its runtime. libgcc and libgcc-devel are interchangeable, so you should remove libgcc and allow libgcc-devel to be installed instead. Chris > On 15 Dec 2021, at 11:37 am, VACCARI FRANCO wrote: > > I?m configuring a new Mac Mini M1 running Mac OS 12.1 and Xcode 13.2, and installing the usual packages I need. When dealing with ImageMagick I get the following error: > > mm02:~ sudo port install imagemagick > ---> Computing dependencies for ImageMagick > Error: Can't install libgcc-devel because conflicting ports are active: libgcc > Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug. > Error: Processing of port imagemagick failed > mm02:~ > > I believe that deactivating libgcc would break packages already installed that depend on it. Is it so, or can I deactivate libgcc and later activate it again? > > Thanks > > Franco > > -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 1930 bytes Desc: not available URL: From vaccari at units.it Wed Dec 15 11:55:43 2021 From: vaccari at units.it (VACCARI FRANCO) Date: Wed, 15 Dec 2021 11:55:43 +0000 Subject: ImageMagick failure to install In-Reply-To: <8CDA8EE0-6778-4863-ADC9-47EC119E4886@hep.phy.cam.ac.uk> References: <224170C6-70C7-4661-B124-850E28BD6219@ds.units.it> <8CDA8EE0-6778-4863-ADC9-47EC119E4886@hep.phy.cam.ac.uk> Message-ID: Ok, I?ll delete all what I installed up to now and restart from scratch. My concern is that some packages will force the install of libgcc and some others will require libgcc-devel. Will see and report the outcome... Thanks Franco > On 15 Dec 2021, at 12:51, Christopher Jones wrote: > > Hi, > > gcc-devel is the (current) preferred gcc compiler on Apple silicon at the moment, as none of the released gcc versions are fully stable on this platform. gcc-devel requires libgcc-devel as its runtime. libgcc and libgcc-devel are interchangeable, so you should remove libgcc and allow libgcc-devel to be installed instead. > > Chris > >> On 15 Dec 2021, at 11:37 am, VACCARI FRANCO wrote: >> >> I?m configuring a new Mac Mini M1 running Mac OS 12.1 and Xcode 13.2, and installing the usual packages I need. When dealing with ImageMagick I get the following error: >> >> mm02:~ sudo port install imagemagick >> ---> Computing dependencies for ImageMagick >> Error: Can't install libgcc-devel because conflicting ports are active: libgcc >> Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug. >> Error: Processing of port imagemagick failed >> mm02:~ >> >> I believe that deactivating libgcc would break packages already installed that depend on it. Is it so, or can I deactivate libgcc and later activate it again? >> >> Thanks >> >> Franco >> >> > From jonesc at hep.phy.cam.ac.uk Wed Dec 15 11:56:16 2021 From: jonesc at hep.phy.cam.ac.uk (Christopher Jones) Date: Wed, 15 Dec 2021 11:56:16 +0000 Subject: ImageMagick failure to install In-Reply-To: References: <224170C6-70C7-4661-B124-850E28BD6219@ds.units.it> <8CDA8EE0-6778-4863-ADC9-47EC119E4886@hep.phy.cam.ac.uk> Message-ID: Please remember to reply to list... No. do not do that. sudo port -f uninstall libgcc sudo port install libgcc-devel > On 15 Dec 2021, at 11:54 am, VACCARI FRANCO wrote: > > Ok, I?ll delete all what I installed up to now and restart from scratch. My concern is that some packages will force the install of libgcc and some others will require libgcc-devel. Will see and report the outcome... > > Thanks > > Franco > > >> On 15 Dec 2021, at 12:51, Christopher Jones wrote: >> >> Hi, >> >> gcc-devel is the (current) preferred gcc compiler on Apple silicon at the moment, as none of the released gcc versions are fully stable on this platform. gcc-devel requires libgcc-devel as its runtime. libgcc and libgcc-devel are interchangeable, so you should remove libgcc and allow libgcc-devel to be installed instead. >> >> Chris >> >>> On 15 Dec 2021, at 11:37 am, VACCARI FRANCO wrote: >>> >>> I?m configuring a new Mac Mini M1 running Mac OS 12.1 and Xcode 13.2, and installing the usual packages I need. When dealing with ImageMagick I get the following error: >>> >>> mm02:~ sudo port install imagemagick >>> ---> Computing dependencies for ImageMagick >>> Error: Can't install libgcc-devel because conflicting ports are active: libgcc >>> Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug. >>> Error: Processing of port imagemagick failed >>> mm02:~ >>> >>> I believe that deactivating libgcc would break packages already installed that depend on it. Is it so, or can I deactivate libgcc and later activate it again? >>> >>> Thanks >>> >>> Franco >>> >>> >> > -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 1930 bytes Desc: not available URL: From vaccari at units.it Wed Dec 15 13:56:37 2021 From: vaccari at units.it (VACCARI FRANCO) Date: Wed, 15 Dec 2021 13:56:37 +0000 Subject: ImageMagick failure to install In-Reply-To: References: <224170C6-70C7-4661-B124-850E28BD6219@ds.units.it> <8CDA8EE0-6778-4863-ADC9-47EC119E4886@hep.phy.cam.ac.uk> Message-ID: <3526B0A7-A388-4A6C-B609-98C112FEE207@ds.units.it> So I did that, but a lot of messages care coming?s out, mm02:~ sudo port -f uninstall libgcc Password: ---> Unable to uninstall libgcc @5.0_0, the following ports depend on it: ---> gcc11 @11.2.0_0 Warning: Uninstall forced. Proceeding despite dependencies. ---> Deactivating libgcc @5.0_0 ---> Cleaning libgcc ---> Uninstalling libgcc @5.0_0 ---> Cleaning libgcc mm02:~ sudo port install libgcc-devel ---> Computing dependencies for libgcc-devel ---> Fetching archive for libgcc-devel ---> Attempting to fetch libgcc-devel-12-20211209_0.darwin_21.arm64.tbz2 from https://packages.macports.org/libgcc-devel ---> Attempting to fetch libgcc-devel-12-20211209_0.darwin_21.arm64.tbz2.rmd160 from https://packages.macports.org/libgcc-devel ---> Installing libgcc-devel @12-20211209_0 ---> Activating libgcc-devel @12-20211209_0 Error: Failed to activate libgcc-devel: Image error: /opt/local/include/gcc/c++/algorithm is being used by the active libgcc11 port. Please deactivate this port first, or use 'port -f activate libgcc-devel' to force the activation. Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc-devel/libgcc-devel/main.log for details. Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug. Error: Processing of port libgcc-devel failed mm02:~ sudo port -f activate libgcc-devel ---> Computing dependencies for libgcc-devel ---> Activating libgcc-devel @12-20211209_0 Warning: File /opt/local/include/gcc/c++/algorithm already exists. Moving to: /opt/local/include/gcc/c++/algorithm.mp_1639575707. Warning: File /opt/local/include/gcc/c++/any already exists. Moving to: /opt/local/include/gcc/c++/any.mp_1639575707. Warning: File /opt/local/include/gcc/c++/array already exists. Moving to: /opt/local/include/gcc/c++/array.mp_1639575707. Warning: File /opt/local/include/gcc/c++/atomic already exists. Moving to: /opt/local/include/gcc/c++/atomic.mp_1639575707. Warning: File /opt/local/include/gcc/c++/backward/auto_ptr.h already exists. Moving to: /opt/local/include/gcc/c++/backward/auto_ptr.h.mp_1639575707. Warning: File /opt/local/include/gcc/c++/backward/backward_warning.h already exists. Moving to: /opt/local/include/gcc/c++/backward/backward_warning.h.mp_1639575707. Warning: File /opt/local/include/gcc/c++/backward/binders.h already exists. Moving to: /opt/local/include/gcc/c++/backward/binders.h.mp_1639575707. Warning: File /opt/local/include/gcc/c++/backward/hash_fun.h already exists. Moving to: /opt/local/include/gcc/c++/backward/hash_fun.h.mp_1639575707. Warning: File /opt/local/include/gcc/c++/backward/hash_map already exists. Moving to: /opt/local/include/gcc/c++/backward/hash_map.mp_1639575707. Warning: File /opt/local/include/gcc/c++/backward/hash_set already exists. Moving to: /opt/local/include/gcc/c++/backward/hash_set.mp_1639575707. ? ? ? tons of similar messages ? ? Warning: File /opt/local/lib/libgcc/libatomic.1.dylib already exists. Moving to: /opt/local/lib/libgcc/libatomic.1.dylib.mp_1639575707. Warning: File /opt/local/lib/libgcc/libgcc_s.1.1.dylib already exists. Moving to: /opt/local/lib/libgcc/libgcc_s.1.1.dylib.mp_1639575707. Warning: File /opt/local/lib/libgcc/libgfortran.5.dylib already exists. Moving to: /opt/local/lib/libgcc/libgfortran.5.dylib.mp_1639575707. Warning: File /opt/local/lib/libgcc/libgomp.1.dylib already exists. Moving to: /opt/local/lib/libgcc/libgomp.1.dylib.mp_1639575707. Warning: File /opt/local/lib/libgcc/libitm.1.dylib already exists. Moving to: /opt/local/lib/libgcc/libitm.1.dylib.mp_1639575707. Warning: File /opt/local/lib/libgcc/libobjc-gnu.4.dylib already exists. Moving to: /opt/local/lib/libgcc/libobjc-gnu.4.dylib.mp_1639575707. Warning: File /opt/local/lib/libgcc/libssp.0.dylib already exists. Moving to: /opt/local/lib/libgcc/libssp.0.dylib.mp_1639575707. Warning: File /opt/local/lib/libgcc/libstdc++.6.dylib already exists. Moving to: /opt/local/lib/libgcc/libstdc++.6.dylib.mp_1639575707. Warning: File /opt/local/lib/libstdc++.6.dylib already exists. Moving to: /opt/local/lib/libstdc++.6.dylib.mp_1639575707. ---> Cleaning libgcc-devel ? miniadmin at mm02:~ After that I could install ImageMagick. So, should I happily disregard those warming messages? And, as I had previously installed gcc11, should I uninstall it and rather install gcc-devel? I?m afraid of mixing things up? Franco > On 15 Dec 2021, at 12:56, Christopher Jones wrote: > > > Please remember to reply to list... > > No. do not do that. > > sudo port -f uninstall libgcc > sudo port install libgcc-devel > > >> On 15 Dec 2021, at 11:54 am, VACCARI FRANCO wrote: >> >> Ok, I?ll delete all what I installed up to now and restart from scratch. My concern is that some packages will force the install of libgcc and some others will require libgcc-devel. Will see and report the outcome... >> >> Thanks >> >> Franco >> >> >>> On 15 Dec 2021, at 12:51, Christopher Jones wrote: >>> >>> Hi, >>> >>> gcc-devel is the (current) preferred gcc compiler on Apple silicon at the moment, as none of the released gcc versions are fully stable on this platform. gcc-devel requires libgcc-devel as its runtime. libgcc and libgcc-devel are interchangeable, so you should remove libgcc and allow libgcc-devel to be installed instead. >>> >>> Chris >>> >>>> On 15 Dec 2021, at 11:37 am, VACCARI FRANCO wrote: >>>> >>>> I?m configuring a new Mac Mini M1 running Mac OS 12.1 and Xcode 13.2, and installing the usual packages I need. When dealing with ImageMagick I get the following error: >>>> >>>> mm02:~ sudo port install imagemagick >>>> ---> Computing dependencies for ImageMagick >>>> Error: Can't install libgcc-devel because conflicting ports are active: libgcc >>>> Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug. >>>> Error: Processing of port imagemagick failed >>>> mm02:~ >>>> >>>> I believe that deactivating libgcc would break packages already installed that depend on it. Is it so, or can I deactivate libgcc and later activate it again? >>>> >>>> Thanks >>>> >>>> Franco >>>> >>>> >>> >> > From jonesc at hep.phy.cam.ac.uk Wed Dec 15 13:59:44 2021 From: jonesc at hep.phy.cam.ac.uk (Christopher Jones) Date: Wed, 15 Dec 2021 13:59:44 +0000 Subject: ImageMagick failure to install In-Reply-To: <3526B0A7-A388-4A6C-B609-98C112FEE207@ds.units.it> References: <224170C6-70C7-4661-B124-850E28BD6219@ds.units.it> <8CDA8EE0-6778-4863-ADC9-47EC119E4886@hep.phy.cam.ac.uk> <3526B0A7-A388-4A6C-B609-98C112FEE207@ds.units.it> Message-ID: <74ADC0F3-E21B-4064-84D2-2AB3981ECB1C@hep.phy.cam.ac.uk> Its never a good idea to force activation as you did below. what you should do instead is is sudo port -f deactivate libgcc11 libgcc then install libgcc-devel > On 15 Dec 2021, at 1:56 pm, VACCARI FRANCO wrote: > > So I did that, but a lot of messages care coming?s out, > > mm02:~ sudo port -f uninstall libgcc > Password: > ---> Unable to uninstall libgcc @5.0_0, the following ports depend on it: > ---> gcc11 @11.2.0_0 > Warning: Uninstall forced. Proceeding despite dependencies. > ---> Deactivating libgcc @5.0_0 > ---> Cleaning libgcc > ---> Uninstalling libgcc @5.0_0 > ---> Cleaning libgcc > > mm02:~ sudo port install libgcc-devel > > ---> Computing dependencies for libgcc-devel > ---> Fetching archive for libgcc-devel > ---> Attempting to fetch libgcc-devel-12-20211209_0.darwin_21.arm64.tbz2 from https://packages.macports.org/libgcc-devel > ---> Attempting to fetch libgcc-devel-12-20211209_0.darwin_21.arm64.tbz2.rmd160 from https://packages.macports.org/libgcc-devel > ---> Installing libgcc-devel @12-20211209_0 > ---> Activating libgcc-devel @12-20211209_0 > Error: Failed to activate libgcc-devel: Image error: /opt/local/include/gcc/c++/algorithm is being used by the active libgcc11 port. Please deactivate this port first, or use 'port -f activate libgcc-devel' to force the activation. > Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc-devel/libgcc-devel/main.log for details. > Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug. > Error: Processing of port libgcc-devel failed > > mm02:~ sudo port -f activate libgcc-devel > > ---> Computing dependencies for libgcc-devel > ---> Activating libgcc-devel @12-20211209_0 > Warning: File /opt/local/include/gcc/c++/algorithm already exists. Moving to: /opt/local/include/gcc/c++/algorithm.mp_1639575707. > Warning: File /opt/local/include/gcc/c++/any already exists. Moving to: /opt/local/include/gcc/c++/any.mp_1639575707. > Warning: File /opt/local/include/gcc/c++/array already exists. Moving to: /opt/local/include/gcc/c++/array.mp_1639575707. > Warning: File /opt/local/include/gcc/c++/atomic already exists. Moving to: /opt/local/include/gcc/c++/atomic.mp_1639575707. > Warning: File /opt/local/include/gcc/c++/backward/auto_ptr.h already exists. Moving to: /opt/local/include/gcc/c++/backward/auto_ptr.h.mp_1639575707. > Warning: File /opt/local/include/gcc/c++/backward/backward_warning.h already exists. Moving to: /opt/local/include/gcc/c++/backward/backward_warning.h.mp_1639575707. > Warning: File /opt/local/include/gcc/c++/backward/binders.h already exists. Moving to: /opt/local/include/gcc/c++/backward/binders.h.mp_1639575707. > Warning: File /opt/local/include/gcc/c++/backward/hash_fun.h already exists. Moving to: /opt/local/include/gcc/c++/backward/hash_fun.h.mp_1639575707. > Warning: File /opt/local/include/gcc/c++/backward/hash_map already exists. Moving to: /opt/local/include/gcc/c++/backward/hash_map.mp_1639575707. > Warning: File /opt/local/include/gcc/c++/backward/hash_set already exists. Moving to: /opt/local/include/gcc/c++/backward/hash_set.mp_1639575707. > ? > ? > ? > > tons of similar messages > > ? > ? > > Warning: File /opt/local/lib/libgcc/libatomic.1.dylib already exists. Moving to: /opt/local/lib/libgcc/libatomic.1.dylib.mp_1639575707. > Warning: File /opt/local/lib/libgcc/libgcc_s.1.1.dylib already exists. Moving to: /opt/local/lib/libgcc/libgcc_s.1.1.dylib.mp_1639575707. > Warning: File /opt/local/lib/libgcc/libgfortran.5.dylib already exists. Moving to: /opt/local/lib/libgcc/libgfortran.5.dylib.mp_1639575707. > Warning: File /opt/local/lib/libgcc/libgomp.1.dylib already exists. Moving to: /opt/local/lib/libgcc/libgomp.1.dylib.mp_1639575707. > Warning: File /opt/local/lib/libgcc/libitm.1.dylib already exists. Moving to: /opt/local/lib/libgcc/libitm.1.dylib.mp_1639575707. > Warning: File /opt/local/lib/libgcc/libobjc-gnu.4.dylib already exists. Moving to: /opt/local/lib/libgcc/libobjc-gnu.4.dylib.mp_1639575707. > Warning: File /opt/local/lib/libgcc/libssp.0.dylib already exists. Moving to: /opt/local/lib/libgcc/libssp.0.dylib.mp_1639575707. > Warning: File /opt/local/lib/libgcc/libstdc++.6.dylib already exists. Moving to: /opt/local/lib/libgcc/libstdc++.6.dylib.mp_1639575707. > Warning: File /opt/local/lib/libstdc++.6.dylib already exists. Moving to: /opt/local/lib/libstdc++.6.dylib.mp_1639575707. > ---> Cleaning libgcc-devel > ? miniadmin at mm02:~ > > After that I could install ImageMagick. > > So, should I happily disregard those warming messages? > > And, as I had previously installed gcc11, should I uninstall it and rather install gcc-devel? I?m afraid of mixing things up? > > Franco > > >> On 15 Dec 2021, at 12:56, Christopher Jones wrote: >> >> >> Please remember to reply to list... >> >> No. do not do that. >> >> sudo port -f uninstall libgcc >> sudo port install libgcc-devel >> >> >>> On 15 Dec 2021, at 11:54 am, VACCARI FRANCO wrote: >>> >>> Ok, I?ll delete all what I installed up to now and restart from scratch. My concern is that some packages will force the install of libgcc and some others will require libgcc-devel. Will see and report the outcome... >>> >>> Thanks >>> >>> Franco >>> >>> >>>> On 15 Dec 2021, at 12:51, Christopher Jones wrote: >>>> >>>> Hi, >>>> >>>> gcc-devel is the (current) preferred gcc compiler on Apple silicon at the moment, as none of the released gcc versions are fully stable on this platform. gcc-devel requires libgcc-devel as its runtime. libgcc and libgcc-devel are interchangeable, so you should remove libgcc and allow libgcc-devel to be installed instead. >>>> >>>> Chris >>>> >>>>> On 15 Dec 2021, at 11:37 am, VACCARI FRANCO wrote: >>>>> >>>>> I?m configuring a new Mac Mini M1 running Mac OS 12.1 and Xcode 13.2, and installing the usual packages I need. When dealing with ImageMagick I get the following error: >>>>> >>>>> mm02:~ sudo port install imagemagick >>>>> ---> Computing dependencies for ImageMagick >>>>> Error: Can't install libgcc-devel because conflicting ports are active: libgcc >>>>> Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug. >>>>> Error: Processing of port imagemagick failed >>>>> mm02:~ >>>>> >>>>> I believe that deactivating libgcc would break packages already installed that depend on it. Is it so, or can I deactivate libgcc and later activate it again? >>>>> >>>>> Thanks >>>>> >>>>> Franco >>>>> >>>>> >>>> >>> >> > -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 1930 bytes Desc: not available URL: From vaccari at units.it Wed Dec 15 14:09:58 2021 From: vaccari at units.it (VACCARI FRANCO) Date: Wed, 15 Dec 2021 14:09:58 +0000 Subject: ImageMagick failure to install In-Reply-To: <74ADC0F3-E21B-4064-84D2-2AB3981ECB1C@hep.phy.cam.ac.uk> References: <224170C6-70C7-4661-B124-850E28BD6219@ds.units.it> <8CDA8EE0-6778-4863-ADC9-47EC119E4886@hep.phy.cam.ac.uk> <3526B0A7-A388-4A6C-B609-98C112FEE207@ds.units.it> <74ADC0F3-E21B-4064-84D2-2AB3981ECB1C@hep.phy.cam.ac.uk> Message-ID: <11B06091-F925-4C05-96F5-4B3AB24823C1@ds.units.it> Eh, I gave the same weight to the two alternatives mentioned in the error message: Error: Failed to activate libgcc-devel: Image error: /opt/local/include/gcc/c++/algorithm is being used by the active libgcc11 port. Please deactivate this port first, or use 'port -f activate libgcc-devel' to force the activation. and chose the bad one? :-( At this point I prefer to uninstall everything and be more careful in the new adventure. Also, I will install gcc-devel instead of gcc11. > On 15 Dec 2021, at 14:59, Christopher Jones wrote: > > > Its never a good idea to force activation as you did below. > > what you should do instead is is > > sudo port -f deactivate libgcc11 libgcc > > then install libgcc-devel > >> On 15 Dec 2021, at 1:56 pm, VACCARI FRANCO wrote: >> >> So I did that, but a lot of messages care coming?s out, >> >> mm02:~ sudo port -f uninstall libgcc >> Password: >> ---> Unable to uninstall libgcc @5.0_0, the following ports depend on it: >> ---> gcc11 @11.2.0_0 >> Warning: Uninstall forced. Proceeding despite dependencies. >> ---> Deactivating libgcc @5.0_0 >> ---> Cleaning libgcc >> ---> Uninstalling libgcc @5.0_0 >> ---> Cleaning libgcc >> >> mm02:~ sudo port install libgcc-devel >> >> ---> Computing dependencies for libgcc-devel >> ---> Fetching archive for libgcc-devel >> ---> Attempting to fetch libgcc-devel-12-20211209_0.darwin_21.arm64.tbz2 from https://packages.macports.org/libgcc-devel >> ---> Attempting to fetch libgcc-devel-12-20211209_0.darwin_21.arm64.tbz2.rmd160 from https://packages.macports.org/libgcc-devel >> ---> Installing libgcc-devel @12-20211209_0 >> ---> Activating libgcc-devel @12-20211209_0 >> Error: Failed to activate libgcc-devel: Image error: /opt/local/include/gcc/c++/algorithm is being used by the active libgcc11 port. Please deactivate this port first, or use 'port -f activate libgcc-devel' to force the activation. >> Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc-devel/libgcc-devel/main.log for details. >> Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug. >> Error: Processing of port libgcc-devel failed >> >> mm02:~ sudo port -f activate libgcc-devel >> >> ---> Computing dependencies for libgcc-devel >> ---> Activating libgcc-devel @12-20211209_0 >> Warning: File /opt/local/include/gcc/c++/algorithm already exists. Moving to: /opt/local/include/gcc/c++/algorithm.mp_1639575707. >> Warning: File /opt/local/include/gcc/c++/any already exists. Moving to: /opt/local/include/gcc/c++/any.mp_1639575707. >> Warning: File /opt/local/include/gcc/c++/array already exists. Moving to: /opt/local/include/gcc/c++/array.mp_1639575707. >> Warning: File /opt/local/include/gcc/c++/atomic already exists. Moving to: /opt/local/include/gcc/c++/atomic.mp_1639575707. >> Warning: File /opt/local/include/gcc/c++/backward/auto_ptr.h already exists. Moving to: /opt/local/include/gcc/c++/backward/auto_ptr.h.mp_1639575707. >> Warning: File /opt/local/include/gcc/c++/backward/backward_warning.h already exists. Moving to: /opt/local/include/gcc/c++/backward/backward_warning.h.mp_1639575707. >> Warning: File /opt/local/include/gcc/c++/backward/binders.h already exists. Moving to: /opt/local/include/gcc/c++/backward/binders.h.mp_1639575707. >> Warning: File /opt/local/include/gcc/c++/backward/hash_fun.h already exists. Moving to: /opt/local/include/gcc/c++/backward/hash_fun.h.mp_1639575707. >> Warning: File /opt/local/include/gcc/c++/backward/hash_map already exists. Moving to: /opt/local/include/gcc/c++/backward/hash_map.mp_1639575707. >> Warning: File /opt/local/include/gcc/c++/backward/hash_set already exists. Moving to: /opt/local/include/gcc/c++/backward/hash_set.mp_1639575707. >> ? >> ? >> ? >> >> tons of similar messages >> >> ? >> ? >> >> Warning: File /opt/local/lib/libgcc/libatomic.1.dylib already exists. Moving to: /opt/local/lib/libgcc/libatomic.1.dylib.mp_1639575707. >> Warning: File /opt/local/lib/libgcc/libgcc_s.1.1.dylib already exists. Moving to: /opt/local/lib/libgcc/libgcc_s.1.1.dylib.mp_1639575707. >> Warning: File /opt/local/lib/libgcc/libgfortran.5.dylib already exists. Moving to: /opt/local/lib/libgcc/libgfortran.5.dylib.mp_1639575707. >> Warning: File /opt/local/lib/libgcc/libgomp.1.dylib already exists. Moving to: /opt/local/lib/libgcc/libgomp.1.dylib.mp_1639575707. >> Warning: File /opt/local/lib/libgcc/libitm.1.dylib already exists. Moving to: /opt/local/lib/libgcc/libitm.1.dylib.mp_1639575707. >> Warning: File /opt/local/lib/libgcc/libobjc-gnu.4.dylib already exists. Moving to: /opt/local/lib/libgcc/libobjc-gnu.4.dylib.mp_1639575707. >> Warning: File /opt/local/lib/libgcc/libssp.0.dylib already exists. Moving to: /opt/local/lib/libgcc/libssp.0.dylib.mp_1639575707. >> Warning: File /opt/local/lib/libgcc/libstdc++.6.dylib already exists. Moving to: /opt/local/lib/libgcc/libstdc++.6.dylib.mp_1639575707. >> Warning: File /opt/local/lib/libstdc++.6.dylib already exists. Moving to: /opt/local/lib/libstdc++.6.dylib.mp_1639575707. >> ---> Cleaning libgcc-devel >> ? miniadmin at mm02:~ >> >> After that I could install ImageMagick. >> >> So, should I happily disregard those warming messages? >> >> And, as I had previously installed gcc11, should I uninstall it and rather install gcc-devel? I?m afraid of mixing things up? >> >> Franco >> >> >>> On 15 Dec 2021, at 12:56, Christopher Jones wrote: >>> >>> >>> Please remember to reply to list... >>> >>> No. do not do that. >>> >>> sudo port -f uninstall libgcc >>> sudo port install libgcc-devel >>> >>> >>>> On 15 Dec 2021, at 11:54 am, VACCARI FRANCO wrote: >>>> >>>> Ok, I?ll delete all what I installed up to now and restart from scratch. My concern is that some packages will force the install of libgcc and some others will require libgcc-devel. Will see and report the outcome... >>>> >>>> Thanks >>>> >>>> Franco >>>> >>>> >>>>> On 15 Dec 2021, at 12:51, Christopher Jones wrote: >>>>> >>>>> Hi, >>>>> >>>>> gcc-devel is the (current) preferred gcc compiler on Apple silicon at the moment, as none of the released gcc versions are fully stable on this platform. gcc-devel requires libgcc-devel as its runtime. libgcc and libgcc-devel are interchangeable, so you should remove libgcc and allow libgcc-devel to be installed instead. >>>>> >>>>> Chris >>>>> >>>>>> On 15 Dec 2021, at 11:37 am, VACCARI FRANCO wrote: >>>>>> >>>>>> I?m configuring a new Mac Mini M1 running Mac OS 12.1 and Xcode 13.2, and installing the usual packages I need. When dealing with ImageMagick I get the following error: >>>>>> >>>>>> mm02:~ sudo port install imagemagick >>>>>> ---> Computing dependencies for ImageMagick >>>>>> Error: Can't install libgcc-devel because conflicting ports are active: libgcc >>>>>> Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug. >>>>>> Error: Processing of port imagemagick failed >>>>>> mm02:~ >>>>>> >>>>>> I believe that deactivating libgcc would break packages already installed that depend on it. Is it so, or can I deactivate libgcc and later activate it again? >>>>>> >>>>>> Thanks >>>>>> >>>>>> Franco >>>>>> >>>>>> >>>>> >>>> >>> >> > From vaccari at units.it Wed Dec 15 16:46:02 2021 From: vaccari at units.it (VACCARI FRANCO) Date: Wed, 15 Dec 2021 16:46:02 +0000 Subject: ImageMagick failure to install In-Reply-To: <11B06091-F925-4C05-96F5-4B3AB24823C1@ds.units.it> References: <224170C6-70C7-4661-B124-850E28BD6219@ds.units.it> <8CDA8EE0-6778-4863-ADC9-47EC119E4886@hep.phy.cam.ac.uk> <3526B0A7-A388-4A6C-B609-98C112FEE207@ds.units.it> <74ADC0F3-E21B-4064-84D2-2AB3981ECB1C@hep.phy.cam.ac.uk> <11B06091-F925-4C05-96F5-4B3AB24823C1@ds.units.it> Message-ID: After cleaning and uninstalling all installed ports, I installed gcc-devel instead of gcc11 and that solved the issue. I could install all packages I need after that. Thanks Chris for your help Franco > On 15 Dec 2021, at 15:09, VACCARI FRANCO wrote: > > Eh, I gave the same weight to the two alternatives mentioned in the error message: > > Error: Failed to activate libgcc-devel: Image error: /opt/local/include/gcc/c++/algorithm is being used by the active libgcc11 port. Please deactivate this port first, or use 'port -f activate libgcc-devel' to force the activation. > > and chose the bad one? :-( > > At this point I prefer to uninstall everything and be more careful in the new adventure. Also, I will install gcc-devel instead of gcc11. > > >> On 15 Dec 2021, at 14:59, Christopher Jones wrote: >> >> >> Its never a good idea to force activation as you did below. >> >> what you should do instead is is >> >> sudo port -f deactivate libgcc11 libgcc >> >> then install libgcc-devel >> >>> On 15 Dec 2021, at 1:56 pm, VACCARI FRANCO wrote: >>> >>> So I did that, but a lot of messages care coming?s out, >>> >>> mm02:~ sudo port -f uninstall libgcc >>> Password: >>> ---> Unable to uninstall libgcc @5.0_0, the following ports depend on it: >>> ---> gcc11 @11.2.0_0 >>> Warning: Uninstall forced. Proceeding despite dependencies. >>> ---> Deactivating libgcc @5.0_0 >>> ---> Cleaning libgcc >>> ---> Uninstalling libgcc @5.0_0 >>> ---> Cleaning libgcc >>> >>> mm02:~ sudo port install libgcc-devel >>> >>> ---> Computing dependencies for libgcc-devel >>> ---> Fetching archive for libgcc-devel >>> ---> Attempting to fetch libgcc-devel-12-20211209_0.darwin_21.arm64.tbz2 from https://packages.macports.org/libgcc-devel >>> ---> Attempting to fetch libgcc-devel-12-20211209_0.darwin_21.arm64.tbz2.rmd160 from https://packages.macports.org/libgcc-devel >>> ---> Installing libgcc-devel @12-20211209_0 >>> ---> Activating libgcc-devel @12-20211209_0 >>> Error: Failed to activate libgcc-devel: Image error: /opt/local/include/gcc/c++/algorithm is being used by the active libgcc11 port. Please deactivate this port first, or use 'port -f activate libgcc-devel' to force the activation. >>> Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc-devel/libgcc-devel/main.log for details. >>> Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug. >>> Error: Processing of port libgcc-devel failed >>> >>> mm02:~ sudo port -f activate libgcc-devel >>> >>> ---> Computing dependencies for libgcc-devel >>> ---> Activating libgcc-devel @12-20211209_0 >>> Warning: File /opt/local/include/gcc/c++/algorithm already exists. Moving to: /opt/local/include/gcc/c++/algorithm.mp_1639575707. >>> Warning: File /opt/local/include/gcc/c++/any already exists. Moving to: /opt/local/include/gcc/c++/any.mp_1639575707. >>> Warning: File /opt/local/include/gcc/c++/array already exists. Moving to: /opt/local/include/gcc/c++/array.mp_1639575707. >>> Warning: File /opt/local/include/gcc/c++/atomic already exists. Moving to: /opt/local/include/gcc/c++/atomic.mp_1639575707. >>> Warning: File /opt/local/include/gcc/c++/backward/auto_ptr.h already exists. Moving to: /opt/local/include/gcc/c++/backward/auto_ptr.h.mp_1639575707. >>> Warning: File /opt/local/include/gcc/c++/backward/backward_warning.h already exists. Moving to: /opt/local/include/gcc/c++/backward/backward_warning.h.mp_1639575707. >>> Warning: File /opt/local/include/gcc/c++/backward/binders.h already exists. Moving to: /opt/local/include/gcc/c++/backward/binders.h.mp_1639575707. >>> Warning: File /opt/local/include/gcc/c++/backward/hash_fun.h already exists. Moving to: /opt/local/include/gcc/c++/backward/hash_fun.h.mp_1639575707. >>> Warning: File /opt/local/include/gcc/c++/backward/hash_map already exists. Moving to: /opt/local/include/gcc/c++/backward/hash_map.mp_1639575707. >>> Warning: File /opt/local/include/gcc/c++/backward/hash_set already exists. Moving to: /opt/local/include/gcc/c++/backward/hash_set.mp_1639575707. >>> ? >>> ? >>> ? >>> >>> tons of similar messages >>> >>> ? >>> ? >>> >>> Warning: File /opt/local/lib/libgcc/libatomic.1.dylib already exists. Moving to: /opt/local/lib/libgcc/libatomic.1.dylib.mp_1639575707. >>> Warning: File /opt/local/lib/libgcc/libgcc_s.1.1.dylib already exists. Moving to: /opt/local/lib/libgcc/libgcc_s.1.1.dylib.mp_1639575707. >>> Warning: File /opt/local/lib/libgcc/libgfortran.5.dylib already exists. Moving to: /opt/local/lib/libgcc/libgfortran.5.dylib.mp_1639575707. >>> Warning: File /opt/local/lib/libgcc/libgomp.1.dylib already exists. Moving to: /opt/local/lib/libgcc/libgomp.1.dylib.mp_1639575707. >>> Warning: File /opt/local/lib/libgcc/libitm.1.dylib already exists. Moving to: /opt/local/lib/libgcc/libitm.1.dylib.mp_1639575707. >>> Warning: File /opt/local/lib/libgcc/libobjc-gnu.4.dylib already exists. Moving to: /opt/local/lib/libgcc/libobjc-gnu.4.dylib.mp_1639575707. >>> Warning: File /opt/local/lib/libgcc/libssp.0.dylib already exists. Moving to: /opt/local/lib/libgcc/libssp.0.dylib.mp_1639575707. >>> Warning: File /opt/local/lib/libgcc/libstdc++.6.dylib already exists. Moving to: /opt/local/lib/libgcc/libstdc++.6.dylib.mp_1639575707. >>> Warning: File /opt/local/lib/libstdc++.6.dylib already exists. Moving to: /opt/local/lib/libstdc++.6.dylib.mp_1639575707. >>> ---> Cleaning libgcc-devel >>> ? miniadmin at mm02:~ >>> >>> After that I could install ImageMagick. >>> >>> So, should I happily disregard those warming messages? >>> >>> And, as I had previously installed gcc11, should I uninstall it and rather install gcc-devel? I?m afraid of mixing things up? >>> >>> Franco >>> >>> >>>> On 15 Dec 2021, at 12:56, Christopher Jones wrote: >>>> >>>> >>>> Please remember to reply to list... >>>> >>>> No. do not do that. >>>> >>>> sudo port -f uninstall libgcc >>>> sudo port install libgcc-devel >>>> >>>> >>>>> On 15 Dec 2021, at 11:54 am, VACCARI FRANCO wrote: >>>>> >>>>> Ok, I?ll delete all what I installed up to now and restart from scratch. My concern is that some packages will force the install of libgcc and some others will require libgcc-devel. Will see and report the outcome... >>>>> >>>>> Thanks >>>>> >>>>> Franco >>>>> >>>>> >>>>>> On 15 Dec 2021, at 12:51, Christopher Jones wrote: >>>>>> >>>>>> Hi, >>>>>> >>>>>> gcc-devel is the (current) preferred gcc compiler on Apple silicon at the moment, as none of the released gcc versions are fully stable on this platform. gcc-devel requires libgcc-devel as its runtime. libgcc and libgcc-devel are interchangeable, so you should remove libgcc and allow libgcc-devel to be installed instead. >>>>>> >>>>>> Chris >>>>>> >>>>>>> On 15 Dec 2021, at 11:37 am, VACCARI FRANCO wrote: >>>>>>> >>>>>>> I?m configuring a new Mac Mini M1 running Mac OS 12.1 and Xcode 13.2, and installing the usual packages I need. When dealing with ImageMagick I get the following error: >>>>>>> >>>>>>> mm02:~ sudo port install imagemagick >>>>>>> ---> Computing dependencies for ImageMagick >>>>>>> Error: Can't install libgcc-devel because conflicting ports are active: libgcc >>>>>>> Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug. >>>>>>> Error: Processing of port imagemagick failed >>>>>>> mm02:~ >>>>>>> >>>>>>> I believe that deactivating libgcc would break packages already installed that depend on it. Is it so, or can I deactivate libgcc and later activate it again? >>>>>>> >>>>>>> Thanks >>>>>>> >>>>>>> Franco >>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> > From dave at horsfall.org Wed Dec 15 20:18:00 2021 From: dave at horsfall.org (Dave Horsfall) Date: Thu, 16 Dec 2021 07:18:00 +1100 (EST) Subject: pwait? In-Reply-To: <20309226-2CF1-4031-9421-84B41F6C24BD@macports.org> References: <20309226-2CF1-4031-9421-84B41F6C24BD@macports.org> Message-ID: On Tue, 14 Dec 2021, Ryan Schmidt wrote: > > Wishing for a port...bit ugly when you can't use the supplied > > Makefile. Sadly, not volunteering myself. :-/ > > Added! Thanks for the suggestion. That was quick! Compiling the FreeBSD source was easy, though; I've found that most FreeBSD sources work with little if any changes. -- Dave From dave at horsfall.org Wed Dec 15 20:25:45 2021 From: dave at horsfall.org (Dave Horsfall) Date: Thu, 16 Dec 2021 07:25:45 +1100 (EST) Subject: Cannot build libb2 In-Reply-To: <4C226EA1-952F-4E70-90D9-F8D2DC6989FB@macports.org> References: <4C226EA1-952F-4E70-90D9-F8D2DC6989FB@macports.org> Message-ID: On Fri, 10 Dec 2021, Ryan Schmidt wrote: > The "-arch x86_64 -arch i386" in the log does seem to indicate MacPorts > is doing a universal build. The ways that could happen: > > * You specified +universal on the command line Nope... > * You specified +universal in variants.conf Nope... > * You installed a port that, because it does not support your machine's > native architecture, requires its dependencies to be installed > universal. Could be; how do I tell which variants were used by what? > If libb2 does not build universal, then that is certainly something we > should fix. A bug has already been filed about it: > > https://trac.macports.org/ticket/64148 Thanks; I'll try the suggested fix, but... > If you want to explore why libb2 is building universal when you don't > intend that, show us what command you ran and the output. Specifically, > we'd want to know which port you are trying to install or upgrade when > libb2 gets build universal. It was no more than my weekly "port selfupdate; port upgrade outdated" etc. Looks like I forgot to run it under "script", but when I tried again it now mysteriously works, so I dunno... Chalk it up to a "heisenbug", I guess (I hate those). -- Dave From rlhamil at smart.net Thu Dec 16 04:48:33 2021 From: rlhamil at smart.net (Richard L. Hamilton) Date: Wed, 15 Dec 2021 23:48:33 -0500 Subject: Xcode 13.2 from App Store problem reported Message-ID: <836207D4-CEC5-4C86-A35E-499CE4B19A15@smart.net> Apparently the developer download site (NOT Mac App store) version is ok. Not that most of us are in a rush to update, but just in case... https://www.macrumors.com/2021/12/14/xcode-13-2-bug/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From earle at isolar.DynDNS.ORG Thu Dec 16 08:55:43 2021 From: earle at isolar.DynDNS.ORG (Greg Earle) Date: Thu, 16 Dec 2021 00:55:43 -0800 Subject: "Broken files found, but all associated ports are not in the index" error Message-ID: <9B3743FD-871C-41A5-8378-EC58706BDD04@isolar.DynDNS.ORG> On a 2010 Mac Pro running macOS Mojave 10.14.6, I'm getting this: -- [0:48] nightowl:/ % sudo port upgrade outdated Nothing to upgrade. ---> Scanning binaries for linking errors ---> Found 2 broken files, matching files to ports Warning: No port p5.26-net-ssleay found in the index; can't rebuild ---> Broken files found, but all associated ports are not in the index and so cannot be rebuilt. [0:49] nightowl:/ % port installed p5.26-net-ssleay The following ports are currently installed: p5.26-net-ssleay @1.900.0_0 (active) [0:50] nightowl:/ % port info p5.26-net-ssleay Error: Port p5.26-net-ssleay not found -- Tried to remove it but it didn't like that: -- [0:52] nightowl:/ % sudo port uninstall p5.26-net-ssleay Note: It is not recommended to uninstall/deactivate a port that has dependents as it breaks the dependents. The following ports will break: p5.26-io-socket-ssl @2.68.0_0 p5.26-http-tiny @0.76.0_0 p5.26-io-socket-ssl @2.69.0_0 p5.26-io-socket-ssl @2.70.0_0 p5.26-io-socket-ssl @2.71.0_0 Continue? [y/N]: N ---> Cleaning p5.26-net-ssleay -- Is there anything I can do about it? I still have a ton of p5.26-* and p5.28-* ports installed, as well as p5.30-*. -- [0:54] nightowl:/ % sudo port installed | grep p5.26 | wc -l 134 -- Thanks, - Greg From lenorehorner at sbcglobal.net Thu Dec 16 17:33:08 2021 From: lenorehorner at sbcglobal.net (Lenore Horner) Date: Thu, 16 Dec 2021 12:33:08 -0500 Subject: Files and Folders access References: <7493BB72-621E-4E3F-B9E3-11C3626FFE0C.ref@sbcglobal.net> Message-ID: <7493BB72-621E-4E3F-B9E3-11C3626FFE0C@sbcglobal.net> I?m still struggling with letting Inkscape (I think Gimp too) installed via MacPorts to be able to open files. I?ve searched the mailing list archive for the last year for any mention of this and found zip so apparently I?m particularly incompetent. Here?s what I?ve tried. Big Sur 11.6 MacPorts base 2.7.1 Just updated the tree and all anything listed as outdated. inkscape-app @0.92_1, inkscape @0.92.5_9_x11, and xorg-server @1.20.11_1 installed and active r In Apple -> System Preferences -> Security and Privacy -> Files and Folders I cannot do any thing even having unlocked with an admin password. In Apple -> System Preferences -> Security and Privacy -> Full Disk Access I have given the following access the following: Inkscape (the terminal app found with Show Contents in the Inkscape.app file in my MacPorts folder) Xquartz Terminal X11.app Inkscape.app (the Inkscape icon in the MacPorts folder) I?ve shut down and restarted the computer and I?m still getting "Could not read the contents of Desktop? and a parallel complaint for Documents. I know that a dialog box should pop up asking for my permission to access my Desktop, Documents, etc. folder and that those dialogs not popping up is a known (and unfixible I think) issue. I thought granting full disk access was the only known work-around, but full disk access to what? I have, by the way also tried the dmg from the Inkscape website for version 1.1.1. I don?t get error messages with it, but it also can?t open a file (spinning beachball of death). So that?s not good either. Thanks, Lenore -------------- next part -------------- An HTML attachment was scrubbed... URL: From frank at fdsd.co.uk Thu Dec 16 19:58:02 2021 From: frank at fdsd.co.uk (Frank Dean) Date: Thu, 16 Dec 2021 19:58:02 +0000 Subject: Files and Folders access In-Reply-To: <7493BB72-621E-4E3F-B9E3-11C3626FFE0C@sbcglobal.net> (message from Lenore Horner on Thu, 16 Dec 2021 12:33:08 -0500) Message-ID: Lenore Horner writes: > [1:text/plain Show] > > > [2:text/html Hide Save:noname (7kB)] > > I?m still struggling with letting Inkscape (I think Gimp too) installed via MacPorts to be able to open files. I?ve searched the mailing list archive for the last > year for any mention of this and found zip so apparently I?m particularly incompetent. Here?s what I?ve tried. > > Big Sur 11.6 > MacPorts base 2.7.1 > Just updated the tree and all anything listed as outdated. > inkscape-app @0.92_1, inkscape @0.92.5_9_x11, and xorg-server @1.20.11_1 installed and active > r > In Apple -> System Preferences -> Security and Privacy -> Files and Folders I cannot do any thing even having unlocked with an admin password. > In Apple -> System Preferences -> Security and Privacy -> Full Disk Access I have given the following access the following: > Inkscape (the terminal app found with Show Contents in the Inkscape.app file in my MacPorts folder) > Xquartz > Terminal > X11.app > Inkscape.app (the Inkscape icon in the MacPorts folder) > > I?ve shut down and restarted the computer and I?m still getting "Could not read the contents of Desktop? and a parallel complaint for Documents. I know > that a dialog box should pop up asking for my permission to access my Desktop, Documents, etc. folder and that those dialogs not popping up is a known > (and unfixible I think) issue. I thought granting full disk access was the only known work-around, but full disk access to what? > > I have, by the way also tried the dmg from the Inkscape website for version 1.1.1. I don?t get error messages with it, but it also can?t open a file (spinning > beachball of death). So that?s not good either. > > Thanks, > Lenore Hi Lenore, I don't know if this is the **proper** way to do it, but after running Inkscape via the launcher, `ps ux | grep -i inkscape` shows Inkscape is being executed via `/bin/sh`. Giving `/bin/sh` full disk access allows it to open files in the Documents folder, but presumably this allows pretty well all applications to access the entire disk, somewhat subverting the entire privacy mechanism. Hopefully, someone knows of a better way. Similarly, granting the Terminal application access to the Documents folder allows you to execute the inkscape binary from `/usr/local/bin` and open documents in the Documents folder, with the advantage of being able to reduce the scope of access. All, far from intuitive. Cheers, Frank From iandw.au at gmail.com Thu Dec 16 22:58:19 2021 From: iandw.au at gmail.com (Ian Wadham) Date: Fri, 17 Dec 2021 09:58:19 +1100 Subject: Files and Folders access In-Reply-To: <7493BB72-621E-4E3F-B9E3-11C3626FFE0C@sbcglobal.net> References: <7493BB72-621E-4E3F-B9E3-11C3626FFE0C.ref@sbcglobal.net> <7493BB72-621E-4E3F-B9E3-11C3626FFE0C@sbcglobal.net> Message-ID: <756778DD-78D3-49E4-B64E-A32328C84694@gmail.com> I have had two similar issues, but with Catalina. One where Gimp (from the Gimp website, not Macports) would not save a file to my Desktop and the other where Apple??s Screenshot facility (Command-Shift-4) would not save to it, although it had always done so automatically in High Sierra and earlier O/Ss. I got onto Apple Support?s chat line about the first, and they suggested to upgrade my Gimp, which I did and it worked. The failure to save a screenshot to my Desktop actually occurred during the chat with Apple, but I was unable to investigate at the time. A day later I wanted to take a screenshot and send it by email. Same problem. All the usual Unix permissions on my Desktop seemed fine, but there is a new extension called ?com.apple.macl? which works some kind of magic (ls - at ld ~/Desktop to see it). Nothing I did at the command-line could fix the problem with my Desktop. Eventually I found the ?approved? method of making my own Desktop accessible to me again. 1. Bring up a Finder window. 2. in the left-hand column, right-click on ?Desktop? and select ?Get Info? from the popup menu. 3. Scroll to the bottom of the Info window and click on the tiny ?lock? icon. 4. When requested, enter your Admin password. 5. Click on ?+?. A window listing Users and Groups should appear. 6. Select one (e.g. yourself). This should now appear in the Info window?s list, with Privilege ?Read only". 7. Click on the Privilege and select ?Read & Write? from the popup list. 8. Click on the little ?lock? again, to close it. Not exactly ?intuitive?? I would say. Also Apple?s action regarding my Desktop, when it installed Catalina for me, is rather like a builder calling at my house to do some work, then changing the lock on my front door in the process, not telling me about this and then not leaving me a new key. I believe Apple?s intentions are still good, but they are becoming careless of their users? interests. That works against them because I thought at first that they are becoming like IBM in the "bad old days? of the 60s and 70s. I thought they were trying to ?influence" me to use only Apple products on my computer. Re Gimp, I now have Gimp 2.10.28 from Gimp?s website. It has been upgraded to follow Apple?s latest security protocol. The first time I asked it to save to my Desktop, I got a dialog box asking permission and requiring an Admin password. After that it has been fine and is now on the list of ?approved? applications in System Preferences->Security and Privacy->Privacy->Files and Folders. Hope some of this helps. Ian Wadham. > On 17 Dec 2021, at 4:33 am, Lenore Horner wrote: > > I?m still struggling with letting Inkscape (I think Gimp too) installed via MacPorts to be able to open files. I?ve searched the mailing list archive for the last year for any mention of this and found zip so apparently I?m particularly incompetent. Here?s what I?ve tried. > > Big Sur 11.6 > MacPorts base 2.7.1 > Just updated the tree and all anything listed as outdated. > inkscape-app @0.92_1, inkscape @0.92.5_9_x11, and xorg-server @1.20.11_1 installed and active > r > In Apple -> System Preferences -> Security and Privacy -> Files and Folders I cannot do any thing even having unlocked with an admin password. > In Apple -> System Preferences -> Security and Privacy -> Full Disk Access I have given the following access the following: > Inkscape (the terminal app found with Show Contents in the Inkscape.app file in my MacPorts folder) > Xquartz > Terminal > X11.app > Inkscape.app (the Inkscape icon in the MacPorts folder) > > I?ve shut down and restarted the computer and I?m still getting "Could not read the contents of Desktop? and a parallel complaint for Documents. I know that a dialog box should pop up asking for my permission to access my Desktop, Documents, etc. folder and that those dialogs not popping up is a known (and unfixible I think) issue. I thought granting full disk access was the only known work-around, but full disk access to what? > > I have, by the way also tried the dmg from the Inkscape website for version 1.1.1. I don?t get error messages with it, but it also can?t open a file (spinning beachball of death). So that?s not good either. > > Thanks, > Lenore From ryandesign at macports.org Thu Dec 16 23:07:54 2021 From: ryandesign at macports.org (Ryan Schmidt) Date: Thu, 16 Dec 2021 17:07:54 -0600 Subject: Cannot build libb2 In-Reply-To: References: <4C226EA1-952F-4E70-90D9-F8D2DC6989FB@macports.org> Message-ID: <039E4D96-46EA-4670-A199-BBA3D16B20CC@macports.org> On Dec 15, 2021, at 14:25, Dave Horsfall wrote: > On Fri, 10 Dec 2021, Ryan Schmidt wrote: > >> The "-arch x86_64 -arch i386" in the log does seem to indicate MacPorts >> is doing a universal build. The ways that could happen: >> >> * You specified +universal on the command line > > Nope... > >> * You specified +universal in variants.conf > > Nope... > >> * You installed a port that, because it does not support your machine's >> native architecture, requires its dependencies to be installed >> universal. > > Could be; how do I tell which variants were used by what? If you are installing a port that indicates, for example, that it only supports i386, and it depends on other ports, then MacPorts must install those other ports universal for i386 and x86_64. If it did not, then you would only have an x86_64 version of them, which wouldn't be sufficient for whichever port it is that only supports i386. To discover which of your installed ports fit that description, you could run: port -qv installed | grep -Ev 'archs=.*noarch|x86_64' >> If libb2 does not build universal, then that is certainly something we >> should fix. A bug has already been filed about it: >> >> https://trac.macports.org/ticket/64148 > > Thanks; I'll try the suggested fix, but... > >> If you want to explore why libb2 is building universal when you don't >> intend that, show us what command you ran and the output. Specifically, >> we'd want to know which port you are trying to install or upgrade when >> libb2 gets build universal. > > It was no more than my weekly "port selfupdate; port upgrade outdated" > etc. Great, so one of your outdated ports, or one of its dependencies, is causing libb2 to build universal. We'd need to see the output of your commands, possibly with debug output, to know which one, if the above `port -qv installed ...` command doesn't provide the answer. > Looks like I forgot to run it under "script", but when I tried again it > now mysteriously works, so I dunno... Chalk it up to a "heisenbug", I > guess (I hate those). If you selfupdated or synced before trying again, then your success is expected, since I fixed the problem as indicated in #64148. From ryandesign at macports.org Thu Dec 16 23:08:50 2021 From: ryandesign at macports.org (Ryan Schmidt) Date: Thu, 16 Dec 2021 17:08:50 -0600 Subject: "Broken files found, but all associated ports are not in the index" error In-Reply-To: <9B3743FD-871C-41A5-8378-EC58706BDD04@isolar.DynDNS.ORG> References: <9B3743FD-871C-41A5-8378-EC58706BDD04@isolar.DynDNS.ORG> Message-ID: <00921785-1C28-4289-8BE3-E38726E8CB47@macports.org> On Dec 16, 2021, at 02:55, Greg Earle wrote: > > On a 2010 Mac Pro running macOS Mojave 10.14.6, I'm getting this: > > -- > [0:48] nightowl:/ % sudo port upgrade outdated > Nothing to upgrade. > ---> Scanning binaries for linking errors > ---> Found 2 broken files, matching files to ports > Warning: No port p5.26-net-ssleay found in the index; can't rebuild > ---> Broken files found, but all associated ports are not in the index and so cannot be rebuilt. > > [0:49] nightowl:/ % port installed p5.26-net-ssleay > The following ports are currently installed: > p5.26-net-ssleay @1.900.0_0 (active) > > [0:50] nightowl:/ % port info p5.26-net-ssleay > Error: Port p5.26-net-ssleay not found > -- > > Tried to remove it but it didn't like that: > > -- > [0:52] nightowl:/ % sudo port uninstall p5.26-net-ssleay > Note: It is not recommended to uninstall/deactivate a port that has dependents as it breaks the dependents. > The following ports will break: > p5.26-io-socket-ssl @2.68.0_0 > p5.26-http-tiny @0.76.0_0 > p5.26-io-socket-ssl @2.69.0_0 > p5.26-io-socket-ssl @2.70.0_0 > p5.26-io-socket-ssl @2.71.0_0 > Continue? [y/N]: N > ---> Cleaning p5.26-net-ssleay > -- > > Is there anything I can do about it? I still have a ton of p5.26-* and p5.28-* ports installed, as well as p5.30-*. > > -- > [0:54] nightowl:/ % sudo port installed | grep p5.26 | wc -l > 134 I recommend uninstalling all p5.26 ports. Use p5.28 equivalents instead. From dluke at geeklair.net Fri Dec 17 16:49:40 2021 From: dluke at geeklair.net (Daniel J. Luke) Date: Fri, 17 Dec 2021 11:49:40 -0500 Subject: "Broken files found, but all associated ports are not in the index" error In-Reply-To: <00921785-1C28-4289-8BE3-E38726E8CB47@macports.org> References: <9B3743FD-871C-41A5-8378-EC58706BDD04@isolar.DynDNS.ORG> <00921785-1C28-4289-8BE3-E38726E8CB47@macports.org> Message-ID: On Dec 16, 2021, at 6:08 PM, Ryan Schmidt wrote: >> Is there anything I can do about it? I still have a ton of p5.26-* and p5.28-* ports installed, as well as p5.30-*. > > I recommend uninstalling all p5.26 ports. Use p5.28 equivalents instead. Unfortunately, this cleanup is necessary because MacPorts has decided to support multiple versions of perl5 (which I think is a bad choice). If MacPorts instead had a perl5 port that tracked the latest perl5, the end-use experience would be 'port upgrade outdated' and everything could continue to work (provided we bumped the revision of all of the p5- ports and/or added some update to base or to a portgroup to make that unnecessary). Instead you need to periodically uninstall any p5.XX ports and older perl5 - install equivalent newer perl5 and p5.XX ports that you want to use directly ... and /also/ find any ports that you have installed that use a variant to specify which perl5 version they want and uninstall + reinstall them with the new variant that points to the newer perl5 that you want. It's enough effort that I, personally, don't use MacPorts perl for anything other than MacPorts dependencies - and instead use perlbrew to manage a perl install for any of my stuff that uses perl. -- Daniel J. Luke From rlhamil at smart.net Sun Dec 19 07:32:46 2021 From: rlhamil at smart.net (Richard L. Hamilton) Date: Sun, 19 Dec 2021 02:32:46 -0500 Subject: Xcode 13.2 from App Store problem reported In-Reply-To: <836207D4-CEC5-4C86-A35E-499CE4B19A15@smart.net> References: <836207D4-CEC5-4C86-A35E-499CE4B19A15@smart.net> Message-ID: <921C17A3-DC4D-4903-8C26-DA576D1B9CC9@smart.net> https://developer.apple.com/documentation/xcode-release-notes/xcode-13_2_1-release-notes 13.2.1 looks like it would fix that, and has a workaround for vulnerable log4j within Xcode (used as part of app store upload, I guess). > On Dec 15, 2021, at 23:48, Richard L. Hamilton wrote: > > Apparently the developer download site (NOT Mac App store) version is ok. Not that most of us are in a rush to update, but just in case... > https://www.macrumors.com/2021/12/14/xcode-13-2-bug/ > -- eMail: mailto:rlhamil at smart.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From dandunfee at gmail.com Mon Dec 20 15:12:29 2021 From: dandunfee at gmail.com (dan d.) Date: Mon, 20 Dec 2021 10:12:29 -0500 (EST) Subject: Failure to activate Message-ID: Recently I have increasingly begun to get the failure to activate on installs and upgrades. It prompts to use the "-f activate portname" approach. This begins but never finishes; requiring a control-c to stop it. Any ideas? Thanks. -- ent- XR From audvare at gmail.com Mon Dec 20 21:46:06 2021 From: audvare at gmail.com (Andrew Udvare) Date: Mon, 20 Dec 2021 16:46:06 -0500 Subject: Failure to activate In-Reply-To: References: Message-ID: Do you have any kind of antivirus software running? On Mon, Dec 20, 2021, 10:12 dan d. wrote: > > Recently I have increasingly begun to get the failure to activate on > installs and upgrades. It prompts to use the "-f activate portname" > approach. This begins but never finishes; requiring a control-c to stop > it. > > Any ideas? > > Thanks. > > -- > ent- > XR > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ryandesign at macports.org Tue Dec 21 09:38:05 2021 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue, 21 Dec 2021 03:38:05 -0600 Subject: Failure to activate In-Reply-To: References: Message-ID: <5FA15100-3E34-496F-B167-A7316322AF43@macports.org> On Dec 20, 2021, at 09:12, dan d. wrote: > Recently I have increasingly begun to get the failure to activate on installs and upgrades. It prompts to use the "-f activate portname" > approach. This begins but never finishes; requiring a control-c to stop it. You usually should not force a port activation. You should usually choose the other alternative presented in the error message (deactivate the conflicting port). Please show us specifically which messages you are getting (which ports are giving the message, and which other ports they seem to be conflicting with). From dandunfee at gmail.com Tue Dec 21 18:56:14 2021 From: dandunfee at gmail.com (dan d.) Date: Tue, 21 Dec 2021 13:56:14 -0500 (EST) Subject: Failure to activate Message-ID: No. On Mon, 20 Dec 2021, Andrew Udvare wrote: > Do you have any kind of antivirus software running? > > On Mon, Dec 20, 2021, 10:12 dan d. wrote: > > > > > Recently I have increasingly begun to get the failure to activate on > > installs and upgrades. It prompts to use the "-f activate portname" > > approach. This begins but never finishes; requiring a control-c to stop > > it. > > > > Any ideas? > > > > Thanks. > > > > -- > > ent- > > XR > > > -- ent- XR From dandunfee at gmail.com Tue Dec 21 19:17:15 2021 From: dandunfee at gmail.com (dan d.) Date: Tue, 21 Dec 2021 14:17:15 -0500 (EST) Subject: Failure to activate Message-ID: <7a408ed5-abba-bdff-24c7-d8449258b0@gmail.com> Ok, I will do so the next time it happens. I don't recall seeing the "deactivate" prompt. On Tue, 21 Dec 2021, Ryan Schmidt wrote: > On Dec 20, 2021, at 09:12, dan d. wrote: > > > Recently I have increasingly begun to get the failure to activate on installs and upgrades. It prompts to use the "-f activate portname" > > approach. This begins but never finishes; requiring a control-c to stop it. > > You usually should not force a port activation. You should usually choose the other alternative presented in the error message (deactivate the conflicting port). > > Please show us specifically which messages you are getting (which ports are giving the message, and which other ports they seem to be conflicting with). > > > -- ent- XR From macintosh at mathiesen.info Tue Dec 21 19:42:17 2021 From: macintosh at mathiesen.info (Bjarne D Mathiesen) Date: Tue, 21 Dec 2021 20:42:17 +0100 Subject: ssh & ssh-agent conflict Message-ID: <35892f11-2549-de33-20db-476cecc11e16@mathiesen.info> Recently, I've gotten the exact same problem as described here : https://apple.stackexchange.com/questions/277479/openssh-hangs-at-rekey-after-134217728-blocks https://itectec.com/askdifferent/openssh-hangs-at-rekey-after-134217728-blocks/ and the work-around of setting SSH_AUTH_SOCK='ssh git at github.com' works as described BUT I'm at a loss as to which process messes ssh up :-( I don't have any running ssh-agent.plist anywhere I'm having this problem on both of my macmini1,1 10.6.8 macmini2,1 10.6.8 but not my MacPro5,1 They've all got openssh @8.8p1_2+kerberos5+xauth Any ideas as to how I can trouble-shoot this further ??? thanks, -- Bjarne D Mathiesen Kors?r ; Danmark ; Europa ----------------------------------------------------------------------- denne besked er skrevet i et totalt M$-frit milj? MacPro 2010 ; OpenCore + macOS 10.15.7 Catalina 2 x 3,46 GHz 6-Core Intel Xeon ; 256 GB 1333 MHz DDR3 ECC RDIMM ATI Radeon RX 590 8 GB From macintosh at mathiesen.info Tue Dec 21 21:09:36 2021 From: macintosh at mathiesen.info (Bjarne D Mathiesen) Date: Tue, 21 Dec 2021 22:09:36 +0100 Subject: ssh & ssh-agent conflict In-Reply-To: <35892f11-2549-de33-20db-476cecc11e16@mathiesen.info> References: <35892f11-2549-de33-20db-476cecc11e16@mathiesen.info> Message-ID: OK - I've gotten a bit further : When I took a look at env variables, I saw this: SSH_AUTH_SOCK=/tmp/launch-Mnqkqu/Listener #=> ls -l /tmp/launch-Mnqkqu/Listeners srwx------ 1 root wheel 0 20 Dec 03:11 launch-Mnqkqu/Listeners Any tips regarding how I can find out who has set this ? Q: does the MacPorts OpenSSH try to start an ssh-agent ? -- Bjarne D Mathiesen Kors?r ; Danmark ; Europa ----------------------------------------------------------------------- denne besked er skrevet i et totalt M$-frit milj? MacPro 2010 ; OpenCore + macOS 10.15.7 Catalina 2 x 3,46 GHz 6-Core Intel Xeon ; 256 GB 1333 MHz DDR3 ECC RDIMM ATI Radeon RX 590 8 GB From macintosh at mathiesen.info Tue Dec 21 22:51:03 2021 From: macintosh at mathiesen.info (Bjarne D Mathiesen) Date: Tue, 21 Dec 2021 23:51:03 +0100 Subject: ssh & ssh-agent conflict In-Reply-To: <35892f11-2549-de33-20db-476cecc11e16@mathiesen.info> References: <35892f11-2549-de33-20db-476cecc11e16@mathiesen.info> Message-ID: <76f201f8-1c90-ee31-acbf-0d83e732168a@mathiesen.info> further dectective work has given me : root at MiniWeb 22:41:05 /tmp #=> lsof | sed -En -e '1,1p' -e '/launch-Mnqkqu/p' COMMAND launchd PID 136 USER root FD 11u TYPE unix DEVICE 0x04fc6dd0 SIZE/OFF 0t0 NODE NAME /tmp/launch-Mnqkqu/Listeners so, it's something started by launchctl #=> launchctl list | grep 136 136 - com.apple.launchd.peruser.0 and it's apparently from LaunchAgents somewhere OK - /System/Library/LaunchAgents & org.openbsd.ssh-agent.plist & Console shows that it's trying to start it every 10 sec but it seems as if I can only get rid of it after re-login [thinking] because as the service isn't actually running it can't be administered #=> ll /usr/bin/ssh-agent ls: /usr/bin/ssh-agent: No such file or directory So, at some time this ssh-agent existed, but now it's disappeared somehow mysteriously ... kill -9 136 got rid of the re-spawning, but the SSH_AUTH_SOCK env variable is still set when opening a Terminal window/tab Seems as if I'll have to do an unset SSH_AUTH_SOCK whenever I'll use ssh until reboot and I've changed /usr/bin/ssh-agent to /opt/local/bin/ssh-agent in org.openbsd.ssh-agent.plist +--------+ | SOLVED | +--------+ -- Bjarne D Mathiesen Kors?r ; Danmark ; Europa ----------------------------------------------------------------------- denne besked er skrevet i et totalt M$-frit milj? MacPro 2010 ; OpenCore + macOS 10.15.7 Catalina 2 x 3,46 GHz 6-Core Intel Xeon ; 256 GB 1333 MHz DDR3 ECC RDIMM ATI Radeon RX 590 8 GB From ryandesign at macports.org Wed Dec 22 09:02:30 2021 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed, 22 Dec 2021 03:02:30 -0600 Subject: Failure to activate In-Reply-To: <7a408ed5-abba-bdff-24c7-d8449258b0@gmail.com> References: <7a408ed5-abba-bdff-24c7-d8449258b0@gmail.com> Message-ID: On Dec 21, 2021, at 13:17, dan d. wrote: > Ok, I will do so the next time it happens. I don't recall seeing the "deactivate" prompt. The message I thought you were referring to is: https://github.com/macports/macports-base/blob/master/src/registry2.0/portimage.tcl#L597 Image error: $file is being used by the active [$owner name] port. Please deactivate this port first, or use 'port -f activate [$port name]' to force the activation. From macintosh at mathiesen.info Wed Dec 22 09:46:44 2021 From: macintosh at mathiesen.info (Bjarne D Mathiesen) Date: Wed, 22 Dec 2021 10:46:44 +0100 Subject: ssh & ssh-agent conflict In-Reply-To: <35892f11-2549-de33-20db-476cecc11e16@mathiesen.info> References: <35892f11-2549-de33-20db-476cecc11e16@mathiesen.info> Message-ID: <461988fe-c970-a3ba-0693-7ce2e4c7f01e@mathiesen.info> So, one reboot later; & I've got : #=> ps axu | sed -En -e '1,1p' -e '/ssh/p' USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND root 110 0,0 0,0 2442336 372 ?? Ss 7:58am 0:00.00 sshd: /opt/local/sbin/sshd [listener] 0 of 10-100 startups root 255 0,0 0,1 2450756 2584 ?? S 8:06am 0:00.02 /opt/local/bin/ssh-agent -l & no issues -- Bjarne D Mathiesen Kors?r ; Danmark ; Europa ----------------------------------------------------------------------- denne besked er skrevet i et totalt M$-frit milj? MacPro 2010 ; OpenCore + macOS 10.15.7 Catalina 2 x 3,46 GHz 6-Core Intel Xeon ; 256 GB 1333 MHz DDR3 ECC RDIMM ATI Radeon RX 590 8 GB From maxim.abalenkov at gmail.com Tue Dec 28 14:01:04 2021 From: maxim.abalenkov at gmail.com (Maxim Abalenkov) Date: Tue, 28 Dec 2021 16:01:04 +0200 Subject: [numpy @ bigsur: multithreading] Message-ID: <0A11C310-861D-47D1-834A-BC0873CE31F0@gmail.com> Dear all, I?m looking for guidance please. I would like to make sure, that I use all eight of my CPU cores, when I run Python?s 3.9.9 NumPy on my macOS BigSur 12.1. When I run my NumPy code, I see in ?htop?, that only one ?python? process is running and the core utilisation is 20?25%. I remember in the past, stock MacPorts NumPy installation would use Apple?s Accelerate library including the multithreaded BLAS and LAPACK (https://developer.apple.com/documentation/accelerate). As I understand this is no longer the case. I run Python code using a virtual environment located under /opt/venv/zipfstime/lib/python3.9/site-packages/numpy/core When I change there and issue otool -L _multiarray_umath.cpython-39-darwin.so _multiarray_umath.cpython-39-darwin.so: @loader_path/../.dylibs/libopenblas.0.dylib (compatibility version 0.0.0, current version 0.0.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1281.100.1) In other words, NumPy relies on openBLAS. Command `port variants openblas` returns OpenBLAS has the variants: g95: Build using the g95 Fortran compiler * conflicts with gcc10 gcc11 gcc8 gcc9 gccdevel gcc10: Build using the MacPorts gcc 10 compiler * conflicts with g95 g95 gcc11 gcc8 gcc9 gccdevel [+]gcc11: Build using the MacPorts gcc 11 compiler * conflicts with g95 g95 gcc10 gcc8 gcc9 gccdevel gcc8: Build using the MacPorts gcc 8 compiler * conflicts with g95 g95 gcc10 gcc11 gcc9 gccdevel gcc9: Build using the MacPorts gcc 9 compiler * conflicts with g95 g95 gcc10 gcc11 gcc8 gccdevel gccdevel: Build using the MacPorts gcc devel compiler * conflicts with g95 g95 gcc10 gcc11 gcc8 gcc9 [+]lapack: Add Lapack/CLapack support to the library native: Force compilation on machine to get fully optimized library universal: Build for multiple architectures I tried installing the ?native? variant of OpenBLAS port with `sudo port install openblas +native` and setting the environment variable `OMP_NUM_THREADS=8`, but I didn?t see any improvement when running my Python code. I would welcome your help and guidance on this subject. ? Best wishes, Maxim From jmr at macports.org Wed Dec 29 11:33:36 2021 From: jmr at macports.org (Joshua Root) Date: Wed, 29 Dec 2021 22:33:36 +1100 Subject: [numpy @ bigsur: multithreading] In-Reply-To: <0A11C310-861D-47D1-834A-BC0873CE31F0@gmail.com> References: <0A11C310-861D-47D1-834A-BC0873CE31F0@gmail.com> Message-ID: Maxim Abalenkov wrote: > Dear all, > > I?m looking for guidance please. I would like to make sure, that I use all eight of my CPU cores, when I run Python?s 3.9.9 NumPy on my macOS BigSur 12.1. When I run my NumPy code, I see in ?htop?, that only one ?python? process is running and the core utilisation is 20?25%. I remember in the past, stock MacPorts NumPy installation would use Apple?s Accelerate library including the multithreaded BLAS and LAPACK (https://developer.apple.com/documentation/accelerate). As I understand this is no longer the case. > > I run Python code using a virtual environment located under > > /opt/venv/zipfstime/lib/python3.9/site-packages/numpy/core > > When I change there and issue > > otool -L _multiarray_umath.cpython-39-darwin.so > > _multiarray_umath.cpython-39-darwin.so: > @loader_path/../.dylibs/libopenblas.0.dylib (compatibility version 0.0.0, current version 0.0.0) > /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1281.100.1) > > In other words, NumPy relies on openBLAS. Command `port variants openblas` returns > > OpenBLAS has the variants: > g95: Build using the g95 Fortran compiler > * conflicts with gcc10 gcc11 gcc8 gcc9 gccdevel > gcc10: Build using the MacPorts gcc 10 compiler > * conflicts with g95 g95 gcc11 gcc8 gcc9 gccdevel > [+]gcc11: Build using the MacPorts gcc 11 compiler > * conflicts with g95 g95 gcc10 gcc8 gcc9 gccdevel > gcc8: Build using the MacPorts gcc 8 compiler > * conflicts with g95 g95 gcc10 gcc11 gcc9 gccdevel > gcc9: Build using the MacPorts gcc 9 compiler > * conflicts with g95 g95 gcc10 gcc11 gcc8 gccdevel > gccdevel: Build using the MacPorts gcc devel compiler > * conflicts with g95 g95 gcc10 gcc11 gcc8 gcc9 > [+]lapack: Add Lapack/CLapack support to the library > native: Force compilation on machine to get fully optimized library > universal: Build for multiple architectures > > I tried installing the ?native? variant of OpenBLAS port with `sudo port install openblas +native` and setting the environment variable `OMP_NUM_THREADS=8`, but I didn?t see any improvement when running my Python code. I would welcome your help and guidance on this subject. I'm using py39-numpy with default variants: % port installed py39-numpy openblas The following ports are currently installed: ? OpenBLAS @0.3.19_0+gcc11+lapack (active) ? py39-numpy @1.21.5_1+gfortran+openblas (active) I see Python using around 600% CPU on my 6-core machine when running this basic benchmark script: If you try that and see how many cores it uses, that will at least tell you if there is something different about your code. If it doesn't use all the cores for you, there are some other environment variables that OpenBLAS looks at that you could check: - Josh -------------- next part -------------- An HTML attachment was scrubbed... URL: