Re: boost176 + py311 vs +py312

[Christopher Jones]

Forcing things is never really the best way to go.

In this case vigra just needs to have py312 support added.

 https://github.com/macports/macports-ports/pull/22655

Chris

> On 12 Feb 2024, at 6:42 pm, Lenore Horner  wrote:
> 
> I'd like to have both TexLive and Hugin-app installed.  However, TexLive-bin 
> needs Poppler which installed  boost176 +py312 while Hugin-app needs vigra 
> which demands boost176 +py311.  I'm actually not sure why Poppler installed 
> +py312 because it's library dependency lists python311.  Can I force 
> uninstall Boost176, let vigra install it the way it wants and then expect 
> Poppler to work or will I need to rebuild Poppler?
> 
> TIA,
> Lenore



smime.p7s
Description: S/MIME cryptographic signature

Re: Quartz no longer launching when an X application is invoked

[Christopher Jones]

> On 1 Dec 2023, at 6:52 am, Kenneth Wolcott  wrote:
> 
> Hi;
> 
>  So what is the proper way for X to be started?


If properly configured the X11 server will automatically start on demand. You 
really should never need to manually start it.

> 
>  Do I need to manually create a launch entry like I have for the
> emacs server?  If so, what is the invocation? What is being invoked?
> xorg-server?
> 
>  Now that the DISPLAY is null, invoking xpdf fails even after an open
> -a /Applications/MacPorts/X11.app, complaining about the DISPLAY
> variable setting

Having DISPLAY null is as bad as setting it to :0.0

It should look something like what I posted before

$ echo $DISPLAY
/private/tmp/com.apple.launchd.TwDg8TRtvI/org.macosforge.xquartz:0

This is the launchd socket, the magic if you like, that triggers it to be 
started on demand.

Please try as I posted in my first mail completeing uninstalling org-server, 
then re-install it. Then log out and back in again (this is important) and then 
see. If it is still null then you have something else setting that and you need 
to figure out what.

Chris

> 
> Thanks,
> Ken
> 
> On Thu, Nov 30, 2023 at 10:47 PM Kenneth Wolcott
>  wrote:
>> 
>> Hi Ryan;
>> 
>>  It was defined in ~/.zprofile and created by MacPorts in 2021 :-)  I
>> commented it out. I'll source the .zprofile and see what happens.
>> 
>> Thanks,
>> Ken
>> 
>> On Thu, Nov 30, 2023 at 10:23 PM Ryan Schmidt  
>> wrote:
>>> 
>>> On Nov 30, 2023, at 16:01, Kenneth Wolcott wrote:
 
 3. My DISPLAY environment variable is set to ":0";
 I do not know where this variable is not being set properly or is
 being overridden.
>>> 
>>> You need to figure out where DISPLAY=:0 is being set, and remove the code 
>>> that does so. It's probably in your shell startup file. Depending on which 
>>> shell you use, there are many possible names for startup files in your home 
>>> directory: .zshrc, .zprofile, .bashrc, .bash_profile, etc.
>>> 
>>> Setting DISPLAY=:0 was correct in Mac OS X 10.4 and earlier but it has not 
>>> been correct since Mac OS X 10.5.

Re: Clang 17.0.3 fails to build on Sonoma.

[Christopher Jones]

Sending a 31MB log to a mailing list is not a great idea..

Please open a trac ticket.

 https://trac.macports.org/

Chris

> On 20 Oct 2023, at 10:11 pm, doa via macports-users 
>  wrote:
> 
> This port was recently outdated, so this seems rather strange. Attached is 
> the log I received.
> 
> 
> 
> Thank you.
> 
> Diego Vicioso.
> 
> Email… viciosodi...@icloud.com 
> Click to Download
>  
> main.log
> 31.6 MB

Re: problem with py311-scipy on M1 MacBook Pro

[Christopher Jones]

boost176 not building is a different issue to the one I was talking about, 
which was the linker issue affecting a number of builds. So no, I don’t 
necessarily expect Xcode 15.1 to help there.

Is there a ticket open with your problem with boost ? If not please open one.

Chris

> On 20 Oct 2023, at 5:04 pm, Frank Schima  wrote:
> 
> Correct. I installed the beta CLT (as I mentioned). 
> 
> No joy. boost176 does not build. 
> 
> 
>> On Oct 20, 2023, at 2:26 AM, Christopher Jones  
>> wrote:
>> 
>> 
>> Do you also have CLT installed and updated to 15.1 as well (if there is a 
>> version) ?
>> 
>> If you still have 15.0 CLT then likely it won’t help.
>> 
>>> On 20 Oct 2023, at 1:23 am, Frank Schima  wrote:
>>> 
>>> py311-scipy still does not build for me with the latest Xcode 15.1 beta and 
>>> associated CLT. I can only hope I’m doing something wrong. 
>>> 
>>> I cannot even get past boost176 which is required. I modified my local 
>>> Portfile to use boost181 (which does build) but py311-scipy still does not 
>>> build. 
>>> 
>>> 
>>> 
>>>> On Oct 19, 2023, at 1:11 PM, Christopher Jones  
>>>> wrote:
>>>> 
>>>> The fix is in Xcode 15.1, not 15.0.1
>>>> 
>>>> Chris
>>>> 
>>>>> On 19 Oct 2023, at 5:27 pm, Jim Secan  wrote:
>>>>> 
>>>>> I see that there’s an Xcode 15.0.1 released yesterday.  Anyone tried that?
>>>>> 
>>>>> Jim
>>>>> Seattle, WA
>>>>> 
>>>>>> On 10/19/2023, at 8:00 AM, Chris Jones  wrote:
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> On 19/10/2023 3:59 pm, Chris Jones wrote:
>>>>>>> On 19/10/2023 3:09 pm, Artemio González López via macports-users wrote:
>>>>>>>> I just realized that my problem could exactly be the one reported in 
>>>>>>>> ticket #68329 (py311-scipy @1.10.1_0+gfortran+openblas not building on 
>>>>>>>> Sonoma apple silicon). Indeed, I just spotted the following lines in 
>>>>>>>> my main.log:
>>>>>>>> 
>>>>>>>> :info:build ld: duplicate LC_RPATH '/opt/local/lib/libgcc' in 
>>>>>>>> '/opt/local/lib/libopenblas-r1.dylib'
>>>>>>>> :info:build clang: error: linker command failed with exit code 1 (use 
>>>>>>>> -v to see invocation)
>>>>>>>> 
>>>>>>>> Short of waiting for Apple to release XCode 15.1, is there any quick 
>>>>>>>> fix for this?
>>>>>>> The canocial fix is to tell the build to use the classic linker option. 
>>>>>>> 'Well behaved' builds will respect the following setting in the Portfile
>>>>>>> configure.ldflags-append  -Wl,-ld_classic
>>>>>>> This has worked for me in a few places, like the root6 port. I did 
>>>>>>> actually try it in py-scipy and there it did not work, and nor did a 
>>>>>>> handful of other tricks I have to get the build to use a certain linker.
>>>>>>> In my experience python based builds are not that well behaved when it 
>>>>>>> comes to things like respecting the macports build flags...
>>>>>>> At this point I am in the 'wait for Xcode 15.1' camp. Usually the first 
>>>>>>> X.1 OS release comes along relatively soon after the initial X.0 
>>>>>>> release, so I would anticipate it relatively soon, most likely.
>>>>>> 
>>>>>> b.t.w. If it is urgent for you, there is I believe a beta version of 
>>>>>> Xcode 15.1 available you could try. Its not the urgent for me so I am 
>>>>>> just waiting for it to become public..
>>>>>> 
>>>>>>> cheers Chris
>>>>> 
>>>> 
>>> 
>> 
> 

Re: problem with py311-scipy on M1 MacBook Pro

[Christopher Jones]

Do you also have CLT installed and updated to 15.1 as well (if there is a 
version) ?

If you still have 15.0 CLT then likely it won’t help.

> On 20 Oct 2023, at 1:23 am, Frank Schima  wrote:
> 
> py311-scipy still does not build for me with the latest Xcode 15.1 beta and 
> associated CLT. I can only hope I’m doing something wrong. 
> 
> I cannot even get past boost176 which is required. I modified my local 
> Portfile to use boost181 (which does build) but py311-scipy still does not 
> build. 
> 
> 
> 
>> On Oct 19, 2023, at 1:11 PM, Christopher Jones  
>> wrote:
>> 
>> The fix is in Xcode 15.1, not 15.0.1
>> 
>> Chris
>> 
>>> On 19 Oct 2023, at 5:27 pm, Jim Secan  wrote:
>>> 
>>> I see that there’s an Xcode 15.0.1 released yesterday.  Anyone tried that?
>>> 
>>> Jim
>>> Seattle, WA
>>> 
>>>> On 10/19/2023, at 8:00 AM, Chris Jones  wrote:
>>>> 
>>>> 
>>>> 
>>>> On 19/10/2023 3:59 pm, Chris Jones wrote:
>>>>> On 19/10/2023 3:09 pm, Artemio González López via macports-users wrote:
>>>>>> I just realized that my problem could exactly be the one reported in 
>>>>>> ticket #68329 (py311-scipy @1.10.1_0+gfortran+openblas not building on 
>>>>>> Sonoma apple silicon). Indeed, I just spotted the following lines in my 
>>>>>> main.log:
>>>>>> 
>>>>>> :info:build ld: duplicate LC_RPATH '/opt/local/lib/libgcc' in 
>>>>>> '/opt/local/lib/libopenblas-r1.dylib'
>>>>>> :info:build clang: error: linker command failed with exit code 1 (use -v 
>>>>>> to see invocation)
>>>>>> 
>>>>>> Short of waiting for Apple to release XCode 15.1, is there any quick fix 
>>>>>> for this?
>>>>> The canocial fix is to tell the build to use the classic linker option. 
>>>>> 'Well behaved' builds will respect the following setting in the Portfile
>>>>> configure.ldflags-append  -Wl,-ld_classic
>>>>> This has worked for me in a few places, like the root6 port. I did 
>>>>> actually try it in py-scipy and there it did not work, and nor did a 
>>>>> handful of other tricks I have to get the build to use a certain linker.
>>>>> In my experience python based builds are not that well behaved when it 
>>>>> comes to things like respecting the macports build flags...
>>>>> At this point I am in the 'wait for Xcode 15.1' camp. Usually the first 
>>>>> X.1 OS release comes along relatively soon after the initial X.0 release, 
>>>>> so I would anticipate it relatively soon, most likely.
>>>> 
>>>> b.t.w. If it is urgent for you, there is I believe a beta version of Xcode 
>>>> 15.1 available you could try. Its not the urgent for me so I am just 
>>>> waiting for it to become public..
>>>> 
>>>>> cheers Chris
>>> 
>> 
> 

Re: problem with py311-scipy on M1 MacBook Pro

[Christopher Jones]

The fix is in Xcode 15.1, not 15.0.1

Chris

> On 19 Oct 2023, at 5:27 pm, Jim Secan  wrote:
> 
> I see that there’s an Xcode 15.0.1 released yesterday.  Anyone tried that?
> 
> Jim
> Seattle, WA
> 
>> On 10/19/2023, at 8:00 AM, Chris Jones  wrote:
>> 
>> 
>> 
>> On 19/10/2023 3:59 pm, Chris Jones wrote:
>>> On 19/10/2023 3:09 pm, Artemio González López via macports-users wrote:
 I just realized that my problem could exactly be the one reported in 
 ticket #68329 (py311-scipy @1.10.1_0+gfortran+openblas not building on 
 Sonoma apple silicon). Indeed, I just spotted the following lines in my 
 main.log:
 
 :info:build ld: duplicate LC_RPATH '/opt/local/lib/libgcc' in 
 '/opt/local/lib/libopenblas-r1.dylib'
 :info:build clang: error: linker command failed with exit code 1 (use -v 
 to see invocation)
 
 Short of waiting for Apple to release XCode 15.1, is there any quick fix 
 for this?
>>> The canocial fix is to tell the build to use the classic linker option. 
>>> 'Well behaved' builds will respect the following setting in the Portfile
>>> configure.ldflags-append  -Wl,-ld_classic
>>> This has worked for me in a few places, like the root6 port. I did actually 
>>> try it in py-scipy and there it did not work, and nor did a handful of 
>>> other tricks I have to get the build to use a certain linker.
>>> In my experience python based builds are not that well behaved when it 
>>> comes to things like respecting the macports build flags...
>>> At this point I am in the 'wait for Xcode 15.1' camp. Usually the first X.1 
>>> OS release comes along relatively soon after the initial X.0 release, so I 
>>> would anticipate it relatively soon, most likely.
>> 
>> b.t.w. If it is urgent for you, there is I believe a beta version of Xcode 
>> 15.1 available you could try. Its not the urgent for me so I am just waiting 
>> for it to become public..
>> 
>>> cheers Chris
> 

Re: Help me understand dependents of libgcc-devel vs gcc13?

[Christopher Jones]

> 
> Clever!
> 
> One question of mine which did not get answered: "Q: why are ports like 
> fftw-3 reported as dependents of port libgcc-devel? I don't see anything in 
> fftw-3's portfile[2] which mentions port libgcc-devel, or indeed any gcc or 
> libgcc, are dependencies.
> 
> "I suspect there is some behind-the-scenes dependency addition. Maybe it is 
> behind the scenes because so many ports depend on C or C++ compilers. Where 
> is this dependence addition documented? How should I as a user think of it?"


I a lot of ports gain this via the compilers PortGroup. It’s often used to for 
instance select a gcc compiler for fortran, as Xcode does not provide one.

 
https://github.com/macports/macports-ports/blob/master/_resources/port1.0/group/compilers-1.0.tcl

Chris

> 
> Best regards,
> —Jim DeLaHunt
> 

Re: Segfault 11 of sshfs

[Christopher Jones]

> On 14 Oct 2023, at 10:39 am, Christoph Kukulies via macports-users 
>  wrote:
> 
> Trying to use sshfs under BigSur and errouneously typing an imcomplete 
> command:
> 
> $ sshfs foobar.de :/home/foo
> Segmentation fault: 11
> $ 
> 
> leads to a Segmentation fault:  11.
> 
> Just would like to bring this to the maintainers' attention.

Which sending a mail to this list is not going to g to necessarily do. Please 
open a trac ticket.

> 
> --
> Christoph
> 

Re: Xcode 15 issues - my temporary workaround

[Christopher Jones]

Hi,

Thanks. We will need to see how widespread problems are due to this, but we 
might need to. at least temporarily, set this as the default in some central 
place if it ends up affecting a lot of ports. 

Just to note, a potentially more convenient way to force the legacy linker is 
via the environment variable

OTHER_LDFLAGS=-Wl,-ld_classic

as that can be set, as appropriate, and thus avoids the need to ensure build 
options get passed.

https://developer.apple.com/documentation/xcode-release-notes/xcode-15-release-notes#Linking
Xcode 15 Release Notes | Apple Developer Documentation
developer.apple.com

At the moment most issues see isolated to places where gcc, or binaries built 
with gcc are used. My guess is eventually GCC will have to adapt to support the 
new linker.

Chris


> On 25 Sep 2023, at 11:10 pm, CC  wrote:
> 
> Hi -
> 
> Instead of reverting to Xcode 14, I have had success (so far) by forcing the 
> linker to use the "classic" version.  Xcode 15 switched the default to 
> Apple's newer "prime" linker.
> 
> what I did --
> - start with a clean slate (mv /opt/local /opt/local.0; mv 
> /Applications/MacPorts /Applications/MacPorts.0)
> - install macports from macports-base repo
> - "port install ld64" (which should install ld64-xcode)
> - edit /opt/local/bin/ld to add "-ld_classic" option (see below)
> 
> "libgcc12" was my test port and it worked after I did the above.  I hope this 
> helps others while we wait for someone with more knowledge to dig deeper into 
> issues with the new linker.

Re: g++ errors after upgrading XCode Command Line tools to version 15.0.0.0.1.1694021235

[Christopher Jones]

> 
> Workaround, for now, is to not use gcc to build C++ sources. Clang is anyway 
> the default compiler on Mac’s, and is what MacPorts uses for the vast 
> majority of ports, so if you can use clang++ (either Xcode or MacPorts own 
> builds). Both these are still fine.

Or, of course, downgrade your Xcode/CLT back to the 14.x versions.

Re: g++ errors after upgrading XCode Command Line tools to version 15.0.0.0.1.1694021235

[Christopher Jones]

> On 22 Sep 2023, at 1:27 pm, Christopher Jones  
> wrote:
> 
> 
> 
>> On 22 Sep 2023, at 1:09 pm, Carlo Tambuatco  wrote:
>> 
>> macOS 13.5.2
>> package-id: com.apple.pkg.CLTools_Executables
>> version: 15.0.0.0.1.1694021235
>> 
>> My g++-mp-12 (from gcc version 12) install on macports started giving me 
>> these errors compiling 
>> C++ programs after upgrading my XCode command line tools a few days ago.
>> 
>> Is this something macports will address in a future update?
> 
> This indeed looks like an issue introduced with the recent Xcode/CLT update.
> 
> At this time I don’t think anyone can say how it will get addressed, or show 
> long that might take, as it needs to be determined if this is an bug on 
> Apple’s side, in Xcode/CLT, a bug in gcc, or just some incompatibility 
> upstream gcc now needs to address.
> 
> It could also be an issue introduced with how MacPorts builds GCC. I have my 
> doubts that this could be the case, given how it just appeared with an Xcode 
> update, but it cannot be ruled out right now.

A quick web search yields a number of reports of this, e.g.

https://discussions.apple.com/thread/255137447

so this is I think nothing to do with the MacPorts packing of GCC.

Whether its GCC or Xcode at fault remains to be seen.

> 
>> Do I need to reinstall/recompile 
>> all of macports?
> 
> I doubt that would help.
> 
> Workaround, for now, is to not use gcc to build C++ sources. Clang is anyway 
> the default compiler on Mac’s, and is what MacPorts uses for the vast 
> majority of ports, so if you can use clang++ (either Xcode or MacPorts own 
> builds). Both these are still fine.
> 
> Chris
> 
>> 
>> -macosx_version_min has been renamed to -macos_version_min
>> 0  0x106e2df43  __assert_rtn + 64
>> 1  0x106d2ff43  ld::AtomPlacement::findAtom(unsigned char, unsigned long 
>> long, ld::AtomPlacement::AtomLoc const*&, long long&) const + 1411
>> 2  0x106d4c431  ld::InputFiles::SliceParser::parseObjectFile(mach_o::Header 
>> const*) const + 19745
>> 3  0x106d5cb71  ld::InputFiles::parseAllFiles(void (ld::AtomFile const*) 
>> block_pointer)::$_7::operator()(unsigned long, ld::FileInfo const&) const + 
>> 657
>> 4  0x7ff80f31d066  _dispatch_client_callout2 + 8
>> 5  0x7ff80f33018f  _dispatch_apply_invoke_and_wait + 213
>> 6  0x7ff80f32f692  _dispatch_apply_with_attr_f + 1207
>> 7  0x7ff80f32f847  dispatch_apply + 45
>> 8  0x106df5972  ld::AtomFileConsolidator::parseFiles(bool) + 370
>> 9  0x106d7cd67  main + 12263
>> ld: Assertion failed: (resultIndex < sectData.atoms.size()), function 
>> findAtom, file Relocations.cpp, line 1336.
>> collect2: error: ld returned 1 exit status
> 

Re: g++ errors after upgrading XCode Command Line tools to version 15.0.0.0.1.1694021235

[Christopher Jones]

> On 22 Sep 2023, at 1:09 pm, Carlo Tambuatco  wrote:
> 
> macOS 13.5.2
> package-id: com.apple.pkg.CLTools_Executables
> version: 15.0.0.0.1.1694021235
> 
> My g++-mp-12 (from gcc version 12) install on macports started giving me 
> these errors compiling 
> C++ programs after upgrading my XCode command line tools a few days ago.
> 
> Is this something macports will address in a future update?

This indeed looks like an issue introduced with the recent Xcode/CLT update.

At this time I don’t think anyone can say how it will get addressed, or show 
long that might take, as it needs to be determined if this is an bug on Apple’s 
side, in Xcode/CLT, a bug in gcc, or just some incompatibility upstream gcc now 
needs to address.

It could also be an issue introduced with how MacPorts builds GCC. I have my 
doubts that this could be the case, given how it just appeared with an Xcode 
update, but it cannot be ruled out right now.

> Do I need to reinstall/recompile 
> all of macports?

I doubt that would help.

Workaround, for now, is to not use gcc to build C++ sources. Clang is anyway 
the default compiler on Mac’s, and is what MacPorts uses for the vast majority 
of ports, so if you can use clang++ (either Xcode or MacPorts own builds). Both 
these are still fine.

Chris

> 
> -macosx_version_min has been renamed to -macos_version_min
> 0  0x106e2df43  __assert_rtn + 64
> 1  0x106d2ff43  ld::AtomPlacement::findAtom(unsigned char, unsigned long 
> long, ld::AtomPlacement::AtomLoc const*&, long long&) const + 1411
> 2  0x106d4c431  ld::InputFiles::SliceParser::parseObjectFile(mach_o::Header 
> const*) const + 19745
> 3  0x106d5cb71  ld::InputFiles::parseAllFiles(void (ld::AtomFile const*) 
> block_pointer)::$_7::operator()(unsigned long, ld::FileInfo const&) const + 
> 657
> 4  0x7ff80f31d066  _dispatch_client_callout2 + 8
> 5  0x7ff80f33018f  _dispatch_apply_invoke_and_wait + 213
> 6  0x7ff80f32f692  _dispatch_apply_with_attr_f + 1207
> 7  0x7ff80f32f847  dispatch_apply + 45
> 8  0x106df5972  ld::AtomFileConsolidator::parseFiles(bool) + 370
> 9  0x106d7cd67  main + 12263
> ld: Assertion failed: (resultIndex < sectData.atoms.size()), function 
> findAtom, file Relocations.cpp, line 1336.
> collect2: error: ld returned 1 exit status

Re: ports that are outdated but cannot be upgraded.

[Christopher Jones]

> On 30 Mar 2023, at 2:28 am, Kenneth Wolcott  wrote:
> 
> Not too bad.  The uninstall and install from source sequence completed
> fairly quickly.

Chances are you did not need to build from source, as this is only required for 
specific reasons, like if you pick non-default variants (which the commands you 
where given do not) or if you are using a non-default installation prefix.

Chris

> 
> Thanks,
> Ken
> 
> On Wed, Mar 29, 2023 at 10:12 AM Bill Cole
>  wrote:
>> 
>> On 2023-03-29 at 07:49:28 UTC-0400 (Wed, 29 Mar 2023 12:49:28 +0100)
>> Christopher Jones 
>> is rumored to have said:
>> 
>>> Hio,
>>> 
>>> Your problem is precisely what it says at the end
>>> 
>>>> Error: Failed to configure libtorrent-rasterbar: boost176 must be
>>>> installed with +python311.
>>> 
>>> you will likely have it installed with a different python version
>>> selected, and port respects this as your ‘choice’. You need to
>>> uninstall boost176 and reinstall it with the new default variants.
>> 
>> I agree 100%. Simple commands:
>> 
>> port uninstall boost176
>> port install boost176
>> 
>> Beware: building Boost from source is painfully slow.
>> 
>> 
>> --
>> Bill Cole
>> b...@scconsult.com or billc...@apache.org
>> (AKA @grumpybozo and many *@billmail.scconsult.com addresses)
>> Not Currently Available For Hire

Re: ports that are outdated but cannot be upgraded.

[Christopher Jones]

Hio,

Your problem is precisely what it says at the end

> Error: Failed to configure libtorrent-rasterbar: boost176 must be
> installed with +python311.

you will likely have it installed with a different python version selected, and 
port respects this as your ‘choice’. You need to uninstall boost176 and 
reinstall it with the new default variants.

Chris

> On 29 Mar 2023, at 4:26 am, Kenneth Wolcott  wrote:
> 
> Hi Bill;
> 
>  I ran selfupdate again.
> 
>  Then port outdated
> 
>  Then sudo port -v -s upgrade outdated
> 
>  Now I get the message:
> 
> --->  Scanning binaries for linking errors
> Could not open /opt/local/libexec/boost/1.76/lib/libboost_python311-mt.dylib:
> Error opening or reading file (referenced from
> /opt/local/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/libtorrent.cpython-311-darwin.so)
> --->  Found 1 broken file, matching files to ports
> --->  Found 1 broken port, determining rebuild order
> You can always run 'port rev-upgrade' again to fix errors.
> The following ports will be rebuilt: libtorrent-rasterbar @2.0.8+python311
> Continue? [Y/n]: n
> ~: sudo port rev-upgrade
> --->  Scanning binaries for linking errors
> --->  Found 1 broken file, matching files to ports
> --->  Found 1 broken port, determining rebuild order
> You can always run 'port rev-upgrade' again to fix errors.
> The following ports will be rebuilt: libtorrent-rasterbar @2.0.8+python311
> Continue? [Y/n]: y
> --->  Computing dependencies for libtorrent-rasterbar
> --->  Cleaning libtorrent-rasterbar
> --->  Scanning binaries for linking errors
> --->  Found 1 broken file, matching files to ports
> --->  Found 1 broken port, determining rebuild order
> --->  Rebuilding in order
> libtorrent-rasterbar @2.0.8_1+python311
> --->  Computing dependencies for libtorrent-rasterbar
> --->  Fetching distfiles for libtorrent-rasterbar
> --->  Verifying checksums for libtorrent-rasterbar
> --->  Extracting libtorrent-rasterbar
> --->  Applying patches to libtorrent-rasterbar
> --->  Configuring libtorrent-rasterbar
> Error: Failed to configure libtorrent-rasterbar: boost176 must be
> installed with +python311.
> Error: See 
> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_net_libtorrent-rasterbar/libtorrent-rasterbar/main.log
> for details.
> Error: rev-upgrade failed: Error rebuilding libtorrent-rasterbar
> Error: Follow https://guide.macports.org/#project.tickets if you
> believe there is a bug.
> 
> On Tue, Mar 28, 2023 at 12:48 PM Kenneth Wolcott
>  wrote:
>> 
>> Hi Bill;
>> 
>>  I've tried that, but the problem remains even if I do respond affirmatively.
>> 
>>  I think that there's a root problem here, but I just can't grasp
>> what it is precisely.
>> 
>> Thanks,
>> Ken
>> 
>> On Tue, Mar 28, 2023 at 12:41 PM Bill Cole
>>  wrote:
>>> 
>>> On 2023-03-28 at 15:03:48 UTC-0400 (Tue, 28 Mar 2023 12:03:48 -0700)
>>> Kenneth Wolcott 
>>> is rumored to have said:
>>> 
 HI;
 
  I ran a selfupdate successfully today.
 
 Then "sudo port -v -s upgrade outdated" seemed successful.
 
 But then:
 
 --->  Scanning binaries for linking errors
 Could not open
 /opt/local/libexec/boost/1.76/lib/libboost_python311-mt.dylib:
 Error opening or reading file (referenced from
 /opt/local/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/libtorrent.cpython-311-darwin.so)
 --->  Found 1 broken file, matching files to ports
 --->  Found 1 broken port, determining rebuild order
 You can always run 'port rev-upgrade' again to fix errors.
 The following ports will be rebuilt: libtorrent-rasterbar
 @2.0.8+python311
 Continue? [Y/n]: n
 ~: port diagnose
 [nothing returned]
 port outdated
 No installed ports are outdated.
 
 So, this still seems less than ideal.
>>> 
>>> It seems to me that the right answer to rev-upgrade's "Continue?" prompt
>>> should always be "y" but I could be wrong.
>>> 
>>> --
>>> Bill Cole
>>> b...@scconsult.com or billc...@apache.org
>>> (AKA @grumpybozo and many *@billmail.scconsult.com addresses)
>>> Not Currently Available For Hire

Re: Installing Grace on Ventura fails due to llvm-10 configure failure: command execution failed

[Christopher Jones]

That now shows a different error to what you previously reported. It is now a 
failure when configuring grace

Please check for an open trac ticket for the error you see, and if not present 
open one

https://trac.macports.org/wiki/Tickets

> On 16 Nov 2022, at 10:06 am, Vahid Askarpour  wrote:
> 
> Please see the attached transcript.
> 
> 
> 
> > On Nov 16, 2022, at 6:00 AM, Christopher Jones  
> > wrote:
> > 
> > CAUTION: The Sender of this email is not from within Dalhousie.
> > 
> > There is no indication below as to why your system is trying to build 
> > llvm-10 as part of installing grace, it does not appear in the dips tree
> > 
> > please run
> > 
> > sudo port clean grace
> > sudo port -d configure grace
> > 
> > and post the complete transcript of what you get back.
> > 
> >> On 16 Nov 2022, at 9:53 am, Vahid Askarpour  wrote:
> >> 
> >> Hi Chris,
> >> 
> >> The port rdeps grace command results in
> >> 
> >> The following ports are dependencies of grace @5.1.25_5:
> >> openmotif
> >>  pkgconfig
> >>libiconv
> >>  gperf
> >>  xbitmaps
> >>  bison
> >>xz
> >>  gettext
> >>diffutils-for-muniversal
> >>libtextstyle
> >>  ncurses
> >>gettext-runtime
> >>gettext-tools-libs
> >>m4
> >>bison-runtime
> >>  flex
> >>lzip
> >>  libjpeg-turbo
> >>cmake
> >>  libcxx
> >>  curl
> >>brotli
> >>  cmake-bootstrap
> >>libidn2
> >>  libunistring
> >>autoconf
> >>automake
> >>libtool
> >>libpsl
> >>  python310
> >>bzip2
> >>expat
> >>libedit
> >>libffi
> >>  expect
> >>tcl
> >>  dejagnu
> >>openssl
> >>  openssl3
> >>zlib
> >>sqlite3
> >>python_select
> >>python3_select
> >>zstd
> >>  lz4
> >>nghttp2
> >>curl-ca-bundle
> >>  unzip
> >>  perl5
> >>perl5.34
> >>  db48
> >>  gdbm
> >>readline
> >>  libarchive
> >>libxml2
> >>  icu
> >>lzo2
> >>libb2
> >>  libuv
> >>nasm
> >>  libpng
> >>  xorg-libsm
> >>xorg-xtrans
> >>xorg-libice
> >>  xorg-xorgproto
> >>  xorg-libXext
> >>xorg-util-macros
> >>xorg-libX11
> >>  xorg-libXdmcp
> >>  xorg-libXau
> >>  xorg-libxcb
> >>xorg-xcb-proto
> >>xorg-libpthread-stubs
> >>  Xft2
> >>xrender
> >>freetype
> >>fontconfig
> >>  ossp-uuid
> >>  xorg-libXmu
> >>xorg-libXt
> >>  xorg-libXp
> >> pdflib
> >> xpm
> >> openbrowser
> >>  p5.34-mac-propertylist
> >>p5.34-xml-entities
> >>  p5.34-module-build
> >>p5.34-cpan-meta-yaml
> >>p5.34-cpan-meta
> >>  p5.34-cpan-meta-requirements
> >>  p5.34-encode
> >>  p5.34-scalar-list-utils
> >>  p5.34-version
> >>p5.34-inc-latest
> >>p5.34-module-metadata
> >>p5.34-perl-ostype
> >>p5.34-podlators
> >>  p5.34-pod-simple
> >>p5.34-pod-escapes
> >>  p5.34-html-parser
> >>p5.34-html-tagset
> >>p5.34-http-message
> >>  p5.34-test-needs
> >>  p5.34-test-simple
> >>  p5.34-try-tiny
> >>p5.34-capture-tiny
> >>p5.34-sub-name
> >>  p5.34-devel-checkbin
> >>p5.34-extutils-makemaker
> >>  p5.34-extutils-manifest
> >>  p5.34-clone
> >>p5.34-b-cow
> >>  p5.34-xsloader
> >>  p5.34-compress-raw-bzip2
> >>p5.34-test-cpan-meta
> >>p5.34-test-c

Re: Installing Grace on Ventura fails due to llvm-10 configure failure: command execution failed

[Christopher Jones]

There is no indication below as to why your system is trying to build llvm-10 
as part of installing grace, it does not appear in the dips tree

please run

sudo port clean grace
sudo port -d configure grace

and post the complete transcript of what you get back.

> On 16 Nov 2022, at 9:53 am, Vahid Askarpour  wrote:
> 
> Hi Chris,
> 
> The port rdeps grace command results in
> 
> The following ports are dependencies of grace @5.1.25_5:
> openmotif
>   pkgconfig
> libiconv
>   gperf
>   xbitmaps
>   bison
> xz
>   gettext
> diffutils-for-muniversal
> libtextstyle
>   ncurses
> gettext-runtime
> gettext-tools-libs
> m4
> bison-runtime
>   flex
> lzip
>   libjpeg-turbo
> cmake
>   libcxx
>   curl
> brotli
>   cmake-bootstrap
> libidn2
>   libunistring
> autoconf
> automake
> libtool
> libpsl
>   python310
> bzip2
> expat
> libedit
> libffi
>   expect
> tcl
>   dejagnu
> openssl
>   openssl3
> zlib
> sqlite3
> python_select
> python3_select
> zstd
>   lz4
> nghttp2
> curl-ca-bundle
>   unzip
>   perl5
> perl5.34
>   db48
>   gdbm
> readline
>   libarchive
> libxml2
>   icu
> lzo2
> libb2
>   libuv
> nasm
>   libpng
>   xorg-libsm
> xorg-xtrans
> xorg-libice
>   xorg-xorgproto
>   xorg-libXext
> xorg-util-macros
> xorg-libX11
>   xorg-libXdmcp
>   xorg-libXau
>   xorg-libxcb
> xorg-xcb-proto
> xorg-libpthread-stubs
>   Xft2
> xrender
> freetype
> fontconfig
>   ossp-uuid
>   xorg-libXmu
> xorg-libXt
>   xorg-libXp
> pdflib
> xpm
> openbrowser
>   p5.34-mac-propertylist
> p5.34-xml-entities
>   p5.34-module-build
> p5.34-cpan-meta-yaml
> p5.34-cpan-meta
>   p5.34-cpan-meta-requirements
>   p5.34-encode
>   p5.34-scalar-list-utils
>   p5.34-version
> p5.34-inc-latest
> p5.34-module-metadata
> p5.34-perl-ostype
> p5.34-podlators
>   p5.34-pod-simple
> p5.34-pod-escapes
>   p5.34-html-parser
> p5.34-html-tagset
> p5.34-http-message
>   p5.34-test-needs
>   p5.34-test-simple
>   p5.34-try-tiny
> p5.34-capture-tiny
> p5.34-sub-name
>   p5.34-devel-checkbin
> p5.34-extutils-makemaker
>   p5.34-extutils-manifest
>   p5.34-clone
> p5.34-b-cow
>   p5.34-xsloader
>   p5.34-compress-raw-bzip2
> p5.34-test-cpan-meta
> p5.34-test-cpan-meta-json
>   p5.34-json
> p5.34-json-xs
>   p5.34-canary-stability
>   p5.34-common-sense
>   p5.34-types-serialiser
> p5.34-test-pod
>   p5.34-compress-raw-zlib
>   p5.34-encode-locale
>   p5.34-http-date
> p5.34-time-local
> p5.34-timedate
>   p5.34-io-compress
>   p5.34-io-compress-brotli
> p5.34-file-slurper
>   p5.34-test-warnings
> p5.34-cpan-meta-check
>   p5.34-test-deep
> p5.34-getopt-long
> p5.34-time-hires
>   p5.34-io-html
>   p5.34-lwp-mediatypes
> p5.34-test-fatal
>   p5.34-uri
> 
> Is p5/openbrowser the cause of the crash? 
> 
> As for llvm-10, the “port install grace” picked it for installation.
> 
> Thanks,
> Vahid
> 
>> On Nov 16, 2022, at 3:48 AM, Chris Jones  wrote:
>> 
>> CAUTION: The Sender of this email is not from within Dalhousie.
>> 
>> Hi,
>> 
>> Your snippet below indicates that in fact you have not installed all the 
>> dependencies of grace, as it is failing in building llvm-10. Please run
>> 
>> port rdeps grace
>> 
>> To identify which port in the dependency tree of grace is bringing this in.
>> 
>> llvm-10 is quite old at this point, and only time will tell if building it 
>> on macOS13 will be possible or not. Ideally, it would be best to update 
>> whatever port is requiring this to use a newer llvm version.
>> 
>> Chris
>> 
>>> On 15 Nov 2022, at 9:59 pm, Vahid Askarpour  wrote:
>>> 
>>> Dear MacPorts Users,
>>> 
>>> MacPorts installs all the dependencies of Grace successfully but the 
>>> following error occurs while building Grace:
>>> 
>>> Configuring llvm-10
>>> Error: Failed to configure llvm-10: consult 
>>> /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_llvm-10/llvm-10/work/build/CMakeFiles/CMakeError.log

Re: Library Problem

[Christopher Jones]

https://trac.macports.org/ticket/65503#ticket

> On 18 Jul 2022, at 9:53 am, Christopher Jones  
> wrote:
>
>
> Actually, there might be something I can do to address this, more in a bit...
>
>> On 18 Jul 2022, at 9:22 am, Christopher Jones  
>> wrote:
>>
>> Hi,
>>
>> No, you need to recompile everything…
>>
>> Chris
>>
>>> On 17 Jul 2022, at 10:31 pm, Jim Secan  wrote:
>>>
>>> I’m a gfortran user and by no stretch of the imagination a guru on how the 
>>> gcc compilers are rigged up.  I just recently did a full update of my 
>>> MacPorts codes, after which I get the following complaint whenever I try to 
>>> run any codes compiled and linked prior to the update:
>>>
>>> dyld: Library not loaded: @rpath/libgcc_s.1.1.dylib
>>> Referenced from: /opt/local/lib/libgcc/libgcc_s.1.dylib
>>> Reason: image not found
>>> Trace/BPT trap
>>>
>>> If I completely recompile and relink the program, everything works just 
>>> fine.  So, is there anything short of recompiling every code I have 
>>> (numbers in the many hundreds) that I can do to fix this?
>>>
>>> Thanks.
>>>
>>> Jim
>>> Seattle, WA
>>>
>>
>



smime.p7s
Description: S/MIME cryptographic signature

Re: Library Problem

[Christopher Jones]

Actually, there might be something I can do to address this, more in a bit...

> On 18 Jul 2022, at 9:22 am, Christopher Jones  
> wrote:
>
> Hi,
>
> No, you need to recompile everything…
>
> Chris
>
>> On 17 Jul 2022, at 10:31 pm, Jim Secan  wrote:
>>
>> I’m a gfortran user and by no stretch of the imagination a guru on how the 
>> gcc compilers are rigged up.  I just recently did a full update of my 
>> MacPorts codes, after which I get the following complaint whenever I try to 
>> run any codes compiled and linked prior to the update:
>>
>> dyld: Library not loaded: @rpath/libgcc_s.1.1.dylib
>> Referenced from: /opt/local/lib/libgcc/libgcc_s.1.dylib
>> Reason: image not found
>> Trace/BPT trap
>>
>> If I completely recompile and relink the program, everything works just 
>> fine.  So, is there anything short of recompiling every code I have (numbers 
>> in the many hundreds) that I can do to fix this?
>>
>> Thanks.
>>
>> Jim
>> Seattle, WA
>>
>



smime.p7s
Description: S/MIME cryptographic signature

Re: Library Problem

[Christopher Jones]

Hi,

No, you need to recompile everything…

Chris

> On 17 Jul 2022, at 10:31 pm, Jim Secan  wrote:
>
> I’m a gfortran user and by no stretch of the imagination a guru on how the 
> gcc compilers are rigged up.  I just recently did a full update of my 
> MacPorts codes, after which I get the following complaint whenever I try to 
> run any codes compiled and linked prior to the update:
>
> dyld: Library not loaded: @rpath/libgcc_s.1.1.dylib
>  Referenced from: /opt/local/lib/libgcc/libgcc_s.1.dylib
>  Reason: image not found
> Trace/BPT trap
>
> If I completely recompile and relink the program, everything works just fine. 
>  So, is there anything short of recompiling every code I have (numbers in the 
> many hundreds) that I can do to fix this?
>
> Thanks.
>
> Jim
> Seattle, WA
>



smime.p7s
Description: S/MIME cryptographic signature

Re: Uninstalling MacPorts on Mac M1 Chip

[Christopher Jones]

please keep your replies on-list

$ is not the command, just an illustration of the shell prompt ;)

 the command itself starts with ’sudo’

actually, this probably explains your first error. run

sudo port -fp uninstall installed

etc.

Chris

> On 12 Jan 2022, at 4:51 pm, Lisa Kim  wrote:
> 
> Hi Chris! 
>  
> Thanks for your email. 
> Unfortunately, when I try 2.4.2 or 2.4.3, I get the same output: “-bash: $: 
> command not found”
>  
> Lisa
>  
> From: Christopher Jones 
> Date: Wednesday, January 12, 2022 at 10:49 AM
> To: Lisa Kim 
> Cc: macports-users@lists.macports.org 
> Subject: Re: Uninstalling MacPorts on Mac M1 Chip
> 
>  
> Sorry, read your post again…
>  
> If the port command is not working for you, then just skip that command. go 
> on with 2.4.2 and 2.4.3
>  
> Chris
>  
>  
> 
> 
> On 12 Jan 2022, at 4:48 pm, Christopher Jones  <mailto:jon...@hep.phy.cam.ac.uk>> wrote:
>  
>  
> Did you follow all the steps under
>  
> https://guide.macports.org/#installing.macports.uninstalling 
> <https://guide.macports.org/#installing.macports.uninstalling>
>  
> ?
>  
> On 12 Jan 2022, at 4:45 pm, Lisa Kim  <mailto:lisakim...@gmail.com>> wrote:
>  
> Hi,
>  
> I would like to uninstall MacPorts entirely from my Macbook Pro M1. I am 
> currently running MacOS Monterey.
> I initially installed MacPorts on my MacBook Air 2011?, but when I bought my 
> new Macbook Pro M1, I transferred all of the files from the old to new 
> computer. As a result, I still have MacPorts on my new mac. I would like to 
> uninstall it entirely. 
>  
> In an attempt to uninstall MacPorts myself when I first bought the new mac, I 
> may have tried to delete any associated files by searching “MacPorts”. But 
> truthfully, I don’t remember if I had any luck.  
>  
> I have followed the instructions posted on the guide.macports.org 
> <http://guide.macports.org/> website, but have had no success. The output I 
> receive from the “$ sudo port -fp uninstall installed” input is:  
> -bash: $: command not found
>  
> I have no idea where to go from here. Any help would be appreciated.
>  
> Thanks.



smime.p7s
Description: S/MIME cryptographic signature

Re: Uninstalling MacPorts on Mac M1 Chip

[Christopher Jones]

Sorry, read your post again…

If the port command is not working for you, then just skip that command. go on 
with 2.4.2 and 2.4.3

Chris



> On 12 Jan 2022, at 4:48 pm, Christopher Jones  
> wrote:
> 
> 
> Did you follow all the steps under
> 
> https://guide.macports.org/#installing.macports.uninstalling 
> <https://guide.macports.org/#installing.macports.uninstalling>
> 
> ?
> 
>> On 12 Jan 2022, at 4:45 pm, Lisa Kim > <mailto:lisakim...@gmail.com>> wrote:
>> 
>> Hi,
>>  
>> I would like to uninstall MacPorts entirely from my Macbook Pro M1. I am 
>> currently running MacOS Monterey.
>> I initially installed MacPorts on my MacBook Air 2011?, but when I bought my 
>> new Macbook Pro M1, I transferred all of the files from the old to new 
>> computer. As a result, I still have MacPorts on my new mac. I would like to 
>> uninstall it entirely. 
>>  
>> In an attempt to uninstall MacPorts myself when I first bought the new mac, 
>> I may have tried to delete any associated files by searching “MacPorts”. But 
>> truthfully, I don’t remember if I had any luck.  
>>  
>> I have followed the instructions posted on the guide.macports.org 
>> <http://guide.macports.org/> website, but have had no success. The output I 
>> receive from the “$ sudo port -fp uninstall installed” input is:  
>> -bash: $: command not found
>>  
>> I have no idea where to go from here. Any help would be appreciated.
>>  
>> Thanks.
> 



smime.p7s
Description: S/MIME cryptographic signature

Re: Uninstalling MacPorts on Mac M1 Chip

[Christopher Jones]

Did you follow all the steps under

https://guide.macports.org/#installing.macports.uninstalling 


?

> On 12 Jan 2022, at 4:45 pm, Lisa Kim  wrote:
> 
> Hi,
>  
> I would like to uninstall MacPorts entirely from my Macbook Pro M1. I am 
> currently running MacOS Monterey.
> I initially installed MacPorts on my MacBook Air 2011?, but when I bought my 
> new Macbook Pro M1, I transferred all of the files from the old to new 
> computer. As a result, I still have MacPorts on my new mac. I would like to 
> uninstall it entirely. 
>  
> In an attempt to uninstall MacPorts myself when I first bought the new mac, I 
> may have tried to delete any associated files by searching “MacPorts”. But 
> truthfully, I don’t remember if I had any luck.  
>  
> I have followed the instructions posted on the guide.macports.org 
>  website, but have had no success. The output I 
> receive from the “$ sudo port -fp uninstall installed” input is:  
> -bash: $: command not found
>  
> I have no idea where to go from here. Any help would be appreciated.
>  
> Thanks.



smime.p7s
Description: S/MIME cryptographic signature

Re: certbot for 'arm64' dependency py39-zope-hookable only supports 'x86_64' #64364

[Christopher Jones]

https://guide.macports.org/#project.contributing.updates

> On 5 Jan 2022, at 10:53 am, Peter West  wrote:
> 
> There’s some devilish detail involved in this seemingly simple process. I’ll 
> fiddle with it.
> 
> 
> —
> Peter West
> p...@ehealth.id.au <mailto:p...@ehealth.id.au>
> “Behold, this child is appointed for the fall and rising of many in Israel, 
> and for a sign that is opposed (and a sword will pierce through your own soul 
> also), so that thoughts from many hearts may be revealed.”
> 
>> On 5 Jan 2022, at 8:44 pm, Christopher Jones > <mailto:jon...@hep.phy.cam.ac.uk>> wrote:
>> 
>> 
>> Few maintainers/users have arm machines at this time, so for those that do 
>> you have to expect to do some leg work yourself. I suggest trying to edit 
>> the Portfile in question, removing the line that limits the platforms
>> 
>> https://github.com/macports/macports-ports/blob/a34b9f304f3a13bb9239e2ae9917ee3a41de3e9f/python/py-zope-hookable/Portfile#L13
>>  
>> <https://github.com/macports/macports-ports/blob/a34b9f304f3a13bb9239e2ae9917ee3a41de3e9f/python/py-zope-hookable/Portfile#L13>
>> 
>> and see for yourself if it works. If it does, submit a PR with the change.
>> 
>> Chris
>> 
>> 
>>> On 5 Jan 2022, at 10:26 am, Peter West >> <mailto:p...@pbw.id.au>> wrote:
>>> 
>>> I’ve just updated to Monterey 12.1 from Big Sur and am re-installing 
>>> manually.
>>> 
>>> Tried to install certbot and encountered the failure now documented in 
>>> #64364.
>>> 
>>> Is there a workaround?
>>> 
>>> 
>>> —
>>> Peter West
>>> p...@ehealth.id.au <mailto:p...@ehealth.id.au>
>>> “Behold, this child is appointed for the fall and rising of many in Israel, 
>>> and for a sign that is opposed (and a sword will pierce through your own 
>>> soul also), so that thoughts from many hearts may be revealed.”
>>> 
>> 
> 



smime.p7s
Description: S/MIME cryptographic signature

Re: certbot for 'arm64' dependency py39-zope-hookable only supports 'x86_64' #64364

[Christopher Jones]

Few maintainers/users have arm machines at this time, so for those that do you 
have to expect to do some leg work yourself. I suggest trying to edit the 
Portfile in question, removing the line that limits the platforms

https://github.com/macports/macports-ports/blob/a34b9f304f3a13bb9239e2ae9917ee3a41de3e9f/python/py-zope-hookable/Portfile#L13
 


and see for yourself if it works. If it does, submit a PR with the change.

Chris


> On 5 Jan 2022, at 10:26 am, Peter West  wrote:
> 
> I’ve just updated to Monterey 12.1 from Big Sur and am re-installing manually.
> 
> Tried to install certbot and encountered the failure now documented in #64364.
> 
> Is there a workaround?
> 
> 
> —
> Peter West
> p...@ehealth.id.au
> “Behold, this child is appointed for the fall and rising of many in Israel, 
> and for a sign that is opposed (and a sword will pierce through your own soul 
> also), so that thoughts from many hearts may be revealed.”
> 



smime.p7s
Description: S/MIME cryptographic signature

Re: ffmpeg unexpectedly uninstalled

[Christopher Jones]

> On 4 Jan 2022, at 9:38 am, Ryan Schmidt  wrote:
>
> On Jan 4, 2022, at 02:52, Christopher Jones wrote:
>
>> Personally, I also occasionally run
>>
>>> port list requested
>>
>> to see the list of ports I have actively *requested* to be installed. This 
>> excludes ports just installed as dependencies of others.
>
> Note that you should use "port installed requested" rather than "port list 
> requested" since "port list" will show you what is available whereas "port 
> installed" will show you what is actually installed. See:
>
> https://trac.macports.org/wiki/FAQ#portlist
>
> "port installed" is also considerably faster than "port list”.

yeah, I am ware of this option (and port list gives a warning at the start)


Oberon ~/Projects/MacPorts/ports > port list requested
Warning: The 'list' action only shows the currently available version of each 
port. To see installed versions, use the 'installed' action.


I still use it though as frankly I prefer the formatting of the output it 
gives, compared to ‘port installed’

Chris

smime.p7s
Description: S/MIME cryptographic signature

Re: ffmpeg unexpectedly uninstalled

[Christopher Jones]

As others have already commented, the best way to perform regular clean up on 
your installation is to just run

> sudo port reclaim

that does a number of tasks, all designed to clean up your installation.

Personally, I also occasionally run

> port list requested

to see the list of ports I have actively *requested* to be installed. This 
excludes ports just installed as dependencies of others.

If there are any in that list I do not really want any longer, I then run

> sudo port setunrequested 

on them. port reclaim will then remove these ports, if they are not required as 
a dep of some other one.

Chris

> On 4 Jan 2022, at 8:24 am, Mick  wrote:
>
> On Tue, Jan 04, 2022 at 08:56:43AM +0700, Michael Newman via macports-users 
> wrote:
>> I'm using the -f option because I copied it from some recommendation I read 
>> somewhere. I'm not smart enough to figure things like this out myself so I 
>> usually rely on what I find by searching. For years I just ran:
>>
>> sudo port selfupdate
>> sudo port upgrade outdated
>>
>> But then I read somewhere that to remove unneeded junk I should also run:
>>
>> sudo port -f clean --all all
>> sudo port -f uninstall inactive
>> sudo port uninstall leaves
>>
> What I usually do, is:
>
>  sudo port selfupdate
>  sudo port -u upgrade outdated
>
> I read quite recently in the port documentation (man port) about the
> usage of that "-u" option, which does exactly what you want, that is
> removing inactive ports.
>
> I'm not an expert; I just read every now and than chunk of the manual,
> so any comment from people with more knowelge/experience is wellcome,
> even just a confirmation.
> --
> Mick
>



smime.p7s
Description: S/MIME cryptographic signature

Re: ImageMagick failure to install

[Christopher Jones]

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@mm02:~
>
> After that I could ins

Re: ImageMagick failure to install

[Christopher Jones]

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
>>>
>>>
>>
>



smime.p7s
Description: S/MIME cryptographic signature

Re: ImageMagick failure to install

[Christopher Jones]

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
>
>



smime.p7s
Description: S/MIME cryptographic signature

Re: python ports depend on openssl not in index

[Christopher Jones]

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.



smime.p7s
Description: S/MIME cryptographic signature

Re: mozjs60 doesn't want to install

[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@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@computer ~ %
> 
> What should I do to install it?
> 
> With regards
> Stevan Tiefert



smime.p7s
Description: S/MIME cryptographic signature

Re: liboil fail to compile

[Christopher Jones]

Hi,

yes, Ryan beat me to reply here ;)

https://github.com/macports/macports-ports/commit/d5397ebb011482fd219217c44b21d2c0b329180d
 


Chris

> On 23 Nov 2021, at 1:41 pm, Ryan Schmidt  wrote:
> 
> On Nov 23, 2021, at 06:49, Ryan Schmidt wrote:
> 
>> On Nov 22, 2021, at 07:14, rmgls wrote:
>> 
>>> mplayer install  fails because liboil does not  build correctly.
>>> as i can see it is gtkdocize related.
>>> any hints would be appreciated.
>> 
>> We will need more information from you. I see packages successfully built 
>> for liboil on our build system on macOS 11 and earlier, and a build failure 
>> on macOS 12, but I see no bugs open for this port in the issue tracker. 
>> Please file a bug report and attach your main.log file.
> 
> Chris just submitted a build fix for liboil. Wait an hour, then run sudo port 
> selfupdate, then try again.
> 



smime.p7s
Description: S/MIME cryptographic signature

Re: xorg-server

[Christopher Jones]

See https://trac.macports.org/ticket/63990 


rev bumping the xinit port fixed things, at least for me. Please if you are 
having trouble with the X11 server see if that update helps...

> On 18 Nov 2021, at 8:02 am, Ryan Schmidt  wrote:
> 
> On Nov 15, 2021, at 15:11, Tom wrote:
> 
>> On 12. Nov 2021, at 21:17, Chris Jones wrote:
>>> 
>>> Impossible to say without more data.
>>> 
>>> Do you have any crash logs in Console ? Any other messages ?
>>> 
>>> What application are you running ? Try install a simple one like xclock and 
>>> see if that works ?
>>> 
>>> Have you tired removing then reinstalling the xorg-server port ?
>>> 
>>> Are you actually using the xorg-server X11 server or do you perhaps have 
>>> another one installed instead ?
>>> 
>>> Have you logged out and back in again, as required by the xorg-server 
>>> instalation ?
>> 
>> Same problem with xclock. Where can I find the log file of the xorg-server?
> 
> On macOS, crash logs are located in ~/Library/Logs/DiagnosticReports.
> 



smime.p7s
Description: S/MIME cryptographic signature

Re: provide latest OS root certificates via port?

[Christopher Jones]

>
>> it uses the libcurl support compiled into macports base, which
>> defaults to using the system curl. To change that you need to rebuild
>> base against an updated lib curl.
>
> Is that something that can be made to happen for all users by the creation
> of a new version of something (e.g., tclsh or whatever is linking against
> that library)?

Having Macports base ship and build against its own copy of curl by default is 
something that has been discussed previously. I think a fair summary is there 
is no consensus as to if it is the right thing to do.

Chris

smime.p7s
Description: S/MIME cryptographic signature

Re: provide latest OS root certificates via port?

[Christopher Jones]

>
> Unfortunately, mpstats submit still doesn't work on 10.6.8,
> even with /usr/bin/curl replaced with a symlink to
> /opt/local/bin/curl. I don't understand that.
> /usr/bin/curl https://ports.macports.org works there with
> the symlink in place.


mpstat doesn’t use the command line curl utility, so that change will have no 
impact on it.

it uses the libcurl support compiled into macports base, which defaults to 
using the system curl. To change that you need to rebuild base against an 
updated lib curl.

Chris



smime.p7s
Description: S/MIME cryptographic signature

Re: do I have to reinstall my ports after upgrading to Monterey?

[Christopher Jones]

Hi,

You are mixing up a number of different issues with different ports below. Your 
first port (all puns intended) of call should be

https://ports.macports.org <https://ports.macports.org/>

look up the port in question, and then see if any of the active ports match 
what you see. If not, think about submitting  ticket as these are the best way 
to track issues.

e.g. For {lib}gcc11, it is known about

https://trac.macports.org/ticket/63677 <https://trac.macports.org/ticket/63677>

No resolution as of yet I am afraid.

cheers Chris

> On 31 Oct 2021, at 10:53 pm, Artemio González López via macports-users 
>  wrote:
> 
> 
>> On 31 Oct 2021, at 16:46, Christopher Jones > <mailto:jon...@hep.phy.cam.ac.uk>> wrote:
>> 
>> 
>> Yes you do. You should always follow the migration instructions under
>> 
>> https://trac.macports.org/wiki/Migration 
>> <https://trac.macports.org/wiki/Migration>
>> 
>> Chris
>> 
>>> On 31 Oct 2021, at 3:45 pm, Artemio González López via macports-users 
>>> >> <mailto:macports-users@lists.macports.org>> wrote:
>>> 
>>> I just installed macOS 12.0.1 on an M1 MacBook Pro 13” from last year, and 
>>> I was wondering if it’s necessary to reinstall all my ports (which I 
>>> installed under Big Sur) after the update (they seem to be running just 
>>> fine).
>>> 
>>> Thanks a lot in advance,
>>> 
>>> Artemio
>>> 
>>> 
>>> Artemio Gonzalez Lopez
>>> artem...@mac.com <mailto:artem...@mac.com>
>> 
> 
> Hi, Chris,
> 
> Thanks a lot for your (almost instantaneous!) answer. I followed your advised 
> and proceeded to migrate my MacPorts installation to macOS 12. I first 
> upgraded to Xcode 13.1, and downloaded (from the Developer site) and 
> installed the 13.1 Command Tools, and then followed all the steps in the 
> migration instructions. The only non-standard thing I did was to change 
> macports.conf the build_arch to arm64 by adding the following line to it:
> 
> build_arch  arm64
> 
>  However, the last command (sudo ./restore_ports.tcl myports.txt) ended with 
> the following error:
> 
> --->  Building libgcc11
> Error: Failed to build libgcc11: command execution failed
> Error: See 
> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc11/libgcc11/main.log
>  for details.
> --->  Computing dependencies for py39-pyqt5
> --->  Dependencies to be installed: qt5 qt5-qt3d qt5-qtbase qt5-qtdeclarative 
> qt5-qtsvg qt5-qtgamepad qt5-qtimageformats qt5-qtconnectivity 
> qt5-qtgraphicaleffects qt5-qtlocation qt5-qtquickcontrols 
> qt5-qtquickcontrols2 qt5-qtserialport qt5-qtmacextras qt5-qtmultimedia 
> qt5-qtnetworkauth qt5-qtremoteobjects qt5-qtscxml qt5-qtsensors 
> qt5-qtserialbus qt5-qtspeech qt5-qttools qt5-qttranslations qt5-qtwebchannel 
> qt5-qtwebsockets qt5-qtxmlpatterns qt5-sqlite-plugin qt5-qtscript
> Warning: The macOS 12 SDK does not appear to be installed. Ports may not 
> build correctly.
> Warning: You can install it as part of the Xcode Command Line Tools package 
> by running `xcode-select --install'.
> --->  Fetching archive for qt5-qtbase
> --->  Attempting to fetch qt5-qtbase-5.15.2_2+openssl.darwin_21.arm64.tbz2 
> from https://packages.macports.org/qt5-qtbase 
> <https://packages.macports.org/qt5-qtbase>
> --->  Attempting to fetch qt5-qtbase-5.15.2_2+openssl.darwin_21.arm64.tbz2 
> from https://fra.de.packages.macports.org/qt5-qtbase 
> <https://fra.de.packages.macports.org/qt5-qtbase>
> --->  Attempting to fetch qt5-qtbase-5.15.2_2+openssl.darwin_21.arm64.tbz2 
> from https://mse.uk.packages.macports.org/qt5-qtbase 
> <https://mse.uk.packages.macports.org/qt5-qtbase>
> --->  Configuring qt5-qtbase
> Error: Failed to configure qt5-qtbase: configure failure: command execution 
> failed
> Error: See 
> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_aqua_qt5/qt5-qtbase/main.log
>  for details.
> 
> In fact, going through the command output in the Terminal window I found that 
> the first warning about the macOS 12 SDK was here:
> 
> --->  Cleaning py39-widgetsnbextension
> Warning: The macOS 12 SDK does not appear to be installed. Ports may not 
> build correctly.
> Warning: You can install it as part of the Xcode Command Line Tools package 
> by running `xcode-select --install'.
> --->  Computing dependencies for qt5-qtbase
> 
> I also found quite a few warnings to the effect that libgcc11 had failed to 
> build before the last one.
&g

Re: do I have to reinstall my ports after upgrading to Monterey?

[Christopher Jones]

Yes you do. You should always follow the migration instructions under

https://trac.macports.org/wiki/Migration 


Chris

> On 31 Oct 2021, at 3:45 pm, Artemio González López via macports-users 
>  wrote:
> 
> I just installed macOS 12.0.1 on an M1 MacBook Pro 13” from last year, and I 
> was wondering if it’s necessary to reinstall all my ports (which I installed 
> under Big Sur) after the update (they seem to be running just fine).
> 
> Thanks a lot in advance,
> 
> Artemio
> 
> 
> Artemio Gonzalez Lopez
> artem...@mac.com 



smime.p7s
Description: S/MIME cryptographic signature

Re: provide latest OS root certificates via port?

[Christopher Jones]

> On 29 Oct 2021, at 4:17 pm, Richard Bonomo TDS personal  
> wrote:
> 
> 
> I don't know what to think about MacPorts, specifically, providing
> new certificates, but, pertaining to some of the arguments presented
> against doing this on old Macs generally, it must be kept in mind
> that some of us -- including yours truly -- have Apple computers that
> CANNOT use newer operating systems or browsers.  Sometimes, one has
> to work with what one has.

There are other OSes, linux distros for instance, designed for such scenarios..

> 
> Rich
> 
> - Original Message -
> From: "Bill Cole" 
> To: "macports-users Users" 
> Sent: Friday, October 29, 2021 10:09:45 AM
> Subject: Re: provide latest OS root certificates via port?
> 
> On 2021-10-29 at 07:23:38 UTC-0400 (Fri, 29 Oct 2021 07:23:38 -0400)
> Richard L. Hamilton 
> is rumored to have said:
> 
>> You're (probably - seems plausible but I haven't verified it myself) 
>> right that that's annoying and fixable.
>> 
>> But there's a big reason to think carefully about whether to do that. 
>> If something is old enough that it isn't receiving certificate 
>> updates, it probably isn't receiving security updates either. And the 
>> same applications and functionality that need current root 
>> certificates to work are also likely to be common attack points.
>> 
>> So at the very least, anything that makes it easier to take such a 
>> risk should come with a prominent warning, IMO.
> 
> Yes: Anyone running Mojave or earlier is not exactly skydiving without a 
> parachute, but is doing something close. Perhaps it's akin to skydiving 
> with a homemade parachute...
> 
> Frankly, I don't think MacPorts should attempt to 'fix' this issue or 
> similar future issues diretly, not because it encourages risky behavior 
> but because MacPorts should avoid poking around in the MacOS base at all 
> where it isn't essential for the operation of MacPorts. It's easy enough 
> in principle for MacPorts to stand up and use its own modern OSS-based 
> encryption+PKI stack with its own set of trusted CAs (e.g. 
> curl-ca-bundle and openssl ports) and so keep itself functional without 
> poking around in core functionality of the OS that MacPorts-naive tools 
> need to use. People who need to fix the problem of an expired root cert 
> should be able to understand and repair that problem (which can be done 
> without digging a CA bundle out of a newer system) if they need to, and 
> having the issue unaddressed is not itself a security issue, but a 
> functionality issue. Anyone who actually wants to run Safari & Chrome on 
> an OS that isn't getting basic security maintenance should be thinking 
> very carefully about what they are doing and accept responsibility for 
> making something work which arguably should no longer work because it is 
> too risky.
> 
> One risk for MacPorts is a slippery slope created by providing support 
> for antique OS versions that include opaque proprietary bits that are 
> probably insecure in ways that no one fully understands. If it is taken 
> too far (which in my opinion includes fixing core components like PKI) 
> MP would be doing a disservice to users who understandably expect a 
> "Just Works" experience on a Mac by enabling the continued use of tools 
> that could well have permanent unrecognized and mostly invisible 
> security flaws.
> 
> 
>>> On Oct 29, 2021, at 07:12, René J.V. Bertin  
>>> wrote:
>>> 
>>> Hi,
>>> 
>>> Users of older Apple OSes that are no longer receiving updates 
>>> probably noticed that Safari and Chrome-based browsers no longer 
>>> connect to lots of sites because a crucial root certificate has 
>>> expired.
>>> 
>>> Answer 1 to 
>>> https://apple.stackexchange.com/questions/422332/how-do-i-update-my-root-certificates-on-an-older-version-of-mac-os-e-g-el-capi
>>>  
>>> provides an easy solution, but you need access to an up-to-date OS 
>>> install.
>>> 
>>> These are not proprietary to Apple so I presume it should be possible 
>>> to provide the suggested `rootcerts.pem` file via a port - possibly 
>>> even install it in the post-activate. I had a look but couldn't find 
>>> if such a port already exists. I think it'd help for lots of 
>>> people... I'd propose a draft but I'm running 10.9 ... so thanks to 
>>> anyone picking this up!
>>> 
>>> R.
>>> 
> 
> 
> -- 
> Bill Cole
> b...@scconsult.com or billc...@apache.org
> (AKA @grumpybozo and many *@billmail.scconsult.com addresses)
> Not Currently Available For Hire



smime.p7s
Description: S/MIME cryptographic signature

Re: Youtube-dl install failure

[Christopher Jones]

create a trac ticket, with a *complete* build log.

> On 27 Oct 2021, at 5:11 pm, dan d.  wrote:
> 
> 
> If I had to guess the install routine is not fetching the youtube-dl 
> distribution files to install.
> 
> I get this error message
> 
> Error: Failed to install youtube-dl: no destroot found at: 
> /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_net_youtube-dl/youtube-dl/work/destroot--
> Any help appreciated.
> 
> ent-
> XR



smime.p7s
Description: S/MIME cryptographic signature

Re: Question about realeasing *pkg for macOS 12 on website

[Christopher Jones]

I don’t know about an ETA, but you do not need to wait for them to get started. 
Just follow the install from source instructions in the meantime.

> On 26 Oct 2021, at 1:26 pm, xgfvc via macports-users 
>  wrote:
> 
> Hello everyone,
> 
> Hope you’re doing well. I have a question: Do we have an ETA on *pkg file for 
> macOS 12 released/uploaded on the macports website?
> 
> Kindly,
> Jacob   



smime.p7s
Description: S/MIME cryptographic signature

Re: Macports for Monterey on M1, M1 Pro, M1 Max

[Christopher Jones]

Hi,

In that MacPorts already supports arm for macOS11, adding support for macOS12 
will likely not be as much of a deal as it was for macOS11, where it was a 
brand new arch. I imagine it will be, give or take, as much work as any other 
OS has been on the x86_64 side. As for if/when there will be binary tarballs 
for macOS12, thats a question for Ryan who hosts/maintains that hardware.

In terms of specific support for the Pro and Max CPU variants, this really down 
to the compiler to support, so assuming Xcode knows what to do, will be there 
from day one. However, as far as I have seen the CPU cores are essentially the 
same as in the M1, so in that regards the Pro/Max will  seem like the same, 
just with more cores. So any ports that support multi-threaded running will 
gain out the box.

Chris

> On 19 Oct 2021, at 6:20 pm, Vihan Pandey  wrote:
> 
> Hello,
> 
> I wanted to know if there are any plans for creating a port of macports for 
> Monterey for the new M1, and specifically optimized for M1 Pro and M1 Max 
> processors?
> 
> Thanks and regards,
> 
> - Vihan



smime.p7s
Description: S/MIME cryptographic signature

Re: Error: Failed to build librsvg: command execution failed

[Christopher Jones]

> On 13 Oct 2021, at 1:54 pm, Michael Newman  wrote:
> 
>> On Oct 13, 2021, at 18:12, Lenore Horner > <mailto:lenorehor...@sbcglobal.net>> wrote:
>> 
>> Do you have /opt/local/bin/clang-mp-11? 
> 
> Axe:~ mnewman$ ls /opt/local/bin/clang-mp-11
> ls: /opt/local/bin/clang-mp-11: No such file or directory
> 
> 
>> On Oct 13, 2021, at 19:31, Christopher Jones > <mailto:jon...@hep.phy.cam.ac.uk>> wrote:
>> 
>> oh, and to be sure please first run `sudo port sync` t make sure your ports 
>> are fully up to date….
> 
> Axe:~ mnewman$ sudo port sync
> Password:
> --->  Updating the ports tree
> Error: Synchronization of the local ports tree failed doing rsync
> port sync failed: Synchronization of 1 source failed


Maybe not an issue here, but the above is a problem I don’t personally see so 
you should look into it...

> 
> 
>> On Oct 13, 2021, at 19:30, Christopher Jones > <mailto:jon...@hep.phy.cam.ac.uk>> wrote:
>> 
>> Please run `port info librsvg rust` and post what that returns.
> 
> Axe:~ mnewman$ port info librsvg rust
> librsvg @2.52.1_1 (graphics, gnome)
> Variants: quartz, universal, x11
> 
> Description:  GNOME implementation of rsvg.
> Homepage: https://wiki.gnome.org/Projects/LibRsvg 
> <https://wiki.gnome.org/Projects/LibRsvg>
> 
> Extract Dependencies: xz
> Build Dependencies:   pkgconfig, rust, cargo
> Library Dependencies: glib2, cairo, pango, gdk-pixbuf2, libxml2, vala,
>   gobject-introspection
> Platforms:darwin
> License:  (GPL-2+ or LGPL-2+)
> Maintainers:  Email: dev...@macports.org 
> <mailto:dev...@macports.org>, GitHub: dbevans
>   Email: masc...@macports.org 
> <mailto:masc...@macports.org>, GitHub: mascguy
>   Policy: openmaintainer
> --
> rust @1.55.0_3 (lang, devel)
> Sub-ports:rust-compiler-wrap, rust-src
> 
> Description:  Rust is a curly-brace, block-structured expression
>   language. It visually resembles the C language family, 
> but
>   differs significantly in syntactic and semantic details.
>   Its design is oriented toward concerns of "programming 
> in
>   the large", that is, of creating and maintaining
>   boundaries -- both abstract and operational -- that
>   preserve large-system integrity, availability and
>   concurrency.
> Homepage: https://www.rust-lang.org <https://www.rust-lang.org/>
> 
> Build Dependencies:   git, cmake, cctools, python39, openssl, pkgconfig, 
> ninja,
>   gmake
> Library Dependencies: libffi, libgit2, openssl
> Platforms:darwin
> License:  (MIT or Apache-2) and BSD and zlib and NCSA and 
> Permissive
> Maintainers:  Email: g...@macports.org <mailto:g...@macports.org>, 
> GitHub: g5pw
>   Email: herby.gil...@gmail.com 
> <mailto:herby.gil...@gmail.com>, GitHub: herbygillot
>   Policy: openmaintainer

right, the above is what I expected.

I can reproduce here on my 10.13 machine using the binary tarballs, and in fact 
if I look at the build logs for those tarballs

https://build.macports.org/builders/ports-10.13_x86_64-builder/builds/124766/steps/install-port/logs/stdio/text
 
<https://build.macports.org/builders/ports-10.13_x86_64-builder/builds/124766/steps/install-port/logs/stdio/text>

you can see the build was indeed configured to use macports clang-11, which is 
why its needed at runtime with rustc. 

If though I start a new build by hand, it doesn’t use macports clang 11 and 
instead uses Xcode clang (the norm on  ’newer’ systems).

I don’t know why, but it seems then there is a mis-match between what the port 
now thinks it needs, and what was used for the last binary tarball. I’ll commit 
a rev-bump just to trigger a rebuild and hopefully that will fix things.

In the meantime if you are in a hurry installing macports clang 11 should also 
fix things.

Chris


> 
> 



smime.p7s
Description: S/MIME cryptographic signature

Re: Error: Failed to build librsvg: command execution failed

[Christopher Jones]

oh, and to be sure please first run `sudo port sync` t make sure your ports are 
fully up to date….

> On 13 Oct 2021, at 1:30 pm, Christopher Jones  
> wrote:
> 
> That old ticket indeed has nothing to do with the issues here
> 
> The rust port does indeed require macports clang (on older systems) to be 
> available when building with rustic. However, macOS 10.13 is not one of these 
> (at starts with 10.12) so it shouldn’t be needing it.
> 
> Please run `port info librsvg rust` and post what that returns.
> 
> Chris
> 
>> On 13 Oct 2021, at 12:12 pm, Lenore Horner > <mailto:lenorehor...@sbcglobal.net>> wrote:
>> 
>> I’m not sure that’s the same bug (it’s 4 years old too).  That one was not 
>> finding rust.  The log you posted says lbrsvg prefers compilers 
>> macports-clang- anything from 5.0 up to 12 but then says it’s going to use 
>> Xcode Clang (which doesn’t make sense to me but could be just I don’t know 
>> enough) and then eventually fails because it can’t find the linker 
>> `/opt/local/bin/clang-mp-11`.  I happen to have clang-12 installed via 
>> macports and do have /opt/local/bin/clang-mp-12 so I would guess it thinks 
>> you have clang-11 installed.  Do you have /opt/local/bin/clang-mp-11?  
>> Lenore
>> 
>>> On Oct 13, 2021, at 02:27, Michael Newman via macports-users 
>>> >> <mailto:macports-users@lists.macports.org>> wrote:
>>> 
>>> Old 2010 MacBook Air on: 10.13.6
>>> MacPorts: 2.7.1
>>> CLTools: 10.1.0.0.1.1539992718
>>> 
>>> Here's the error:
>>> 
>>> Error: Failed to build librsvg: command execution failed
>>> Error: See 
>>> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_librsvg/librsvg/main.log
>>>  for details.
>>> 
>>> I looked at the log, but it's above my pay grade.
>>> 
>>> Log is here: https://pastebin.com/ncBFApfH <https://pastebin.com/ncBFApfH>
>>> 
>>> A bug report (#56192 <https://trac.macports.org/ticket/56192>) was opened 
>>> on this but closed:  Resolution: → fixed
>>> 
>>> Quite a few ports depend on librsvg:
>>> 
>>> Axe:~ mnewman$ port echo depends:librsvg | wc -l
>>>   65
>>> 
>>> I have no idea what to do next.
>>> 
>>> Mike Newman
>>> Korat, Thailand
>>> 
>>> 
>> 
> 



smime.p7s
Description: S/MIME cryptographic signature

Re: Error: Failed to build librsvg: command execution failed

[Christopher Jones]

That old ticket indeed has nothing to do with the issues here

The rust port does indeed require macports clang (on older systems) to be 
available when building with rustic. However, macOS 10.13 is not one of these 
(at starts with 10.12) so it shouldn’t be needing it.

Please run `port info librsvg rust` and post what that returns.

Chris

> On 13 Oct 2021, at 12:12 pm, Lenore Horner  wrote:
> 
> I’m not sure that’s the same bug (it’s 4 years old too).  That one was not 
> finding rust.  The log you posted says lbrsvg prefers compilers 
> macports-clang- anything from 5.0 up to 12 but then says it’s going to use 
> Xcode Clang (which doesn’t make sense to me but could be just I don’t know 
> enough) and then eventually fails because it can’t find the linker 
> `/opt/local/bin/clang-mp-11`.  I happen to have clang-12 installed via 
> macports and do have /opt/local/bin/clang-mp-12 so I would guess it thinks 
> you have clang-11 installed.  Do you have /opt/local/bin/clang-mp-11?  
> Lenore
> 
>> On Oct 13, 2021, at 02:27, Michael Newman via macports-users 
>> > > wrote:
>> 
>> Old 2010 MacBook Air on: 10.13.6
>> MacPorts: 2.7.1
>> CLTools: 10.1.0.0.1.1539992718
>> 
>> Here's the error:
>> 
>> Error: Failed to build librsvg: command execution failed
>> Error: See 
>> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_librsvg/librsvg/main.log
>>  for details.
>> 
>> I looked at the log, but it's above my pay grade.
>> 
>> Log is here: https://pastebin.com/ncBFApfH 
>> 
>> A bug report (#56192 ) was opened on 
>> this but closed:  Resolution: → fixed
>> 
>> Quite a few ports depend on librsvg:
>> 
>> Axe:~ mnewman$ port echo depends:librsvg | wc -l
>>   65
>> 
>> I have no idea what to do next.
>> 
>> Mike Newman
>> Korat, Thailand
>> 
>> 
> 



smime.p7s
Description: S/MIME cryptographic signature

Re: What is the best way of installing Python's scientific libraries in MacPorts?

[Christopher Jones]

> On 4 Oct 2021, at 9:18 pm, Artemio González López via macports-users 
>  wrote:
> 
>> 
>> On Oct 4, 2021, at 4:24 PM, Giuseppe 'ferdy' Miceli > > wrote:
>> 
>> ciao artemio,
>> 
>>> Hi, Giuseppe,
>> 
>> 
>> 
>>> So my questions are:
>>> 
>>> 1. Should I activate python39 and decativate python37 before installing the 
>>> 3.9 versions fo numpy, scipy and matplotlib?
>> 
>> I would daresay to remove everything (—force option would be handy) and then 
>> start over again from scratch :-)
>> 
>>> Can both be active at the same time after that, or should I keep 3.7 
>>> inactive for good (or unistall it)?
>> 
>> you can have python37 and python39 both installed and active and choose with 
>> port select which one to use as python3 default version.
>> 
>> wabi:macports-ports admin$ port installed python3\*
>> The following ports are currently installed:
>>   python3_select @0.0_2 (active)
>>   python37 @3.7.12_0+optimizations (active)
>>   python39 @3.9.7_0+optimizations (active)
>> wabi:macports-ports admin$ port select --list python3
>> Available versions for python3:
>>  none
>>  python37
>>  python38-apple
>>  python39 (active)
>> wabi:macports-ports admin$
>> 
>> nevertheless imho, being your first try with macports, i would suggest to 
>> choose one version and have it working with a specific version.
>> you will always have time to experimenting with more than one version.
>> 
>>> 2. Should I install (say) py-numpy or more specifically py39-numpy?
>> 
>> from macports perspective that is the same port (more specifically 
>> py39-numpy is a subport of py-numpy.
>> thus if you install py-numpy you shall end up with py39-numpy.
>> 
>>> 3. Is it OK if the 3.7 versions of the py-* package are active throughout 
>>> this installation process (and afterwards), or should I also deactivate 
>>> them?
>> 
>> as i mentioned before i would deactivate/uninstall the python37 versions 
>> just to be double sure.
>> 
>>> 4. Will "jupyter notebook” automatically find the scientific libraries I’m 
>>> going to install, or should I do something else (like, e.g., create an 
>>> environment)?
>> 
>> apologies, on this one i have to surrender since in this case it’s me not 
>> coming from math :-)
>> 
>> my experience with macports makes me think it should work out of the box, 
>> yet that is really above my paygrade. sorry
>> 
>>> Again, I apologize for my ignorance (I’m coming from Mathematica, but I 
>>> would like to try python out because many of my colleagues now use it).
>> 
>> absolutely no need to apologize! i am sure if i were coming with silly 
>> questions on math you would do your best to help me out ;-)
>> 
>> cheers,
>> —
>> ferdy
> 
> Ciao Giuseppe,
> 
> I am happy to report that after following your advice everything worked as 
> advertised. I only experienced a very minor glitch, namely that for some 
> reason (probably a minor bug?) the 
> /opt/local/Library/Frameworks/Versions/3.9/bin directory where jupyter 
> resides is not in the $PATH, so you must add it by hand if you want to invoke 
> (say) jupyter with just its name.

No, that is not a bug but intentional. it is that way because in principle you 
could have multiple versions installed, for different python versions. For that 
reason one specific python version cannot place its binaries under the default 
${prefix}/bin with the nominal names, as that would prevent others from then 
being installed.

The port does in fact install binaries, but they are suffixed with the python 
version

Oberon ~/Projects/MacPorts/ports > port contents py39-jupyter_client | grep bin
  /opt/local/Library/Frameworks/Python.framework/Versions/3.9/bin/jupyter-kernel
  
/opt/local/Library/Frameworks/Python.framework/Versions/3.9/bin/jupyter-kernelspec
  /opt/local/Library/Frameworks/Python.framework/Versions/3.9/bin/jupyter-run
  /opt/local/bin/jupyter-kernel-3.9
  /opt/local/bin/jupyter-kernelspec-3.9
  /opt/local/bin/jupyter-run-3.9


so to run a specific version (for a given python version) run XYZ-3.9 etc.

Chris


> 
> Thanks a lot for your patience and help!
> 
> Artemio
> 
> 
> Artemio Gonzalez Lopez
> artem...@mac.com 


smime.p7s
Description: S/MIME cryptographic signature

Re: What version of Xcode for which macOS ?

[Christopher Jones]

> On 27 Sep 2021, at 8:49 am, Bjarne D Mathiesen  
> wrote:
> 
> This thread led me to search for the relationships between
> * Xcode version
> * macOS / OS X version
> and I couldn't find a table with these
> 
> So far, I've come up with
> 
> Mac OS X / mac OS  | Xcode
> |
> 10.4Tiger   | 2.4.1
> 10.5Leopard | 3.0
> 10.6Snow Leopard| 3.2.2
> 10.7Lion| 4.3.3
> 10.8Mountain Lion   | 5.1.1
> 10.9Maverics| 6.2
> 10.10   Yosemite| 7
> 10.11   El Capitan  | 8.2
> 10.12   Sierra  | 9.2
> 10.13   High Sierra | 10.1
> 10.14   Mojave  | 10.3
> 10.15   Catalina| 12.4
> 11  Big Sur | 13
> 12  Montery |
> 
> Supplements / correction etc are more than welcome
> 
> I do think we really need to have this listed explicitly somewhere


we already do

https://trac.macports.org/wiki/XcodeVersionInfo

> 
> -- 
> 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



smime.p7s
Description: S/MIME cryptographic signature

Re: XCode reinstall command-line tools

[Christopher Jones]

> On 23 Sep 2021, at 1:32 am, Tom  wrote:
> 
> Can’t you simply just ignore that error message?


Generally no. things will start to fail to build if its not addressed. its 
there for a reason...

> 
>> On 22. Sep 2021, at 21:48, Justin Vallon  wrote:
>> 
>> I upgraded XCode, and encountered the "cltversion: The Command Line Tools 
>> are installed, but MacPorts cannot determine the version" error. It linked 
>> to https://trac.macports.org/wiki/ProblemHotlist#reinstall-clt.
>> 
>> That page talks about missing receipts, and downloading the command line 
>> tools manually.
> 



smime.p7s
Description: S/MIME cryptographic signature

Re: learning to trac

[Christopher Jones]

> On 16 Sep 2021, at 8:51 am, Epstein, David via macports-users 
>  wrote:
> 
> 
> Yesterday I submitted a Trac Ticket (my first), and there has been some 
> activity: the Trac system has been keeping me up-to-date with emails.
> 
> I have been unable to find out either from Google or from the various guides 
> issued by Macports:
> 1) How can I add a further comment to the ticket?
> 2) How can I see all the comments in one place. I don’t want to keep looking 
> at different emails.

The answer to both the above is just follow the http link to the ticket in 
question. you will find it in the emails you are getting. 1) also requires you 
to login to trac, which you must be able to do if you created a ticket.




smime.p7s
Description: S/MIME cryptographic signature

Re: gcc<10 on M1 Mac

[Christopher Jones]

Hi,

Its highly unlikely you will ever get support for gcc<10 on arm. We only have 
support for 10 and 11 because we are using unreleased back ports of support 
from a development branch on arm for these two versions. The back port has not 
been done for anything older than 10, and is highly unlikely it ever will.

and yes, gcc5 does require newer libgccX versions. The reason for this is we 
want all gcc versions supported on a given machine to use the same runtime. So 
we make the most recent stable release the primary provider, for libgccN (N 
currently 11) and the older libgccN versions then only provide the additional 
older ABI versions needed for that specific compiler.

Chris

> On 18 Jun 2021, at 4:06 pm, VACCARI FRANCO  wrote:
> 
> I’ve a temporary access to a new MacBook Air with M1 processor, to test on 
> that Mac all our home made programs, mainly fortran. All external packages 
> needed by our workflow were successfully installed (gnuplot, ImageMagick, 
> gmt4 and many others), and I installed gcc11. 
> 
> Such modern compiler complains about some features in our code that are no 
> longer supported, and fails to produce the executable. Of course one day we 
> should update that code, but for the time being, and having to give back that 
> Mac, I wanted to try with an older compiler. I installed gcc10 but that 
> didn’t help.
> 
> I know that gcc8 works with our codes, so I tried to install that but failed.
> 
> The problem is that gcc8 requires libcc9, and that is marked as incompatible.
> 
> % sudo port install gcc8
> --->  Computing dependencies for gcc8
> The following dependencies will be installed: 
> libgcc8
> libgcc9
> Continue? [Y/n]: 
> --->  Fetching archive for libgcc9
> --->  Attempting to fetch libgcc9-9.4.0_0.darwin_20.arm64.tbz2 from 
> https://fra.de.packages.macports.org/libgcc9
> --->  Attempting to fetch libgcc9-9.4.0_0.darwin_20.arm64.tbz2 from 
> http://fco.it.packages.macports.org/libgcc9
> --->  Attempting to fetch libgcc9-9.4.0_0.darwin_20.arm64.tbz2 from 
> https://packages.macports.org/libgcc9
> --->  Fetching distfiles for libgcc9
> Error: gcc9 9.4.0 is not supported on Darwin 20 arm
> Error: Failed to fetch libgcc9: incompatible OS X version
> Error: See 
> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc9/libgcc9/main.log
>  for details.
> Error: Follow https://guide.macports.org/#project.tickets if you believe there
> is a bug.
> Error: Processing of port gcc8 failed
> locadmin@eAir ~ %
> 
> Actually any version from 5 to 9 requires libcc9
> 
> sudo port install gcc5
> --->  Computing dependencies for gcc5
> The following dependencies will be installed: 
> isl18
> libgcc6
> libgcc7
> libgcc8
> libgcc9
> Continue? [Y/n]:
> 
> and therefore fails to install. 
> 
> gcc49 is a different story, as it’s clearly declared unsupported for Xcode 9 
> or greater:
> 
> sudo port install gcc49
> Password:
> --->  Fetching distfiles for gcc49
> Error: building gcc49 is not supported with Xcode 9 or greater
> Error: Failed to fetch gcc49: unsupported platform
> Error: See 
> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc49/gcc49/main.log
>  for details.
> Error: Follow https://guide.macports.org/#project.tickets if you believe there
> is a bug.
> Error: Processing of port gcc49 failed
> 
> Is it really so that gcc9 and earlier will never be compatible with M1 Macs? 
> And why libgcc9 is needed by gcc5?
> 
> Thanks
> 
> Franco
> 
> 



smime.p7s
Description: S/MIME cryptographic signature

Re: cdrtools streamripper

[Christopher Jones]

Please check for an open trac ticket, and if one does not exist open one.

> On 9 Jun 2021, at 9:47 am, Giuseppe Di Matteo  wrote:
> 
> I made the change in the Portfile, but it still won’t install. It seems that 
> the problem is now with the arch arm64 (Mac mini M1).
> Giuseppe Di Matteo
> pinodimat...@me.com <mailto:pinodimat...@me.com>
> 
> 
> 
> 
> 
>> Le 8 juin 2021 à 20:48, Christopher Jones > <mailto:jon...@hep.phy.cam.ac.uk>> a écrit :
>> 
>> 
>> For the smake issue see
>> 
>> https://github.com/macports/macports-ports/commit/9040f7195e114173a42c71ee57e74c248ef7ebb1
>>  
>> <https://github.com/macports/macports-ports/commit/9040f7195e114173a42c71ee57e74c248ef7ebb1>
>> 
>>> On 7 Jun 2021, at 5:15 pm, Andrew Udvare >> <mailto:audv...@gmail.com>> wrote:
>>> 
>>> 
>>>> On 2021-06-07, at 09:34, Giuseppe Di Matteo via macports-users 
>>>> >>> <mailto:macports-users@lists.macports.org>> wrote:
>>>> 
>>>> I can’t install cdrtools and streamripper on macOS 11 (Big Sur).
>>>> 
>>>> Giuseppe Di Matteo
>>>> pinodimat...@me.com <mailto:pinodimat...@me.com>
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>> 
>>> I can reproduce the issue with cdrtools. `smake` does not accept -j.
>>> 
>>> I cannot reproduce the issue with streamripper. streamripper builds for me. 
>>> However, I am on x86-64.
>> 
> 



smime.p7s
Description: S/MIME cryptographic signature

Re: cdrtools streamripper

[Christopher Jones]

For the smake issue see

https://github.com/macports/macports-ports/commit/9040f7195e114173a42c71ee57e74c248ef7ebb1
 


> On 7 Jun 2021, at 5:15 pm, Andrew Udvare  wrote:
> 
> 
>> On 2021-06-07, at 09:34, Giuseppe Di Matteo via macports-users 
>>  wrote:
>> 
>> I can’t install cdrtools and streamripper on macOS 11 (Big Sur).
>> 
>> Giuseppe Di Matteo
>> pinodimat...@me.com
>> 
>> 
>> 
>> 
>> 
>> 
>> 
> 
> I can reproduce the issue with cdrtools. `smake` does not accept -j.
> 
> I cannot reproduce the issue with streamripper. streamripper builds for me. 
> However, I am on x86-64.



smime.p7s
Description: S/MIME cryptographic signature

Re: Telnet not in netutils

[Christopher Jones]

> On 30 May 2021, at 4:09 pm, Christoph Kukulies  wrote:
> 
> No, of course I didn’t read the port notes since I don’t know where one can 
> find them after having done a 
> port install.

You don’t have to find them. They are printed for you when you install the 
port, you just have to pay attention and read them

 > sudo port install inetutils
--->  Computing dependencies for inetutils
--->  Fetching archive for inetutils
--->  Attempting to fetch inetutils-2.0_0+client.darwin_20.x86_64.tbz2 from 
https://packages.macports.org/inetutils
--->  Attempting to fetch inetutils-2.0_0+client.darwin_20.x86_64.tbz2.rmd160 
from https://packages.macports.org/inetutils
--->  Installing inetutils @2.0_0+client
--->  Activating inetutils @2.0_0+client
--->  Cleaning inetutils
--->  Scanning binaries for linking errors
--->  No broken files found. 
--->  No broken ports found.
--->  Some of the ports you installed have notes:
  inetutils has the following notes:
All clients are now installed with the "g” prefix

> Why did they do that (prefixing the utils with a „g“). Is it now a GNU thing?

Its an explicit choice made in the port, to distinguish the GNU versions of 
these utils from the BSD one that come with the OS.

Chris

> 
> Yes, I know that it is insecure and what not, but for local connections like 
> talking to a port of a local process it’s just fine :)
> 
> And I also recalled how to quit the telnet session (on the Mac keyboard): 
> CTRL-ALT-]
> (^]) :)
> 
> 
> 
>> Am 27.05.2021 um 22:04 schrieb Christopher Jones :
>> 
>> Hi,
>> 
>> I guess you didn’t read/notice the port notes when you installed inetutils ?
>> 
>> inetutils has the following notes:
>>   All clients are now installed with the "g" prefix.
>> 
>> Oberon ~/Projects/MacPorts/ports > sudo port contents inetutils | grep telnet
>> /opt/local/bin/gtelnet
>> /opt/local/share/man/man1/gtelnet.1.gz
>> 
>> Chris
>> ]
>>> On 27 May 2021, at 8:57 pm, Christoph Kukulies  wrote:
>>> 
>>> I’m trying to get a telnet installed under macOS 11.3.1. Didn’t have it 
>>> installed before and some reading says it ought to be in netutils,
>>> but it ain’t.
>>> 
>>> Any clues?
>>> 
>>> —
>>> Christoph
>>> 
>> 
> 



smime.p7s
Description: S/MIME cryptographic signature

Re: Telnet not in netutils

[Christopher Jones]

Hi,

I guess you didn’t read/notice the port notes when you installed inetutils ?

  inetutils has the following notes:
All clients are now installed with the "g" prefix.

Oberon ~/Projects/MacPorts/ports > sudo port contents inetutils | grep telnet
  /opt/local/bin/gtelnet
  /opt/local/share/man/man1/gtelnet.1.gz

Chris
]
> On 27 May 2021, at 8:57 pm, Christoph Kukulies  wrote:
> 
> I’m trying to get a telnet installed under macOS 11.3.1. Didn’t have it 
> installed before and some reading says it ought to be in netutils,
> but it ain’t.
> 
> Any clues?
> 
> —
> Christoph
> 



smime.p7s
Description: S/MIME cryptographic signature

Re: MacPorts 2.7.0 Warning

[Christopher Jones]

>> 
>> What is the output of:
>> 
>> grep -F universal_arch /opt/local/etc/macports/macports.conf
>> 
>> ?
>> 
>> Are you on an M1 system?
>> 
>> The default setting is "arm64 x86_64" (without quotes). You can comment out 
>> the universal_archs line with # to get the default.
> 
> The output of the grep command is "universal_archsx86_64”. I am 
> not on an M1 system (I have a 2017 MacBook).

You must have changed that at some point, as that is not the default. The 
easiest fix is to edit /opt/local/etc/macports/macports.conf and comment out 
that setting, and thus fallback to the (correct) defaults.

Chris

smime.p7s
Description: S/MIME cryptographic signature

Re: [Xfig hangs on start]

[Christopher Jones]

Hi,

fig is an X11 application, and thuis requires an X11 server to be installed to 
work. Do you have one installed ? If you are not sure run

sudo port install xorg-server 

and follow the instructions at the end to log out and back in again, and then 
retry running xfig.

Chris

> On 17 May 2021, at 8:20 am, Maxim Abalenkov  wrote:
> 
> Dear all,
> 
> How are you? I need help launching Xfig @ macOS BigSur 11.3.1. Yesterday I 
> installed the Xfig port (xfig @3.2.8a_0). It installed successfully. But when 
> I try to launch it from the terminal it hangs. Nothing happens. Would you 
> please help me to find the problem? I tried to “clean" the port and install 
> it again, but it didn’t help. Thank you and have a good day ahead!
> 
> —
> Best wishes,
> Maxim
> 
> Maxim Abalenkov \\ maxim.abalen...@gmail.com 
> 
> +44 7 486 486 505 \\ http://mabalenk.gitlab.io 


smime.p7s
Description: S/MIME cryptographic signature

Re: Is it possible to install Julia on M1 Mac?

[Christopher Jones]

OK, I have no idea if julia itself supports Arm yet.

I suggest you search for tickets against julia at

https://trac.macports.org 

and if not submit one.

Chris

> On 7 May 2021, at 2:01 pm,   
> wrote:
> 
> With gcc10 installation fails as well:
> 
> :info:build 
> ===
> :info:build   ERROR: sha512 checksum failure on 
> LibGit2.v1.2.3+0.aarch64-apple-darwin.tar.gz, should be:
> :info:build   
> cf83e1357eefb8bdf1542850d66d8007d620e4050b5715dc83f4a921d36ce9ce
> :info:build   
> 47d0d13c5d85f2b0ff8318d2877eec2f63b931bd47417a81a538327af927da3e
> :info:build   But `shasum -a 512 
> /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_julia/julia/work/julia-1.6.1/deps/srccache/LibGit2.v1.2.3+0.aarch64-apple-darwin.tar.gz
>  | awk '{ print $1; }'` results in:
> :info:build   
> aff23e9d56827be54d8f515489eed92d9cb4d9a1b69c12bbee44fa1343ebc906
> :info:build   
> b38b082c11e6ecb227d256de5cba19b2f3a03c022b88809a33c225c34db08f7c
> :info:build   This can happen due to bad downloads or network proxies, please 
> check your
> :info:build   network proxy/firewall settings and delete
> :info:build   
> /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_julia/julia/work/julia-1.6.1/deps/srccache/LibGit2.v1.2.3+0.aarch64-apple-darwin.tar.gz
> :info:build   to force a redownload when you are ready
> :info:build 
> ===
> :info:build make[1]: *** 
> [/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_julia/julia/work/julia-1.6.1/usr/manifest/libgit2]
>  Error 2
> :info:build make[1]: *** Waiting for unfinished jobs
> 
> I tried to delete the corrupted file but the second install attempt was with 
> the same result.
> 
> Petr
> 
> __
>> Od: "Chris Jones" 
>> Komu: "Andrew Rohl" 
>> Datum: 07.05.2021 14:22
>> Předmět: Re: Is it possible to install Julia on M1 Mac?
>> 
>> CC: 
>> Hi,
>> 
>> Whilst the statement that the devel version of gcc was correct at the time 
>> it was made, gcc10 now has had support back ported. So I suggest you force 
>> uninstall libgcc-devel and let libgcc10 get installed in its place.
>> 
>> Chris
>> 
>>> On 7 May 2021, at 12:37 pm, Andrew Rohl  wrote:
>>> 
>>> I have installed gcc-devel as I was told that it is the only version that 
>>> can be compiled on the M1.
>>> 
>>> Then tried to install Julia:
>>> 
 sudo port install julia
 
 
 --->  Computing dependencies for julia
 Error: Can't install libgcc10 because conflicting ports are active: 
 libgcc-devel
 Error: Follow https://guide.macports.org/#project.tickets to report a bug.
 Error: Processing of port Julia failed
>>> 
>>> Is there any way to install Julia?
>>> 
>>> Many thanks
>>> 
>>> Andrew
>> 
>> 
>> 



smime.p7s
Description: S/MIME cryptographic signature

Re: Issue compiling simple code with clang++-mp-11

[Christopher Jones]

See

https://trac.macports.org/ticket/62770 

Its the macOS11.3 / Xcode 12.5 update, it has broken all MacPorts clang 
versions <= 11

At this time the only macports clang that works is the clang-level port.

Chris

> On 3 May 2021, at 1:14 pm, Andrew Udvare  wrote:
> 
> This code compiles fine with Xcode but fails with Clang from MacPorts. I have 
> not been able to figure out why. I successfully rebuilt Clang and LLVM from 
> source but it made no difference.
> 
> Setup:
> 
> macOS 11.3 20E232 x86_64
> Xcode 12.5 12E262
> 
> The code (main.cpp):
> 
> #include 
> int main(int argc, char *argv[]) {
>  std::filesystem::path p(argv[0]);
>  return p.string().length();
> }
> 
> $ xcrun clang++ -std=c++17 main.cpp
> # No errors
> 
> Anyone know why it would fail with MacPorts' Clang? Seems to be an include 
> path/file issue.
> 
> $ /opt/local/bin/clang++-mp-11 -std=c++17 main.cpp -ferror-limit=2
> In file included from main.cpp:1:
> In file included from 
> /opt/local/libexec/llvm-11/bin/../include/c++/v1/filesystem:234:
> In file included from 
> /opt/local/libexec/llvm-11/bin/../include/c++/v1/cstdlib:85:
> /opt/local/libexec/llvm-11/bin/../include/c++/v1/stdlib.h:142:34: error: 
> unknown type name 'ldiv_t'
> inline _LIBCPP_INLINE_VISIBILITY ldiv_t div(long __x, long __y) _NOEXCEPT {
> ^
> /opt/local/libexec/llvm-11/bin/../include/c++/v1/stdlib.h:143:12: error: no 
> member named 'ldiv' in the global namespace
>  return ::ldiv(__x, __y);
> ~~^
> fatal error: too many errors emitted, stopping now [-ferror-limit=]
> 3 errors generated.
> 
> This generates a lot of errors that are members are missing from the global 
> namespace.
> 
> This affects this port I have had working for a while, probably by accident 
> because it wasn't until recently that Xcode Clang and MacPorts Clang versions 
> mismatched their highest numbers (Xcode 12.5 having Clang 12, MacPorts having 
> up to 11).
> 
> https://github.com/Tatsh/ports/blob/ycm-fixes/devel/ycmd/Portfile
> 
> This project tries to compile this code within CMake to test for required 
> arguments, but it's failing for the reason above rather than actually missing 
> filesystem implementation. See 
> https://github.com/ycm-core/ycmd/blob/master/cpp/ycm/CMakeLists.txt#L279
> 
> -- 
> Andrew Udvare
> 
> 



smime.p7s
Description: S/MIME cryptographic signature

Re: Blimey, but that was a huge update...

[Christopher Jones]

> 
> Looks like a good chunk was recompiled, the major culprits being LLVM and GCC 
> and friends.
> 
> Are there no longer any binaries for Sierra?  

No, they are still being produced when possible, as for all other OSes. See

https://build.macports.org/waterfall 

http://packages.macports.org 

( add /port-name to the end of that last url to look up any port of interest )

Chris

smime.p7s
Description: S/MIME cryptographic signature

Re: QEMU GUI

[Christopher Jones]

> On 25 Apr 2021, at 11:55 am, FritzS - gmx  wrote:
> 
> Why QEMU GUI are not available?
> 
> https://sourceforge.net/projects/qemu-gui/

… because no one has been interested to submit a GitHub PR implementation them.

Please feel free to do so

https://guide.macports.org/chunked/project.contributing.html

smime.p7s
Description: S/MIME cryptographic signature

Re: Binary archive for mpich-default is available but not used

[Christopher Jones]

HI,

It is expected. See

https://github.com/macports/macports-ports/blob/7541d508815705d370fbe619b3a407e30963edf1/science/mpich/Portfile#L220
 


A message at that point might be informative I guess…

Chris

> On 24 Apr 2021, at 9:42 am, Davide Liessi  wrote:
> 
> Hi.
> 
> I'm trying to install mpich-default with default variants on macOS 10.13.6.
> The package is available at http://packages.macports.org/mpich-default/
> but port is refusing to install from the prebuilt binary.
> 
> $ sudo port -b install mpich-default
> --->  Computing dependencies for mpich-default
> Error: Failed to archivefetch mpich-default: Binary-only mode
> requested with no usable archive sites configured
> Error: See 
> /opt/local/var/macports/logs/_opt_macports-git_macports-ports_science_mpich/mpich-default/main.log
> for details.
> Error: Follow https://guide.macports.org/#project.tickets to report a bug.
> Error: Processing of port mpich-default failed
> 
> main.log attached, but I cannot see anything meaningful in there with
> respect to this problem.
> 
> I have just updated many other ports in binary-only mode without any problems.
> Any ideas?
> 
> Thanks and best wishes.
> Davide
> 



smime.p7s
Description: S/MIME cryptographic signature

Re: Error: Failed to configure boost

[Christopher Jones]

Python 2.7 is no longer the default variant with boost, and your log shows you 
are still using this.

> sudo port sync
> sudo port -f uninstall boost
> sudo ports install boost

As others have said, the best way to avoid issues like this is to not leave 
things too long between port updates.

> On 23 Apr 2021, at 3:48 pm, tom eee  wrote:
> 
> I got the following error message while doing sudo port upgrade outdated:
> 
> Error: Failed to configure boost: configure failure: command execution failed
> 
> OS X 10.7.5
> Mac Mini mid-2011
> 
> main.log is attached.
> 
> Thank you,
> Tom
> 
> 



smime.p7s
Description: S/MIME cryptographic signature

Re: Trying to get macports running on my new M1 MacBook Air

[Christopher Jones]

> --->  Fetching distfiles for libgcc10
> Error: gcc10 10.3.0 is not supported on Darwin 20 arm

> Error: Failed to fetch libgcc10: incompatible OS X version
> Error: See 
> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc10/libgcc10/main.log
>  for details.
> Error: Follow https://guide.macports.org/#project.tickets 
>  to report a bug.
> Error: Processing of port gcc9 failed
> 
> Seems odd to me that gcc9 needs libgcc10.

This is correct. I could explain why (its a nuance of how we ensure a 
compatible single runtime environment for all support gcc versions, but its not 
relevant here so I won’t go into that any more).

> 
> Not sure if these two are related but anyone have any idea what the problem 
> might be?

The answer is above

Error: gcc10 10.3.0 is not supported on Darwin 20 arm

No currently released gcc version supports Apple arm. For now the only version 
you can use is the port gcc-devel’ which has experimental support…

Chris



smime.p7s
Description: S/MIME cryptographic signature

Re: -march arm64

[Christopher Jones]

No released version of GCC supports Apple M1 machines. You need to use the 
gcc-devel port for now, which provides  developmental snapshot build with 
(experimental) support.


> On 21 Apr 2021, at 6:07 pm, Tom  wrote:
> 
> Hi,
> 
> gcc does not seem to support -arch arm64
> Can ti be build with arm64 support?
> 
> Regards



smime.p7s
Description: S/MIME cryptographic signature

Re: Update on Big Sur Problems

[Christopher Jones]

https://packages.macports.org/atlas
> --->  Attempting to fetch atlas-3.10.2_2.darwin_20.arm64.tbz2 from 
> https://cph.dk.packages.macports.org/atlas
> --->  Attempting to fetch atlas-3.10.2_2.darwin_20.arm64.tbz2 from 
> https://lil.fr.packages.macports.org/atlas
> --->  Fetching distfiles for atlas
> --->  Verifying checksums for atlas
> --->  Extracting atlas
> --->  Applying patches to atlas
> --->  Configuring atlas
> Selected C compiler: /usr/bin/clang
> Selected F77 compiler: gfortran5
> Warning: reinplace s|-no-cpp-precomp||g didn't change anything in 
> /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_math_atlas/atlas/work/ATLAS/CONFIG/src/atlcomp.txt
> Error: Failed to configure atlas: sysctl failed: No such file or directory
> Error: See 
> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_math_atlas/atlas/main.log
>  for details.
> Error: Follow https://guide.macports.org/#project.tickets to report a bug.
> Error: Processing of port atlas failed
> 
> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_math_atlas/atlas/main.log
> is not very long I attached it
> 
> Petr
> 
> __
>> Od: "Christopher Jones" 
>> Komu: "Lenore Horner" 
>> Datum: 18.04.2021 16:13
>> Předmět: Re: Update on Big Sur Problems
>> 
>> CC: 
>> 
>> yes…
>> 
>> Your build is not being done from a clean start. Do
>> 
>> sudo port clean atlas
>> sudo port install atlas
>> 
>> Chris
>> 
>>> On 18 Apr 2021, at 2:49 pm, Lenore Horner  
>>> wrote:
>>> I think that just means you need to clean and then retry.
>>>> On Apr 18, 2021, at 09:17, petr.2...@centrum.cz wrote:
>>>> I tried also:
>>>> pmm:~ pet$ sudo port install atlas -gcc5
>>>> Password:
>>>> Error: Requested variants "" do not match those the build was started 
>>>> with: "+gcc5".
>>>> Error: Please use the same variants again, or run 'port clean atlas' first 
>>>> to remove the existing partially completed build.
>>>> Error: Follow https://guide.macports.org/#project.tickets to report a bug.
>>>> Error: Processing of port atlas failed
>>>> pmm:~ pet$ sudo port clean atlas
>>>> --->  Cleaning atlas
>>>> pmm:~ pet$ sudo port install atlas -gcc5
>>>> Warning: The macOS 11.2 SDK does not appear to be installed. Ports may not 
>>>> build correctly.
>>>> Warning: You can install it as part of the Xcode Command Line Tools 
>>>> package by running `xcode-select --install'.
>>>> --->  Fetching archive for atlas
>>>> --->  Attempting to fetch atlas-3.10.2_2.darwin_20.arm64.tbz2 from 
>>>> https://packages.macports.org/atlas
>>>> --->  Attempting to fetch atlas-3.10.2_2.darwin_20.arm64.tbz2 from 
>>>> https://cph.dk.packages.macports.org/atlas
>>>> --->  Attempting to fetch atlas-3.10.2_2.darwin_20.arm64.tbz2 from 
>>>> https://lil.fr.packages.macports.org/atlas
>>>> --->  Fetching distfiles for atlas
>>>> --->  Attempting to fetch atlas3.10.2.tar.bz2 from 
>>>> https://distfiles.macports.org/atlas
>>>> --->  Attempting to fetch lapack-3.6.0.tgz from 
>>>> https://distfiles.macports.org/atlas --->  Verifying checksums for atlas   
>>>>        --->  Extracting atlas
>>>> --->  Applying patches to atlas
>>>> --->  Configuring atlas
>>>> Selected C compiler: /usr/bin/clang
>>>> Selected F77 compiler: gfortran5
>>>> Warning: reinplace s|-no-cpp-precomp||g didn't change anything in 
>>>> /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_math_atlas/atlas/work/ATLAS/CONFIG/src/atlcomp.txt
>>>> Error: Failed to configure atlas: sysctl failed: No such file or directory
>>>> Error: See 
>>>> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_math_atlas/atlas/main.log
>>>>  for details.
>>>> Error: Follow https://guide.macports.org/#project.tickets to report a bug.
>>>> Error: Processing of port atlas failed
>>>> __
>>&g

Re: Update on Big Sur Problems

[Christopher Jones]

yes…

Your build is not being done from a clean start. Do

sudo port clean atlas
sudo port install atlas

Chris

> On 18 Apr 2021, at 2:49 pm, Lenore Horner  wrote:
> 
> I think that just means you need to clean and then retry.
> 
>> On Apr 18, 2021, at 09:17, petr.2...@centrum.cz wrote:
>> 
>> I tried also:
>> 
>> pmm:~ pet$ sudo port install atlas -gcc5
>> Password:
>> Error: Requested variants "" do not match those the build was started with: 
>> "+gcc5".
>> Error: Please use the same variants again, or run 'port clean atlas' first 
>> to remove the existing partially completed build.
>> Error: Follow https://guide.macports.org/#project.tickets to report a bug.
>> Error: Processing of port atlas failed
>> pmm:~ pet$ sudo port clean atlas
>> --->  Cleaning atlas
>> pmm:~ pet$ sudo port install atlas -gcc5
>> Warning: The macOS 11.2 SDK does not appear to be installed. Ports may not 
>> build correctly.
>> Warning: You can install it as part of the Xcode Command Line Tools package 
>> by running `xcode-select --install'.
>> --->  Fetching archive for atlas
>> --->  Attempting to fetch atlas-3.10.2_2.darwin_20.arm64.tbz2 from 
>> https://packages.macports.org/atlas
>> --->  Attempting to fetch atlas-3.10.2_2.darwin_20.arm64.tbz2 from 
>> https://cph.dk.packages.macports.org/atlas
>> --->  Attempting to fetch atlas-3.10.2_2.darwin_20.arm64.tbz2 from 
>> https://lil.fr.packages.macports.org/atlas
>> --->  Fetching distfiles for atlas
>> --->  Attempting to fetch atlas3.10.2.tar.bz2 from 
>> https://distfiles.macports.org/atlas
>> --->  Attempting to fetch lapack-3.6.0.tgz from 
>> https://distfiles.macports.org/atlas 
>> --->  Verifying checksums for atlas  
>> 
>> --->  Extracting atlas
>> --->  Applying patches to atlas
>> --->  Configuring atlas
>> Selected C compiler: /usr/bin/clang
>> Selected F77 compiler: gfortran5
>> Warning: reinplace s|-no-cpp-precomp||g didn't change anything in 
>> /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_math_atlas/atlas/work/ATLAS/CONFIG/src/atlcomp.txt
>> Error: Failed to configure atlas: sysctl failed: No such file or directory
>> Error: See 
>> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_math_atlas/atlas/main.log
>>  for details.
>> Error: Follow https://guide.macports.org/#project.tickets to report a bug.
>> Error: Processing of port atlas failed
>> 
>> 
>> __
>>> Od: petr.2...@centrum.cz
>>> Komu: "Christopher Jones" 
>>> Datum: 18.04.2021 15:13
>>> Předmět: Re: Update on Big Sur Problems
>>> 
>>> CC: 
>>> pmm:~ pet$ port info atlas
>>> atlas @3.10.2_2 (math)
>>> Variants: gcc49, [+]gcc5, mpclang37, nofortran, universal
>>> 
>>> Description:  Provides a complete BLAS and LAPACK API.
>>>   ATLAS achieves performance on par with machine-specific 
>>> tuned libraries.
>>> Homepage: http://math-atlas.sourceforge.net/
>>> 
>>> Build Dependencies:   gcc5
>>> Library Dependencies: libgcc, libgcc6
>>> Platforms:darwin
>>> License:  BSD
>>> Maintainers:      Email: vi...@macports.org, GitHub: Veence
>>> pmm:~ pet$ port rdeps atlas
>>> The following ports are dependencies of atlas @3.10.2_2+gcc5:
>>> gcc5
>>> xz
>>>   libiconv
>>> gperf
>>>   gettext
>>> ncurses
>>> cctools
>>> gmp
>>> isl18
>>> ld64
>>>   ld64-xcode
>>> zlib
>>> libmpc
>>>   mpfr
>>> gcc_select
>>> libgcc6
>>>   isl
>>>   libgcc7
>>> libgcc8
>>>   libgcc9
>>> libgcc
>>>   libgcc10
>>> pmm:~ pet$ 
>>> 
>>> 
>>> __
>>>> Od: "Christopher Jones" 
>>>> Komu: petr.2...@centrum.cz
>>>> Datum: 18.04.2021 14:34
>>>> Předmět: Re: Update on Big Sur Problems
>>>> 
>>>> CC: >>> james.se...@gmail.com>
>>>> 
>>>> So the issue is with atlas, it is forcing the use of gcc5, which will 
>>>> never work 

Re: Update on Big Sur Problems

[Christopher Jones]

So the issue is with atlas, it is forcing the use of gcc5, which will never 
work on M1 machines.

please run

port info atlas
port rdeps atlas

I am not sure why you get

 atlas
   gcc5
 isl18
 libgcc6
   libgcc7
 libgcc8
   libgcc9
 libgcc
   libgcc10

below, as on my Intel macOS11 machine I don’t see this in the dep tree for atlas

Oberon ~/Projects/MacPorts/ports > port info atlas 
atlas @3.10.2_2 (math)
Variants: gcc49, gcc5, mpclang37, nofortran

Description:  Provides a complete BLAS and LAPACK API.
  ATLAS achieves performance on par with machine-specific 
tuned libraries.
Homepage: http://math-atlas.sourceforge.net/

Extract Dependencies: lbzip2
Platforms:darwin
License:  BSD
Maintainers:  Email: vi...@macports.org, GitHub: Veence
Oberon ~/Projects/MacPorts/ports > port rdeps atlas
The following ports are dependencies of atlas @3.10.2_2:
  lbzip2

Are you perhaps forcing the use of a gcc5 variant in some way ?

Please check trac for an existing ticket against atlas, and if it does not 
exist create one.

In the meantime I suggest you try without using the atlas variant.

Chris

> On 18 Apr 2021, at 12:25 pm,   
> wrote:
> 
> Hi,
> 
> pmm:~ pet$ port info sundials2 +atlas
> sundials2 @2.7.0_3 (math, devel)
> Variants: accelerate, +atlas, clang11, clangdevel, debug, doc, 
> examples, g95, gccdevel, [+]gfortran,
>  [+]mpich, openblas, openmpi, universal
> 
> Description:  SUNDIALS consists of the following five solvers: CVODE 
> solves initial value problems for ordinary
>  differential equation (ODE) systems. CVODES solves ODE 
> systems and includes sensitivity analysis
>  capabilities (forward and adjoint). IDA solves initial 
> value problems for differential-algebraic
>  equation (DAE) systems. IDAS solves DAE systems and 
> includes sensitivity analysis capabilities
>  (forward and adjoint). KINSOL solves nonlinear algebraic 
> systems.
> Homepage: https://computing.llnl.gov/projects/sundials
> 
> Build Dependencies:   cmake, gcc-devel
> Library Dependencies: SuiteSparse_KLU, libgcc-devel, mpich-default, atlas
> Conflicts with:   sundials
> Platforms:darwin
> License:  BSD
> Maintainers:  none
> 
> pmm:~ pet$ port rdeps sundials2 +atlas
> The following ports are dependencies of sundials2 
> @2.7.0_3+atlas+gfortran+mpich:
>  cmake
>libcxx
>  xz
>libiconv
>  gperf
>gettext
>  ncurses
>curl
>  pkgconfig
>  libidn2
>libunistring
>  perl5
>perl5.28
>  db48
>  gdbm
>readline
>  texinfo
>help2man
>  p5.28-locale-gettext
>perl5.30
>  autoconf
>m4
>  automake
>  libtool
>xattr
>  unzip
>  libpsl
>python39
>  bzip2
>  expat
>  libedit
>  libffi
>expect
>  tcl
>dejagnu
>  openssl
>zlib
>  sqlite3
>  python_select
>  python3_select
>glib2
>  libxml2
>icu
>  pcre
>  zstd
>lz4
>  curl-ca-bundle
>libarchive
>  lzo2
>libuv
>  gcc-devel
>cctools
>gmp
>isl
>ld64
>  ld64-xcode
>libmpc
>  mpfr
>gcc_select
>libgcc-devel
>  SuiteSparse_KLU
>SuiteSparse_config
>SuiteSparse_AMD
>SuiteSparse_BTF
>SuiteSparse_COLAMD
>  mpich-default
>mpi_select
>mpi-doc
>  atlas
>gcc5
>  isl18
>  libgcc6
>libgcc7
>  libgcc8
>libgcc9
>  libgcc
>    libgcc10
> pmm:~ pet$ 
> 
> ps: without +atlas  sundials2 installs successfully
> 
> pmm:~ pet$ uname -a
> Darwin pmm.local 20.3.0 Darwin Kernel Version 20.3.0: Thu Jan 21 00:06:51 PST 
> 2021; root:xnu-7195.81.3~1/RELEASE_ARM64_T8101 arm64
> 
> Petr
> 
> 
> __
>> Od: "Christopher Jones" 
>> Komu: petr.2...@centrum.cz
>> Datum: 18.04.2021 13:08
>> Předmět: Re: Update on Big Sur Problems
>> 
>> CC: > james.se...@gmail.com>
>> Hi,
>> 
>> Any port that forces the use of gcc10 or older on M1 macs cannot work, as 
>> these gcc versions are never going to be suppo

Re: Update on Big Sur Problems

[Christopher Jones]

Hi,

Any port that forces the use of gcc10 or older on M1 macs cannot work, as these 
gcc versions are never going to be supported on these machines. Even gcc11 
support seems unlikely at this time, so for a while gccdevel is likely going to 
be the only supported version on these machines, which currently uses a special 
fork of the gcc mainline by the primary Darwin maintainer with experimental M1 
support.

However, ports using the compilers PG should automatically use gccdevel, so we 
need to see why the port below is trying to install libgcc9, as this is 
incorrect. Please show what

port info sundials2 +atlas

and

port rdeps sundials2 +atlas

Finally, if you want this to get fixed you need to follow the final 
instructions below and submit a trac ticket for the issue.

Chris

> On 18 Apr 2021, at 11:40 am, petr.2...@centrum.cz wrote:
> 
> Hello,
> 
> I run "sudo port selfupdate" and "sudo port upgrade outdated" occasionally 
> and I see that there are updates and improvements. Which is nice.
> 
> Yes,  gcc-devel  is pulled by default, it includes fortran and it seems to 
> work.
> 
> However I am experiencing problems with some packages which need other 
> version which is ether not available for arm64 or it is conflict with  
> gcc-devel .
> 
> Just as an example, I tried to install cantera and it wants sundials2 +atlas
> but :
> 
> sudo port install sundials2 +atlas
> Warning: The macOS 11.2 SDK does not appear to be installed. Ports may not 
> build correctly.
> Warning: You can install it as part of the Xcode Command Line Tools package 
> by running `xcode-select --install'.
> --->  Computing dependencies for sundials2
> Error: Can't install libgcc9 because conflicting ports are active: 
> libgcc-devel
> Error: Follow https://guide.macports.org/#project.tickets to report a bug.
> Error: Processing of port sundials2 failed
> 
> And I am finished at this point.
> 
> Petr
> 
> 
> __
>> Od: "Marius Schamschula" 
>> Komu: "MacPorts Users" 
>> Datum: 17.04.2021 20:50
>> Předmět: Re: Update on Big Sur Problems
>> 
>> James,
>> 
>> gcc-devel works fine on M1 macs. E.g. I’ve used it to install octave.
>> 
>>> On Apr 17, 2021, at 1:05 PM, James Secan  wrote:
>>> 
>>> I just checked the MacPorts wiki page for Big Sur problems and noted that 
>>> it hasn’t been updated for three months (at least that’s what the wiki page 
>>> says).  With the possibility that new M1 iMacs might show up soon can you 
>>> provide a short update on where things stand vis-a-vis Big Sur and M1-based 
>>> Macs?  I’m most interested in where things stand on the gcc compiler 
>>> package (gfortran in particular).
>>> 
>>> Thanks.
>>> Jim
>>> Seattle, WA
>> 
>> Marius
>> --
>> Marius Schamschula
>> 
>> 
>> 
>> 
>> 
>> 
>> Marius
>> --
>> Marius Schamschula
>> 
>> 
>> 
>> 
>> 
>> 



smime.p7s
Description: S/MIME cryptographic signature

Re: Getting python3.8 with macports

[Christopher Jones]

Just like how you would install any other port...

> sudo port install python38

gives the latest python 3.8

or

> sudo port install python39

for the latest in the 3.9 series.

> On 16 Apr 2021, at 3:47 pm, Christoph Kukulies  wrote:
> 
> How can I upgrade to the latest version of python (python 3.8.x)?
> Or should I use conda or something else?
> 
> —
> Christoph
> 



smime.p7s
Description: S/MIME cryptographic signature

Re: Messed with a binary in /usr/local/bin

[Christopher Jones]

Hi,

> On 16 Apr 2021, at 3:46 pm, Christoph Kukulies  wrote:
> 
> I messed up my macports structure a bit. 
> While I was in need of a newer tidy (tidy-html5) I deleted 
> /usr7local/bin/tidy (which is the macports binary if I’m correct).

No, it is not from MacPorts. MacPorts (by default) installs to /opt/local.

Something else installed that binary into /usr/include, assuming you didn’t 
manually configure MacPorts to install there, which wouldn’t be a good idea.

Chris

> How can I „repair“ this situation using some macports command, maybe 
> something like —force?
> 
> 
> Christoph Kukulies
> 
> 
> 
> 



smime.p7s
Description: S/MIME cryptographic signature

Re: gfortran for M1?

[Christopher Jones]

sorry… auto text correction turned ‘xcrun’ into ’scrub’….

> On 20 Mar 2021, at 3:50 pm, Christopher Jones  
> wrote:
> 
> Hi,
> 
> You probably need to specify the SDK location. There are a number ways you 
> can do this, gcc now supports the same mechanisms as clang. i.e. using scrub 
> or setting SDKROOT .
> I personally have
> 
> export SDKROOT=`xcrun --show-sdk-path`
> in my shell profile for this very reason.
> 
> Chris
> 
>> On 20 Mar 2021, at 2:59 pm, petr.2...@centrum.cz wrote:
>> 
>> Thank you Marius,
>> 
>> it did not help. I also reboot the machine.
>> Now I am getting:
>> 
>> ld: library not found for -lm
>> collect2: error: ld returned 1 exit status
>> 
>> I am not sure whether the message from collect2 was there before running 
>> sudo port select gcc mp-gcc-devel.
>> 
>> I am using bash, but in default zsh it behaves the same.
>> 
>> pmm:work pet$ env
>> SHELL=/bin/zsh
>> XPC_FLAGS=0x0
>> TERM_PROGRAM_VERSION=440
>> __CFBundleIdentifier=com.apple.Terminal
>> SSH_AUTH_SOCK=/private/tmp/com.apple.launchd.SMYfudJeEJ/Listeners
>> TERM_SESSION_ID=1AAB1E17-A7F0-4363-9F82-6F387012CAC1
>> PWD=/Users/pet/work
>> LOGNAME=pet
>> HOME=/Users/pet
>> TMPDIR=/var/folders/tk/dp822xl925n937bzfkc1t6v0gn/T/
>> TERM=xterm-256color
>> USER=pet
>> DISPLAY=/private/tmp/com.apple.launchd.EJPRpCSOgP/org.macports:0
>> SHLVL=1
>> XPC_SERVICE_NAME=0
>> LC_CTYPE=UTF-8
>> LC_COLLATE=C
>> PATH=/opt/local/bin:/opt/local/sbin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Library/Apple/usr/bin
>> OLDPWD=/Users/pet
>> TERM_PROGRAM=Apple_Terminal
>> _=/usr/bin/env
>> 
>> Petr
>> 
>> 
>> __
>>> Od: "Marius Schamschula" 
>>> Komu: "Gerben Wierda via macports-users" 
>>> Datum: 20.03.2021 15:24
>>> Předmět: Re: gfortran for M1?
>>> 
>>> Petr,
>>> 
>>> sudo port select gcc mp-gcc-devel
>>> 
>>> will add links so that the binaries, includes and libraries can be found.
>>> 
>>>> On Mar 20, 2021, at 8:59 AM,   
>>>> wrote:
>>>> 
>>>> Thank you Chris,
>>>> 
>>>> I found gfortran-mp-devel in /opt/local/bin.
>>>> 
>>>> However trying to compile my source a got linker error:
>>>> ld: library not found for -lm
>>>> 
>>>> And I am lost again. I did not specified any linker options,
>>>> just compiler options:
>>>> -g -fbounds-check -ffpe-trap=invalid,zero,overflow 
>>>> -ffpe-summary=invalid,zero,overflow -fno-sign-zero -fno-automatic 
>>>> -Wuninitialized
>>>> 
>>>> (Sorry for beginner question. Google did not help.)
>>>> 
>>>> Petr
>>>> 
>>>> __
>>>>> Od: "Chris Jones" 
>>>>> Komu: petr.2...@centrum.cz
>>>>> Datum: 20.03.2021 14:04
>>>>> Předmět: Re: gfortran for M1?
>>>>> 
>>>>> CC: 
>>>>> Hi,
>>>>> 
>>>>> Gcc-devel provides gfortran for M1 machines by default.
>>>>> 
>>>>> Chris
>>>>> 
>>>>>> On 20 Mar 2021, at 1:01 pm, petr.2...@centrum.cz wrote:
>>>>>> 
>>>>>> Is it already possible to install gfortran on M1?
>>>>>> It seems that gcc-devel does not have +gfortran variant and and other 
>>>>>> gcc versions are not compatible. 
>>>>>> Thank you, 
>>>>>> Petr
>>>>> 
>>>>> 
>>>>> 
>>> 
>>> Marius
>>> --
>>> Marius Schamschula
>>> 
>>> 
>>> 
> 



smime.p7s
Description: S/MIME cryptographic signature

Re: gfortran for M1?

[Christopher Jones]

Hi,

You probably need to specify the SDK location. There are a number ways you can 
do this, gcc now supports the same mechanisms as clang. i.e. using scrub or 
setting SDKROOT .
I personally have

export SDKROOT=`xcrun --show-sdk-path`
in my shell profile for this very reason.

Chris

> On 20 Mar 2021, at 2:59 pm, petr.2...@centrum.cz wrote:
> 
> Thank you Marius,
> 
> it did not help. I also reboot the machine.
> Now I am getting:
> 
> ld: library not found for -lm
> collect2: error: ld returned 1 exit status
> 
> I am not sure whether the message from collect2 was there before running 
> sudo port select gcc mp-gcc-devel.
> 
> I am using bash, but in default zsh it behaves the same.
> 
> pmm:work pet$ env
> SHELL=/bin/zsh
> XPC_FLAGS=0x0
> TERM_PROGRAM_VERSION=440
> __CFBundleIdentifier=com.apple.Terminal
> SSH_AUTH_SOCK=/private/tmp/com.apple.launchd.SMYfudJeEJ/Listeners
> TERM_SESSION_ID=1AAB1E17-A7F0-4363-9F82-6F387012CAC1
> PWD=/Users/pet/work
> LOGNAME=pet
> HOME=/Users/pet
> TMPDIR=/var/folders/tk/dp822xl925n937bzfkc1t6v0gn/T/
> TERM=xterm-256color
> USER=pet
> DISPLAY=/private/tmp/com.apple.launchd.EJPRpCSOgP/org.macports:0
> SHLVL=1
> XPC_SERVICE_NAME=0
> LC_CTYPE=UTF-8
> LC_COLLATE=C
> PATH=/opt/local/bin:/opt/local/sbin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Library/Apple/usr/bin
> OLDPWD=/Users/pet
> TERM_PROGRAM=Apple_Terminal
> _=/usr/bin/env
> 
> Petr
> 
> 
> __
>> Od: "Marius Schamschula" 
>> Komu: "Gerben Wierda via macports-users" 
>> Datum: 20.03.2021 15:24
>> Předmět: Re: gfortran for M1?
>> 
>> Petr,
>> 
>> sudo port select gcc mp-gcc-devel
>> 
>> will add links so that the binaries, includes and libraries can be found.
>> 
>>> On Mar 20, 2021, at 8:59 AM,   
>>> wrote:
>>> 
>>> Thank you Chris,
>>> 
>>> I found gfortran-mp-devel in /opt/local/bin.
>>> 
>>> However trying to compile my source a got linker error:
>>> ld: library not found for -lm
>>> 
>>> And I am lost again. I did not specified any linker options,
>>> just compiler options:
>>> -g -fbounds-check -ffpe-trap=invalid,zero,overflow 
>>> -ffpe-summary=invalid,zero,overflow -fno-sign-zero -fno-automatic 
>>> -Wuninitialized
>>> 
>>> (Sorry for beginner question. Google did not help.)
>>> 
>>> Petr
>>> 
>>> __
 Od: "Chris Jones" 
 Komu: petr.2...@centrum.cz
 Datum: 20.03.2021 14:04
 Předmět: Re: gfortran for M1?
 
 CC: 
 Hi,
 
 Gcc-devel provides gfortran for M1 machines by default.
 
 Chris
 
> On 20 Mar 2021, at 1:01 pm, petr.2...@centrum.cz wrote:
> 
> Is it already possible to install gfortran on M1?
> It seems that gcc-devel does not have +gfortran variant and and other gcc 
> versions are not compatible. 
> Thank you, 
> Petr
 
 
 
>> 
>> Marius
>> --
>> Marius Schamschula
>> 
>> 
>> 



smime.p7s
Description: S/MIME cryptographic signature

Re: Debugging restore_ports.tcl

[Christopher Jones]

> On 9 Feb 2021, at 11:22 am, Pieter van Oostrum  
> wrote:
> 
> Eric Gallager via macports-users  > writes:
> 
>> On Mon, Feb 8, 2021 at 1:03 PM Ryan Schmidt  wrote:
>>> 
>>> 
>>> 
>>> On Feb 7, 2021, at 20:59, Eric Gallager wrote:
>>> 
 When restore_ports.tcl gets stuck building its list of ports to
 restore, is there a way to get it to tell you which ports exactly it's
 failing to process? i.e., which ports to remove from your myports.txt
 to get it to continue?
>>> 
>>> I don't know. In what way is it getting stuck?
>> 
>> It's the part on the Troubleshooting section of the wiki page where it says:
>> 
>> If you see an "infinite loop" error message, such as this:
>> 
>> Error: we appear to be stuck, exiting...
>> infinite loop
>>while executing
>> "sort_ports $portList"
>>invoked from within
>> "set operationList [sort_ports $portList]"
>>(file "./restore_ports.tcl" line 285)
>> 
>> it indicates that the script has a list of ports to install, and it
>> can't figure out which of the ports to install next.
>> 
>> https://trac.macports.org/wiki/Migration#Troubleshooting
>> 
>> The workaround it suggests to deal with this issue is "to reduce your
>> list of ports to install, until it no longer has a dependency cycle,"
>> but it doesn't say exactly HOW to go about choosing which ports to
>> remove from the list in order to reduce its length.
>> My myports.txt file has 6147 lines in it. I don't know where to begin with 
>> it.
> 
> The usual way of tackling these kinds of problems is "bisecting". Divide the 
> list in two halves, and try each of these separately. If a half fails, then 
> divide it in two halves again, etc.

Personally, I would recommend not trying to restore *every* port, as this will 
include a bunch of dependencies that might not be needed on a new OS, or might 
even not work there. 

Look at the list of *requested* ports you installed. This will be a lot lot 
shorter, short enough to go through by hand and install one by one.

Chris



smime.p7s
Description: S/MIME cryptographic signature

Re: stdlib.h compilation error for macports gcc9.

[Christopher Jones]

what happens if you set SDKROOT and then try again

export SDKROOT=`xcrun --show-sdk-path`

?

> On 7 Feb 2021, at 11:12 pm, Carlo Tambuatco  wrote:
> 
> 
> 
>> On Feb 7, 2021, at 5:39 PM, Christopher Jones > <mailto:jon...@hep.phy.cam.ac.uk>> wrote:
>> 
>> macOS 11 brought big changes to how Apple versions its SDKs. They now 
>> potentially change each minor update, and as such we had to figure out how 
>> to deal with this.
>> 
>> gcc is built against a specific SDK, and to handle this unpredictably it was 
>> recently changed to use the unversioned SDK, instead of a versioned one, 
>> where required.
>> 
>> https://github.com/macports/macports-ports/commit/e8866c5019d60832527850b4e50fdc1de8878716#diff-5aeb3e82f6999f57229a816d2877a6232489c3484ac3e6716cb7e62b5a82696f
>>  
>> <https://github.com/macports/macports-ports/commit/e8866c5019d60832527850b4e50fdc1de8878716#diff-5aeb3e82f6999f57229a816d2877a6232489c3484ac3e6716cb7e62b5a82696f>
>> 
>> Are you on maOS 11 ?
>> 
>> please post the output you get from your failing build, showing the full 
>> command line you use, and the full output, and include the -v option to get 
>> additional diagnostic output.
>> 
>> Chris
> 
> Using macOS Catalina 10.15.7
> 
> 
> Here’s my CPATH environment variable, which up until the gcc9 upgrade, worked 
> fine to relay the location of 
> relevant include paths: 
> 
> CPATH=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include:/usr/local/include:/opt/local/include:/usr/local/dart-sdk/include:/Library/Frameworks/R.framework/Resources/include
> 
> 
> Also, here’s the contents of my SDKs directory in XCode 12.4: 
> 
> pwd = 
> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs
> 
> 
> drwxr-xr-x 5 root wheel 160 Nov 30 07:27 DriverKit20.2.sdk/
> drwxr-xr-x 7 root wheel 224 Nov 30 07:27 MacOSX.sdk/
> lrwxr-xr-x 1 root wheel  10 Jan 27 04:53 MacOSX11.1.sdk -> MacOSX.sdk/
> 
> So it seems I’m using the SDK for macOS 11.1…
> 
> 
> Here’s the full output of the error using the -v option:
> 
> g++ -v -std=c++11  -c E2.5.2.cpp -o E2.5.2.o
> Using built-in specs.
> COLLECT_GCC=g++
> Target: x86_64-apple-darwin19
> Configured with: 
> /opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_lang_gcc9/gcc9/work/gcc-9.3.0/configure
>  --prefix=/opt/local --build=x86_64-apple-darwin19 
> --enable-languages=c,c++,objc,obj-c++,lto,fortran,jit 
> --libdir=/opt/local/lib/gcc9 --includedir=/opt/local/include/gcc9 
> --infodir=/opt/local/share/info --mandir=/opt/local/share/man 
> --datarootdir=/opt/local/share/gcc-9 --with-local-prefix=/opt/local 
> --with-system-zlib --disable-nls --program-suffix=-mp-9 
> --with-gxx-include-dir=/opt/local/include/gcc9/c++/ --with-gmp=/opt/local 
> --with-mpfr=/opt/local --with-mpc=/opt/local --with-isl=/opt/local 
> --enable-stage1-checking --disable-multilib --enable-lto 
> --enable-libstdcxx-time --with-build-config=bootstrap-debug 
> --with-as=/opt/local/bin/as --with-ld=/opt/local/bin/ld 
> --with-ar=/opt/local/bin/ar --with-bugurl=https://trac.macports.org/newticket 
> <https://trac.macports.org/newticket> --enable-host-shared --disable-tls 
> --with-pkgversion='MacPorts gcc9 9.3.0_5' 
> --with-sysroot=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.15.sdk
> Thread model: posix
> gcc version 9.3.0 (MacPorts gcc9 9.3.0_5) 
> COLLECT_GCC_OPTIONS='-v' '-std=c++11' '-c' '-o' 'E2.5.2.o' 
> '-mmacosx-version-min=10.15.0' '-asm_macosx_version_min=10.15' 
> '-shared-libgcc' '-mtune=core2'
>  /opt/local/libexec/gcc/x86_64-apple-darwin19/9.3.0/cc1plus -quiet -v 
> -D__DYNAMIC__ E2.5.2.cpp -fPIC -quiet -dumpbase E2.5.2.cpp 
> -mmacosx-version-min=10.15.0 -mtune=core2 -auxbase-strip E2.5.2.o -std=c++11 
> -version -o /var/folders/yh/ywbbh6_w8xl9_6006s6dywd8gr/T//cc1Ruczn.s
> GNU C++11 (MacPorts gcc9 9.3.0_5) version 9.3.0 (x86_64-apple-darwin19)
>   compiled by GNU C version 9.3.0, GMP version 6.2.1, MPFR version 4.1.0, 
> MPC version 1.2.1, isl version isl-0.22.1-GMP
> 
> GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
> ignoring nonexistent directory 
> "/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.15.sdk/opt/local/include"
> ignoring nonexistent directory 
> "/opt/local/lib/gcc9/gcc/x86_64-apple-darwin19/9.3.0/../../../../../x86_64-apple-darwin19/include"
> ignoring nonexistent directory 
> "/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.15.sdk/usr

Re: stdlib.h compilation error for macports gcc9.

[Christopher Jones]

macOS 11 brought big changes to how Apple versions its SDKs. They now 
potentially change each minor update, and as such we had to figure out how to 
deal with this.

gcc is built against a specific SDK, and to handle this unpredictably it was 
recently changed to use the unversioned SDK, instead of a versioned one, where 
required.

https://github.com/macports/macports-ports/commit/e8866c5019d60832527850b4e50fdc1de8878716#diff-5aeb3e82f6999f57229a816d2877a6232489c3484ac3e6716cb7e62b5a82696f
 


Are you on maOS 11 ?

please post the output you get from your failing build, showing the full 
command line you use, and the full output, and include the -v option to get 
additional diagnostic output.

Chris

> On 7 Feb 2021, at 10:24 pm, Carlo Tambuatco  wrote:
> 
> Well what's odd is I'm only getting this error after upgrading to the latest 
> macports gcc9. Indeed when I use the XCode provided clang version of gcc, it 
> finds all the required libraries. My CPATH environment variable was 
> sufficient to specify the locations of the libraries before the upgrade, so 
> the question is, what changed post-upgrade?
> 
> On Sun, Feb 7, 2021, 5:03 PM Chris Jones  > wrote:
> 
> It sounds like your builds are not correctly specifying the SDK gcc is to 
> use. There are a number of ways you can do this, either by pass it via a 
> compiler flag, by running the complication through xcrun, or by setting the 
> SDKROOT variables to the required path.
> 
> Cheers Chris
> 
> > On 7 Feb 2021, at 9:25 pm, Carlo Tambuatco  > > wrote:
> > 
> > I don’t know if this is a result of updating to the latest macports gcc9, 
> > or the update of XCode, but 
> > all of a sudden when I try to build my C++ program which includes  
> > I get this strange 
> > chain reaction of errors.
> > 
> > In file included from 
> > /opt/local/include/gcc9/c++/ext/string_conversions.h:41,
> > from /opt/local/include/gcc9/c++/bits/basic_string.h:6493,
> > from /opt/local/include/gcc9/c++/string:55,
> > from /opt/local/include/gcc9/c++/bits/locale_classes.h:40,
> > from /opt/local/include/gcc9/c++/bits/ios_base.h:41,
> > from /opt/local/include/gcc9/c++/ios:42,
> > from /opt/local/include/gcc9/c++/ostream:38,
> > from /opt/local/include/gcc9/c++/iostream:39,
> > from ../../standard_includes.h:1,
> > from E2.5.2.cpp:1:
> > /opt/local/include/gcc9/c++/cstdlib:75:15: fatal error: stdlib.h: No such 
> > file or directory
> >   75 | #include_next 
> > 
> > 
> > From my makefile this seems to be the offending includes statement:
> > 
> > #include 
> > #include 
> > 
> > 
> > I’ve googled and it seems that it can’t find stdlib.h, even though it is on 
> > my CPATH environment variable:
> > 
> > export 
> > CPATH=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include:/usr/local/include:/opt/local/include:/usr/local/dart-sdk/include:/Library/Frameworks/R.framework/Resources/include
> > 
> 



smime.p7s
Description: S/MIME cryptographic signature

Re: latest update to BigSur 11.1 broke gcc

[Christopher Jones]

From a combination of my memory, and reading the tickets referenced in the gcc 
port file, if we don’t use 
—with-sysroot we would need to use --with-build-sysroot in order for the build 
to work, and last time that was tried it didn’t work correctly.

> On 16 Dec 2020, at 3:37 am, Ken Cunningham  
> wrote:
> 
> we might just delete this line from the portfile, perhaps:
> 
> 
>  configure.args-append --with-sysroot="${configure.sdkroot}"



smime.p7s
Description: S/MIME cryptographic signature

Re: latest update to BigSur 11.1 broke gcc

[Christopher Jones]

Hi,

This is another consequence of a change Apple has introduced with macOS11 which 
is the SDK version now changes on every incremental OS update. So updating from 
11.0 to 11.1 (and I presume Xcode 12.3) you now have SDK 11.1, not 11.0, and 
thus the current build of gcc, which has the sys root to the 11.0 baked into 
it, now fails.

A quick workaround is to set in your shell SDKROOT to point to the new path to 
the 11.1 SDK. I use

export SDKROOT=`xcrun --show-sdk-path`

in my ~/.profile which does this for each shell.

This is almost certainly not the only issue this change in SDK versioning is 
going to cause, and its likely going to take a while to figure out what to do 
in MacPorts. One option, for ports which have this problem is to configure them 
to use the versionless SDK path at configuration time, at least on macOS 11 and 
newer… This has other issues, but for now it seems the lesser evil to me…

Chris

> On 15 Dec 2020, at 9:23 pm, Andreas Skarlatoudis via macports-users 
>  wrote:
> 
> Hello all, 
> 
> I’m working on a MBP, 2018 model and yesterday I updated to the latest 
> version of BigSur. Since then I cannot compile any fortran code and the error 
> I get is 
> 
> ld: library not found for -lSystem
> collect2: error: ld returned 1 exit status
> 
> 
> I have tried both gcc9 and gcc10
> 
> gfortran -v gives this output :
> 
> Using built-in specs.
> COLLECT_GCC=gfortran
> COLLECT_LTO_WRAPPER=/opt/local/libexec/gcc/x86_64-apple-darwin20/10.2.0/lto-wrapper
> Target: x86_64-apple-darwin20
> Configured with: 
> /opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_lang_gcc10/gcc10/work/gcc-10.2.0/configure
>  --prefix=/opt/local --build=x86_64-apple-darwin20 
> --enable-languages=c,c++,objc,obj-c++,lto,fortran,jit 
> --libdir=/opt/local/lib/gcc10 --includedir=/opt/local/include/gcc10 
> --infodir=/opt/local/share/info --mandir=/opt/local/share/man 
> --datarootdir=/opt/local/share/gcc-10 --with-local-prefix=/opt/local 
> --with-system-zlib --disable-nls --program-suffix=-mp-10 
> --with-gxx-include-dir=/opt/local/include/gcc10/c++/ --with-gmp=/opt/local 
> --with-mpfr=/opt/local --with-mpc=/opt/local --with-isl=/opt/local 
> --enable-stage1-checking --disable-multilib --enable-lto 
> --enable-libstdcxx-time --with-build-config=bootstrap-debug 
> --with-as=/opt/local/bin/as --with-ld=/opt/local/bin/ld 
> --with-ar=/opt/local/bin/ar --with-bugurl=https://trac.macports.org/newticket 
>  --enable-host-shared --disable-tls 
> --with-pkgversion='MacPorts gcc10 10.2.0_4' 
> --with-sysroot=/Library/Developer/CommandLineTools/SDKs/MacOSX11.0.sdk
> Thread model: posix
> Supported LTO compression algorithms: zlib
> gcc version 10.2.0 (MacPorts gcc10 10.2.0_4) 
> 
> I’ve removed and reinstalled MacPorts and all packages but it didn’t help.
> 
> Any ideas what may be the problem here? 
> 
> Thanks in advance for your help
> 
> Andreas 
> 
> Dr. Seismologist
> 



smime.p7s
Description: S/MIME cryptographic signature

Re: Running X11 in MacOS-window-as-X11-display mode?

[Christopher Jones]

> On 9 Dec 2020, at 5:59 am, Ryan Schmidt  wrote:
> 
> 
> 
> On Dec 8, 2020, at 23:44, Ken Preslan wrote:
> 
>> My main problem was performance.  In the Mojave time-frame the xorg server 
>> was updated from 1.18 to 1.20.  Performance for xterm scrolling tanked.  It 
>> was unusable.  I complained on macports-users on April 1st 2019.  There was 
>> a thread about it and Christopher Jones created a xorg-server-1.18 port, 
>> which made things better for me.
> 
> Oh yes I do remember that. I've stayed on High Sierra so I haven't seen these 
> problem myself.
> 
> 
>> When I upgrade to Catalina, the xorg-server-1.18 port stopped working.
> 
> I don't see any open tickets about xorg-server-1.18.
> 

https://github.com/macports/macports-ports/commit/84e44c01750be5e17f9d972efa1654c79edebe5c
 
<https://github.com/macports/macports-ports/commit/84e44c01750be5e17f9d972efa1654c79edebe5c>

I have not tested what consequences there are to removing the line in question, 
but the port at least builds and passes basic tests (xterm runs) on macOS11.

Chris



smime.p7s
Description: S/MIME cryptographic signature

Re: Running X11 in MacOS-window-as-X11-display mode?

[Christopher Jones]

> On 9 Dec 2020, at 5:52 am, Ken Preslan via macports-users 
>  wrote:
> 
> On Tue, Dec 08, 2020 at 09:47:54PM -0800, Ken Cunningham wrote:
>>> In the Mojave time-frame the xorg server was updated from 1.18 to 1.20.  
>>> Performance for xterm scrolling tanked.
>> There was indeed one update where this happened, but Chris and I 
>> straightened that out quite quickly I thought.
>> 
>> I have not noticed any performance troubles in several years, using the 
>> current xorg-server port, on any systems.
> 
> Thanks to you and Ryan!  I'll try it again this weekend and see if I still 
> see problems.  If I do I'll file bugs.

Also note there is the port xorg-server-1.18 which is pinned to a 1.18.x 
version. This port was created to help workaround / investigate issues with new 
versions. So if you do have issues with the primary xors-server port, please 
try with this one and compare.

Chris



smime.p7s
Description: S/MIME cryptographic signature

Re: Libgcc: new version won't deactivate the old version

[Christopher Jones]

> On 4 Dec 2020, at 2:36 am, Michael  wrote:
> 
>> --->  Computing dependencies for libgcc
>> The following dependencies will be installed:  libgcc10
>> Continue? [Y/n]: y
>> --->  Activating libgcc10 @10.2.0_3
>> Error: Failed to activate libgcc10: Image error: 
>> /opt/local/include/gcc/c++/algorithm is being used by the active libgcc 
>> port.  Please deactivate this port first, or use 'port -f activate libgcc10' 
>> to force the activation.
> 
> Is there a reason that trying to activate the new libgcc does not deactivate 
> the old libgcc?
> 


That particular message can only occur if you have not updated your ports in a 
very long time, as the change that made libgcc a stub port happened several 
years ago now If you don’t update regularly you can run into issues like 
this.

In this case, just follow the instructions as given and force deactivate.

Chris

smime.p7s
Description: S/MIME cryptographic signature

Re: Removing all non-requested ports?

[Christopher Jones]

> sudo port uninstall leaves

sometimes you need to run it  more than once to pick everything up.

that said, I use

> sudo port reclaim

these days which does the above, and a bit more.

Chris

> On 3 Dec 2020, at 9:08 am, Michael  wrote:
> 
> What's the command to remove non-requested ports again?
> 



smime.p7s
Description: S/MIME cryptographic signature

Re: Problem with building poppler

[Christopher Jones]

Yes, known. See the last ticket at

https://ports.macports.org/port/poppler/tickets 


> On 25 Oct 2020, at 9:44 pm, Dave Horsfall  wrote:
> 
> Sierra 10.12.6 (won't go any further), MacPorts 2.6.3 on a mid-2010 MacBook 
> Pro.
> 
> (Looks like "poppler" is part of "xpdf", my favourite PDF viewer.)
> 
> Whenever I do my regular "port upgrade outdated" I keep seeing the following, 
> and it's starting to annoy me:
> 
>--->  Configuring poppler
>Error: poppler cannot be built while another version of poppler is active.
>Error: Please forcibly deactivate the existing copy of poppler, e.g. by 
> running:
>Error:
>Error: sudo port -f deactivate poppler
>Error:
>Error: Then try again.
>Error: Failed to configure poppler: poppler is active
> 
> The "fix" is obvious of course, but before I file a bug report is this a 
> known problem?  Error log available upon request.
> 
> Thanks.
> 
> (And yes, I know that I have a number of replies to acknowledge, but I've 
> been busy/sick lately; comes from being in my late 60s.)
> 
> -- Dave



smime.p7s
Description: S/MIME cryptographic signature

Re: Failure to upgrade outdated

[Christopher Jones]

Hi,

The error

Error: Failed to activate libgcc10: Image error: 
/opt/local/lib/libgcc/libatomic.1.dylib is being used by the active libgcc 
port.  Please deactivate this port first, or use 'port -f activate 

tells me its really been a very very long time since the ports where last 
updated here. Not updating your ports regularly is really not recommended as it 
can lead to problems like this when you do.

try

sudo port -f deactivate libgcc

ignore the warning, then try updating again.

Chris

> On 23 Sep 2020, at 12:12 pm, Ruben Di Battista  
> wrote:
> 
> Did you already tried to do what it suggest? 
> 
> ```
> Please deactivate this port first, or use 'port -f activate libgcc10' to 
> force the activation.
> ```
> So deactivate the libgcc port and run the upgrade again? 
> On Wed, 23 Sep 2020, 12:43 list_email--- via macports-users, 
>  > wrote:
> I had not changed anything in my Macports installation for a long time. Then 
> I got to messing around with AquaTerm and something in the linking stage kept 
> crashing, so naturally I decided to freshen up my MacPorts set-up. Here’s 
> what happened. I have no idea what to do.
> 
> macOS 10.11.6
> 
> Thanks for any help.
> 
> Jerry
> 
> 
> MBPro-2:Aquaterm_Downloaded_September_2020 me$ sudo port selfupdate
> Password:
> --->  Updating MacPorts base sources using rsync
> MacPorts base version 2.6.2 installed,
> MacPorts base version 2.6.3 downloaded.
> --->  Updating the ports tree
> --->  MacPorts base is outdated, installing new version 2.6.3
> Warning: Disabling readline support due to readline in /usr/local
> Installing new MacPorts release in /opt/local as root:admin; permissions 0755
> 
> 
> The ports tree has been updated. To upgrade your installed ports, you should 
> run
>   port upgrade outdated
> You haven't run 'sudo port reclaim' in two weeks. It's recommended you run 
> this regularly to reclaim disk space. Would you like to run it now? [Y/n]: n
> MBPro-2:Aquaterm_Downloaded_September_2020 me$ port upgrade outdated
> Error: Insufficient privileges to write to MacPorts install prefix.
> MBPro-2:Aquaterm_Downloaded_September_2020 me$ sudo port upgrade outdated
> Password:
> --->  Computing dependencies for libgcc10
> --->  Fetching archive for libgcc10
> --->  Attempting to fetch libgcc10-10.2.0_1.darwin_15.x86_64.tbz2 from 
> https://packages.macports.org/libgcc10 
> 
> --->  Attempting to fetch libgcc10-10.2.0_1.darwin_15.x86_64.tbz2.rmd160 from 
> https://packages.macports.org/libgcc10 
> 
> --->  Installing libgcc10 @10.2.0_1
> --->  Activating libgcc10 @10.2.0_1
> Error: Failed to activate libgcc10: Image error: 
> /opt/local/lib/libgcc/libatomic.1.dylib is being used by the active libgcc 
> port.  Please deactivate this port first, or use 'port -f activate libgcc10' 
> to force the activation.
> Error: See 
> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc10/libgcc10/main.log
>  for details.
> Error: Problem while installing libgcc10
> Error: Follow https://guide.macports.org/#project.tickets 
>  to report a bug.
> MBPro-2:Aquaterm_Downloaded_September_2020 me$ 
> 



smime.p7s
Description: S/MIME cryptographic signature

Re: macports-users Digest, Vol 168, Issue 7

[Christopher Jones]

Hi,

What does

 ~ > xcode-select -p
/Applications/Xcode.app/Contents/Developer

If it does not point to the correct Xcode installation, then you need to do 
what the instructions below say, use the utility to set the correct location.

Chris

> On 7 Aug 2020, at 7:20 pm, Thomas Bodlien 
>  wrote:
> 
> Hi,
> 
> MacPorts can’t determine the location of the Xcode-Beta sdk.
> How can I fix this?
> I need the Xcode-Beta 12 for App Store In App Purchase testing.
> 
>> Error: 
>> Error: No Xcode installation was found.
>> Error: Please install Xcode and/or run xcode-select to specify its location.
>> Error: 
>> Error: Unable to determine location of a macOS SDK.
>> Error: Unable to open port: can't read "configure.sdkroot": Unable to 
>> determine location of a macOS SDK.
> 
> 
> 
> Thomas Bodlien
> mac...@t-online.de 



smime.p7s
Description: S/MIME cryptographic signature

Re: cltversion error

[Christopher Jones]

Hi,

Apple have been (not so) slowly depreciating the CLT. I more expect to see it 
completely disappear in some future OS…

Chris

> On 12 Jun 2020, at 9:40 pm, Mircea Trandafir  wrote:
> 
> Hi again,
> 
> I actually went the other route, I removed Xcode and only installed the CLT. 
> I thought it would help with this issue, but it seems not. Hopefully they’ll 
> fix the bug soon.
> 
> Cheers,
> Mircea
> -- 
> Mircea Trandafir
> Associate professor
> Department of Business and Economics, 
> University of Southern Denmark
> Campusvej 55, 5230 Odense M
> Denmark
> Web: http://www.mirceatrandafir.com <http://www.mirceatrandafir.com/>
> 
>> On 12 Jun 2020, at 10.35 PM, Christopher Jones > <mailto:jon...@hep.phy.cam.ac.uk>> wrote:
>> 
>> Hi,
>> 
>> Glad I could help.
>> 
>> Don’t though bank on this not reoccurring…. Its been an issue through the 
>> lifetime of 10.15, and tends to reoccur on OS or Xcode upgrades. I believe 
>> there is a bug somewhere in that Apple removes the CLT package receipts but 
>> not the CLT itself.
>> 
>> One fix is to completely remove the CLT. Its actually not really needed 
>> anymore - Just having Xcode installed is enough.
>> 
>> cheers Chris
>> 
>>> On 12 Jun 2020, at 9:30 pm, Mircea Trandafir >> <mailto:tra...@hotmail.com>> wrote:
>>> 
>>> Thanks Chris for the quick reply. It is a bit weird, because:
>>> 
>>> > xcode-select -p
>>> /Library/Developer/CommandLineTools
>>> 
>>> But:
>>> 
>>> > /usr/sbin/pkgutil --pkg-info=com.apple.pkg.CLTools_Executables
>>> No receipt for 'com.apple.pkg.CLTools_Executables' found at '/'.
>>> 
>>> I manually removed the CLT folder and reinstalled with:
>>> 
>>> > sudo xcode-select --install
>>> 
>>> > /usr/sbin/pkgutil --pkg-info=com.apple.pkg.CLTools_Executables
>>> package-id: com.apple.pkg.CLTools_Executables
>>> version: 11.5.0.0.1.1588476445
>>> volume: /
>>> location: /
>>> install-time: 1591993420
>>> groups: com.apple.FindSystemFiles.pkg-group
>>> 
>>> But I have no idea why it didn’t work/see the CLTs in the first place… 
>>> Thanks again, hopefully this problem won’t pop back up.
>>> 
>>> Best,
>>> Mircea
>>> -- 
>>> Mircea Trandafir
>>> Associate professor
>>> Department of Business and Economics, 
>>> University of Southern Denmark
>>> Campusvej 55, 5230 Odense M
>>> Denmark
>>> Web: http://www.mirceatrandafir.com <http://www.mirceatrandafir.com/>
>>> 
>>>> On 12 Jun 2020, at 10.06 PM, Christopher Jones >>> <mailto:jon...@hep.phy.cam.ac.uk>> wrote:
>>>> 
>>>> Hi,
>>>> 
>>>> Please run this, and check you get something similar
>>>> 
>>>>  > /usr/sbin/pkgutil --pkg-info=com.apple.pkg.CLTools_Executables
>>>> package-id: com.apple.pkg.CLTools_Executables
>>>> version: 11.5.0.0.1.1588476445
>>>> volume: /
>>>> location: /
>>>> install-time: 1591989507
>>>> groups: com.apple.FindSystemFiles.pkg-group 
>>>> 
>>>> If you don’t, then you indeed have the issue the warning is referring to 
>>>> and you need to force reinstall the CLT
>>>> 
>>>> Chris
>>>> 
>>>>> On 12 Jun 2020, at 8:10 pm, Mircea Trandafir >>>> <mailto:tra...@hotmail.com>> wrote:
>>>>> 
>>>>> Hi all,
>>>>> 
>>>>> This is the first time I’m writing to the list, so let me first thank the 
>>>>> developers for such a great piece of software! And also a everyone on the 
>>>>> list, I’ve been a consumer of information for the past few years and I 
>>>>> learned quite a bit about macports and MacOS.
>>>>> 
>>>>> The reason for my cry for help is the following: for the past couple of 
>>>>> months, I keep getting the following message whenever I run port, 
>>>>> particularly port reclaim during the “Building list of distfiles still in 
>>>>> use” step:
>>>>> 
>>>>> Warning: cltversion: For a possible fix, please see: 
>>>>> https://trac.macports.org/wiki/ProblemHotlist#reinstall-clt 
>>>>> <https://trac.macports.org/wiki/ProblemHotlist#reinstall-clt>
>>>>> 
>>>>> I followed the instructions at the link, I also uninstalled and 
>>>>> reinstalled Xcode, it keeps popping back up. I have two MacBook Pros and 
>>>>> the same thing happens on both. Here is my setup:
>>>>> 
>>>>> MacPro 15,2
>>>>> MacOS 10.15.5
>>>>> MacPorts base version 2.6.2 (standard location, /opt/local)
>>>>> 
>>>>> I can confirm that the command line tools are installed in 
>>>>> /Library/Developer/CommandLineTools and that the 10.15 SDK is present in 
>>>>> SDKs. Is there any thing I could do to get rid of this message, which is 
>>>>> getting quite annoying? Any ideas why it might have started in the first 
>>>>> place?
>>>>> 
>>>>> Thanks,
>>>>> Mircea
>>>>> -- 
>>>>> Mircea Trandafir
>>>>> Associate professor
>>>>> Department of Business and Economics, 
>>>>> University of Southern Denmark
>>>>> Campusvej 55, 5230 Odense M
>>>>> Denmark
>>>>> Web: http://www.mirceatrandafir.com <http://www.mirceatrandafir.com/>
>>>> 
>>> 
>> 
> 



smime.p7s
Description: S/MIME cryptographic signature

Re: cltversion error

[Christopher Jones]

Hi,

Glad I could help.

Don’t though bank on this not reoccurring…. Its been an issue through the 
lifetime of 10.15, and tends to reoccur on OS or Xcode upgrades. I believe 
there is a bug somewhere in that Apple removes the CLT package receipts but not 
the CLT itself.

One fix is to completely remove the CLT. Its actually not really needed anymore 
- Just having Xcode installed is enough.

cheers Chris

> On 12 Jun 2020, at 9:30 pm, Mircea Trandafir  wrote:
> 
> Thanks Chris for the quick reply. It is a bit weird, because:
> 
> > xcode-select -p
> /Library/Developer/CommandLineTools
> 
> But:
> 
> > /usr/sbin/pkgutil --pkg-info=com.apple.pkg.CLTools_Executables
> No receipt for 'com.apple.pkg.CLTools_Executables' found at '/'.
> 
> I manually removed the CLT folder and reinstalled with:
> 
> > sudo xcode-select --install
> 
> > /usr/sbin/pkgutil --pkg-info=com.apple.pkg.CLTools_Executables
> package-id: com.apple.pkg.CLTools_Executables
> version: 11.5.0.0.1.1588476445
> volume: /
> location: /
> install-time: 1591993420
> groups: com.apple.FindSystemFiles.pkg-group
> 
> But I have no idea why it didn’t work/see the CLTs in the first place… Thanks 
> again, hopefully this problem won’t pop back up.
> 
> Best,
> Mircea
> -- 
> Mircea Trandafir
> Associate professor
> Department of Business and Economics, 
> University of Southern Denmark
> Campusvej 55, 5230 Odense M
> Denmark
> Web: http://www.mirceatrandafir.com <http://www.mirceatrandafir.com/>
> 
>> On 12 Jun 2020, at 10.06 PM, Christopher Jones > <mailto:jon...@hep.phy.cam.ac.uk>> wrote:
>> 
>> Hi,
>> 
>> Please run this, and check you get something similar
>> 
>>  > /usr/sbin/pkgutil --pkg-info=com.apple.pkg.CLTools_Executables
>> package-id: com.apple.pkg.CLTools_Executables
>> version: 11.5.0.0.1.1588476445
>> volume: /
>> location: /
>> install-time: 1591989507
>> groups: com.apple.FindSystemFiles.pkg-group 
>> 
>> If you don’t, then you indeed have the issue the warning is referring to and 
>> you need to force reinstall the CLT
>> 
>> Chris
>> 
>>> On 12 Jun 2020, at 8:10 pm, Mircea Trandafir >> <mailto:tra...@hotmail.com>> wrote:
>>> 
>>> Hi all,
>>> 
>>> This is the first time I’m writing to the list, so let me first thank the 
>>> developers for such a great piece of software! And also a everyone on the 
>>> list, I’ve been a consumer of information for the past few years and I 
>>> learned quite a bit about macports and MacOS.
>>> 
>>> The reason for my cry for help is the following: for the past couple of 
>>> months, I keep getting the following message whenever I run port, 
>>> particularly port reclaim during the “Building list of distfiles still in 
>>> use” step:
>>> 
>>> Warning: cltversion: For a possible fix, please see: 
>>> https://trac.macports.org/wiki/ProblemHotlist#reinstall-clt 
>>> <https://trac.macports.org/wiki/ProblemHotlist#reinstall-clt>
>>> 
>>> I followed the instructions at the link, I also uninstalled and reinstalled 
>>> Xcode, it keeps popping back up. I have two MacBook Pros and the same thing 
>>> happens on both. Here is my setup:
>>> 
>>> MacPro 15,2
>>> MacOS 10.15.5
>>> MacPorts base version 2.6.2 (standard location, /opt/local)
>>> 
>>> I can confirm that the command line tools are installed in 
>>> /Library/Developer/CommandLineTools and that the 10.15 SDK is present in 
>>> SDKs. Is there any thing I could do to get rid of this message, which is 
>>> getting quite annoying? Any ideas why it might have started in the first 
>>> place?
>>> 
>>> Thanks,
>>> Mircea
>>> -- 
>>> Mircea Trandafir
>>> Associate professor
>>> Department of Business and Economics, 
>>> University of Southern Denmark
>>> Campusvej 55, 5230 Odense M
>>> Denmark
>>> Web: http://www.mirceatrandafir.com <http://www.mirceatrandafir.com/>
>> 
> 



smime.p7s
Description: S/MIME cryptographic signature

Re: cltversion error

[Christopher Jones]

Hi,

Please run this, and check you get something similar

 > /usr/sbin/pkgutil --pkg-info=com.apple.pkg.CLTools_Executables
package-id: com.apple.pkg.CLTools_Executables
version: 11.5.0.0.1.1588476445
volume: /
location: /
install-time: 1591989507
groups: com.apple.FindSystemFiles.pkg-group 

If you don’t, then you indeed have the issue the warning is referring to and 
you need to force reinstall the CLT

Chris

> On 12 Jun 2020, at 8:10 pm, Mircea Trandafir  wrote:
> 
> Hi all,
> 
> This is the first time I’m writing to the list, so let me first thank the 
> developers for such a great piece of software! And also a everyone on the 
> list, I’ve been a consumer of information for the past few years and I 
> learned quite a bit about macports and MacOS.
> 
> The reason for my cry for help is the following: for the past couple of 
> months, I keep getting the following message whenever I run port, 
> particularly port reclaim during the “Building list of distfiles still in 
> use” step:
> 
> Warning: cltversion: For a possible fix, please see: 
> https://trac.macports.org/wiki/ProblemHotlist#reinstall-clt 
> 
> 
> I followed the instructions at the link, I also uninstalled and reinstalled 
> Xcode, it keeps popping back up. I have two MacBook Pros and the same thing 
> happens on both. Here is my setup:
> 
> MacPro 15,2
> MacOS 10.15.5
> MacPorts base version 2.6.2 (standard location, /opt/local)
> 
> I can confirm that the command line tools are installed in 
> /Library/Developer/CommandLineTools and that the 10.15 SDK is present in 
> SDKs. Is there any thing I could do to get rid of this message, which is 
> getting quite annoying? Any ideas why it might have started in the first 
> place?
> 
> Thanks,
> Mircea
> -- 
> Mircea Trandafir
> Associate professor
> Department of Business and Economics, 
> University of Southern Denmark
> Campusvej 55, 5230 Odense M
> Denmark
> Web: http://www.mirceatrandafir.com 



smime.p7s
Description: S/MIME cryptographic signature

Re: SDK 10.15 available but not found

[Christopher Jones]

> On 23 May 2020, at 5:13 pm, Christopher Chavez  wrote:
> 
> On 5/23/2020 10:57 AM, Philippe Morey-Chaisemartin wrote:
>> xcode version:  11.5 (11E608c)
> 
> I think new Xcode versions had to first be whitelisted by MacPorts, so
> it's likely that the recent 11.5 release just hasn't been added yet.

True, but not the cause of the issue here I think. I have Xcode 11.5 installed 
on macOS10.15 and have no problems.

Can you check that 

/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.15.sdk

actually exists and contains a valid SDK ?

 > ls 
 > /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.15.sdk
 >  
Entitlements.plist  Library SDKSettings.json
SDKSettings.plist   System  usr

If not try reinstalling Xcode.

Chris

> 



smime.p7s
Description: S/MIME cryptographic signature

Re: Building xorg fails

[Christopher Jones]

> On 9 May 2020, at 4:12 pm, Christoph Kukulies  wrote:
> 
> 
> 
>> Am 09.05.2020 um 17:02 schrieb Lenore Horner > >:
>> 
>> Try cleaning after uninstalling (although when I recently uninstalled 
>> inactive, I think clean happened automatically).  
>> 
>>> On May 9, 2020, at 10:57, Christoph Kukulies >> > wrote:
>>> 
>>> If you meant update the command line tools I did so now. 
>>> 
>>> How can I rebuild xorg-server (or maybe the whole xorg) now. When doing an 
>>> uninstall, a subsequent install
>>> is satisfied so quickly that it doesn’t seem anything has been rebuilt at 
>>> all.
> 
> I did:
> 
> 
> Christophs-MBP:~ kuku$ sudo port  clean xorg-server
> --->  Cleaning xorg-server
> Christophs-MBP:~ kuku$ sudo port uninstall xorg
> --->  Deactivating xorg @20090316_0
> --->  Cleaning xorg
> --->  Uninstalling xorg @20090316_0
> --->  Cleaning xorg
> Christophs-MBP:~ kuku$ sudo port clean xorg-server
> --->  Cleaning xorg-server
> 
> Christophs-MBP:~ kuku$ sudo port install xorg
> --->  Computing dependencies for xorg
> The following dependencies will be installed:  xorg-server
> Continue? [Y/n]: Y
> --->  Fetching archive for xorg-server
> --->  Attempting to fetch xorg-server-1.20.8_0.darwin_19.x86_64.tbz2 from 
> https://packages.macports.org/xorg-server 
> 
> --->  Attempting to fetch xorg-server-1.20.8_0.darwin_19.x86_64.tbz2.rmd160 
> from https://packages.macports.org/xorg-server 
> 
> --->  Installing xorg-server @1.20.8_0
> --->  Activating xorg-server @1.20.8_0
> --->  Cleaning xorg-server
> --->  Fetching archive for xorg
> --->  Attempting to fetch xorg-20090316_0.darwin_19.noarch.tbz2 from 
> https://packages.macports.org/xorg 
> --->  Attempting to fetch xorg-20090316_0.darwin_19.noarch.tbz2.rmd160 from 
> https://packages.macports.org/xorg 
> --->  Installing xorg @20090316_0
> --->  Activating xorg @20090316_0
> --->  Cleaning xorg
> --->  Scanning binaries for linking errors
> --->  No broken files found. 
> --->  No broken ports found.
> Christophs-MBP:~ kuku$ 
> 
> I would expect an hour lasting compilation orgy.

Not at all just rebuilding frog-server takes a few minutes not an hour…

sudo port uninstall xorg-server
sudo port -s install xorg-server

-s forces build from source…

However, I fail to see the need for you to build from source…. The binary 
tarballs are perfectly functional.




smime.p7s
Description: S/MIME cryptographic signature

Re: X11 no longer working

[Christopher Jones]

> On 9 May 2020, at 1:21 pm, Christoph Kukulies  wrote:
> 
> The port install xorg-server went through and as a result I have XQuartz 
> working again.
> 
> Now you say I should revert this (japanes sites’) hack. I removed the 
> symbolic link that this hack suggested, ran
> sudo uninstall xorg-server and then sudo install xorg-server. It ran much 
> faster now as if it didn’t compile anything.

If you don’t follow the instructions in the link I sent you you will likely 
have other problems. The above means nothing as you didn’t rebuild anything. 
You have been warned...

> 
> So I didn’t run into this error below again.
> 
> Thanks to all. 
> 
> 
> X11 working again.
> 
> —
> Christoph
> 
> 
>> Am 09.05.2020 um 14:09 schrieb Christopher Jones > <mailto:jon...@hep.phy.cam.ac.uk>>:
>> 
>> 
>> Thats not what I am referring to. There was likely a warning earlier on 
>> directing you to the macports problem hot list.
>> 
>>> On 9 May 2020, at 1:07 pm, Christoph Kukulies >> <mailto:k...@kukulies.org>> wrote:
>>> 
>>> 
>>> 
>>>> Am 09.05.2020 um 13:51 schrieb Christopher Jones >>> <mailto:jon...@hep.phy.cam.ac.uk>>:
>>>> 
>>>> 
>>>> then you need to figure out what is failing for you with ossp-uuid ...
>>>> 
>>> 
>>> 
>>> 
>>> The error was this one:
>>> 
>>> 
>>> :info:build ../uuid.h:39:10: fatal error: 'sys/types.h' file not found
>>> 
>>> 
>>> see below in context:
>>> 
>>> :info:build /usr/bin/clang -c  -I. -I.. -fno-common -DPERL_DARWIN 
>>> -mmacosx-version-min=10.15 -pipe -Os 
>>> -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk 
>>> -fno-strict-aliasing -fstack-protector-strong -I/opt/local/include 
>>> -DPERL_USE_SAFE_PUTENV -O3   -DVERSION=\"1.0602\" -DXS_VERSION=\"1.0602\"  
>>> "-I/opt/local/lib/perl5/5.26/darwin-thread-multi-2level/CORE"   uuid.c
>>> :info:build clang: warning: no such sysroot directory: 
>>> '/Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk' 
>>> [-Wmissing-sysroot]
>>> :info:build In file included from uuid.xs:30:
>>> :info:build ../uuid.h:39:10: fatal error: 'sys/types.h' file not found
>>> :info:build #include 
>>> :info:build  ^
>>> :info:build 1 error generated.
>>> :info:build make[1]: *** [uuid.o] Error 1
>>> :info:build make[1]: Leaving directory 
>>> `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_ossp-uuid/ossp-uuid/work/uuid-1.6.2/perl'
>>> :info:build make: *** [perl/blib/lib/OSSP/uuid.pm] Error 2
>>> :info:build make: Leaving directory 
>>> `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_ossp-uuid/ossp-uuid/work/uuid-1.6.2'
>>> :info:build Command failed:  cd 
>>> "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_ossp-uuid/ossp-uuid/work/uuid-1.6.2"
>>>  && /usr/bin/make -j8 -w all
>>> :info:build Exit code: 2
>>> :error:build Failed to build ossp-uuid: command execution failed
>>> :debug:build Error code: CHILDSTATUS 19252 2
>>> :debug:build Backtrace: command execution failed
>>> :debug:build while executing
>>> :debug:build "system {*}$notty {*}$nice $fullcmdstring"
>>> :debug:build invoked from within
>>> :debug:build "command_exec build"
>>> :debug:build (procedure "portbuild::build_main" line 8)
>>> :debug:build invoked from within
>>> :debug:build "$procedure $targetname"
>>> :error:build See 
>>> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_ossp-uuid/ossp-uuid/main.log
>>>  for details.
>>> version:1
>>> :debug:sysinfo macOS 10.15 (darwin/19.4.0) arch i386
>>> :debug:sysinfo MacPorts 2.6.2
>>> :debug:sysinfo Xcode 11.4.1
>>> :debug:sysinfo SDK 10.15
>>> :debug:sysinfo MACOSX_DEPLOYMENT_TARGET: 10.15
>>> :debug:clean dropping privileges: euid changed to 502, egid changed to 501.
>>> :debug:main Executing org.macports.main (ossp-uuid)
>>> 
>>> 
>>>>> On 9 May 2020, at 12:48 pm, Christoph Kukulies >>>> <mailto:k...@kukulies.org>> wrote:
>>

Re: X11 no longer working

[Christopher Jones]

Thats not what I am referring to. There was likely a warning earlier on 
directing you to the macports problem hot list.

> On 9 May 2020, at 1:07 pm, Christoph Kukulies  wrote:
> 
> 
> 
>> Am 09.05.2020 um 13:51 schrieb Christopher Jones > <mailto:jon...@hep.phy.cam.ac.uk>>:
>> 
>> 
>> then you need to figure out what is failing for you with ossp-uuid ...
>> 
> 
> 
> 
> The error was this one:
> 
> 
> :info:build ../uuid.h:39:10: fatal error: 'sys/types.h' file not found
> 
> 
> see below in context:
> 
> :info:build /usr/bin/clang -c  -I. -I.. -fno-common -DPERL_DARWIN 
> -mmacosx-version-min=10.15 -pipe -Os 
> -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk 
> -fno-strict-aliasing -fstack-protector-strong -I/opt/local/include 
> -DPERL_USE_SAFE_PUTENV -O3   -DVERSION=\"1.0602\" -DXS_VERSION=\"1.0602\"  
> "-I/opt/local/lib/perl5/5.26/darwin-thread-multi-2level/CORE"   uuid.c
> :info:build clang: warning: no such sysroot directory: 
> '/Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk' [-Wmissing-sysroot]
> :info:build In file included from uuid.xs:30:
> :info:build ../uuid.h:39:10: fatal error: 'sys/types.h' file not found
> :info:build #include 
> :info:build  ^
> :info:build 1 error generated.
> :info:build make[1]: *** [uuid.o] Error 1
> :info:build make[1]: Leaving directory 
> `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_ossp-uuid/ossp-uuid/work/uuid-1.6.2/perl'
> :info:build make: *** [perl/blib/lib/OSSP/uuid.pm] Error 2
> :info:build make: Leaving directory 
> `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_ossp-uuid/ossp-uuid/work/uuid-1.6.2'
> :info:build Command failed:  cd 
> "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_ossp-uuid/ossp-uuid/work/uuid-1.6.2"
>  && /usr/bin/make -j8 -w all
> :info:build Exit code: 2
> :error:build Failed to build ossp-uuid: command execution failed
> :debug:build Error code: CHILDSTATUS 19252 2
> :debug:build Backtrace: command execution failed
> :debug:build while executing
> :debug:build "system {*}$notty {*}$nice $fullcmdstring"
> :debug:build invoked from within
> :debug:build "command_exec build"
> :debug:build (procedure "portbuild::build_main" line 8)
> :debug:build invoked from within
> :debug:build "$procedure $targetname"
> :error:build See 
> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_ossp-uuid/ossp-uuid/main.log
>  for details.
> version:1
> :debug:sysinfo macOS 10.15 (darwin/19.4.0) arch i386
> :debug:sysinfo MacPorts 2.6.2
> :debug:sysinfo Xcode 11.4.1
> :debug:sysinfo SDK 10.15
> :debug:sysinfo MACOSX_DEPLOYMENT_TARGET: 10.15
> :debug:clean dropping privileges: euid changed to 502, egid changed to 501.
> :debug:main Executing org.macports.main (ossp-uuid)
> 
> 
>>> On 9 May 2020, at 12:48 pm, Christoph Kukulies >> <mailto:k...@kukulies.org>> wrote:
>>> 
>>> 
>>> 
>>> 
>>> 
>>>> Am 09.05.2020 um 13:41 schrieb Christopher Jones >>> <mailto:jon...@hep.phy.cam.ac.uk>>:
>>>> 
>>>> looks like your xorg-server installation is not working. Try removing it, 
>>>> reinstall, then log out and back in again.
>>> 
>>> 
>>> 
>>> 
>>> That’s what I tried already and failed on that (see other post subject 
>>> „Building xorg fails“):
>>> 
>>> 
>>> kuku@Christophs-MBP ~ % sudo port install xorg-server
>>> --->  Computing dependencies for xorg-server
>>> The following dependencies will be installed: 
>>>  font-adobe-100dpi
>>>  font-adobe-75dpi
>>>  font-adobe-utopia-100dpi
>>>  font-adobe-utopia-75dpi
>>>  font-adobe-utopia-type1
>>>  font-arabic-misc
>>>  font-bh-100dpi
>>>  font-bh-75dpi
>>>  font-bh-lucidatypewriter-100dpi
>>>  font-bh-lucidatypewriter-75dpi
>>>  font-bh-ttf
>>>  font-bh-type1
>>>  font-bitstream-100dpi
>>>  font-bitstream-75dpi
>>>  font-bitstream-speedo
>>>  font-bitstream-type1
>>>  font-cronyx-cyrillic
>>>  font-cursor-misc
>>>  font-daewoo-misc
>>>  font-dec-misc
>>>  font-ibm-type1
>>>  font-isas-misc
>>>  font-jis-misc
>>>  font

Re: Building xorg fails

[Christopher Jones]

> On 9 May 2020, at 12:59 pm, Christoph Kukulies  wrote:
> 
> 
> The failure exists also on just building xorg-server.
> 
> I gout around it by:
> 
> sudo ln -s 
> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs
>  /Library/Developer/CommandLineTools/
> 
> 
> (found that on a japanes site:
> https://qiita.com/kazuhidet/items/70d983c6b7381a839471 
> <https://qiita.com/kazuhidet/items/70d983c6b7381a839471>)


bad idea. strongly suggest you undo that.

If you had checked the failing port log file you most probably would have found 
an error message directing you to

https://trac.macports.org/wiki/ProblemHotlist#reinstall-clt 
<https://trac.macports.org/wiki/ProblemHotlist#reinstall-clt>

Go there and follow the instructions therein.

Chris


> 
> 
>> Am 09.05.2020 um 13:53 schrieb Christopher Jones > <mailto:jon...@hep.phy.cam.ac.uk>>:
>> 
>> 
>> you do not need to install all off xorg just to get the X11 server. You only 
>> need xorg-server for that.
>> 
>>> On 9 May 2020, at 9:12 am, Christoph Kukulies >> <mailto:k...@kukulies.org>> wrote:
>>> 
>>> In my desperation about this - currently unresolvable x11/Quartz server 
>>> problem - I’m trying tp build Xorg/Quartz under Catalina 10.15.4, but I’m 
>>> running into an error right off:
>>> 
>>> 
>>> kuku@Christophs-MBP ~ % sudo port install xorg
>>> Password:
>>> --->  Computing dependencies for xorg
>>> The following dependencies will be installed: 
>>>  Xft2
>>>  font-adobe-100dpi
>>>  font-adobe-75dpi
>>>  font-adobe-utopia-100dpi
>>>  font-adobe-utopia-75dpi
>>>  font-adobe-utopia-type1
>>>  font-arabic-misc
>>>  font-bh-100dpi
>>>  font-bh-75dpi
>>>  font-bh-lucidatypewriter-100dpi
>>>  font-bh-lucidatypewriter-75dpi
>>>  font-bh-ttf
>>>  font-bh-type1
>>>  font-bitstream-100dpi
>>>  font-bitstream-75dpi
>>>  font-bitstream-speedo
>>>  font-bitstream-type1
>>>  font-cronyx-cyrillic
>>>  font-cursor-misc
>>>  font-daewoo-misc
>>>  font-dec-misc
>>>  font-ibm-type1
>>>  font-isas-misc
>>>  font-jis-misc
>>>  font-micro-misc
>>>  font-misc-cyrillic
>>>  font-misc-meltho
>>>  font-misc-misc
>>>  font-mutt-misc
>>>  font-schumacher-misc
>>>  font-screen-cyrillic
>>>  font-sony-misc
>>>  font-sun-misc
>>>  font-winitzki-cyrillic
>>>  font-xfree86-type1
>>>  fontconfig
>>>  ossp-uuid
>>>  x11perf
>>>  xbacklight
>>>  xcalc
>>>  xclipboard
>>>  xclock
>>>  xcmsdb
>>>  xcompmgr
>>>  xconsole
>>>  xcursorgen
>>>  xditview
>>>  xdm
>>>  xdpyinfo
>>>  xedit
>>>  xev
>>>  xeyes
>>>  xfd
>>>  xfindproxy
>>>  xfontsel
>>>  xfs
>>>  xfsinfo
>>>  xgamma
>>>  xgc
>>>  xinput
>>>  xkbevd
>>>  xkbprint
>>>  xkbutils
>>>  xkill
>>>  xload
>>>  xlogo
>>>  xlsatoms
>>>  xlsclients
>>>  xlsfonts
>>>  xmag
>>>  xman
>>>  xmessage
>>>  xmh
>>>  xmodmap
>>>  xmore
>>>  xorg-apps
>>>  xorg-fonts
>>>  xorg-libXTrap
>>>  xorg-libXtst
>>>  xorg-libXv
>>>  xorg-libdmx
>>>  xorg-scripts
>>>  xorg-server
>>>  xpr
>>>  xprop
>>>  xrandr
>>>  xrefresh
>>>  xsetmode
>>>  xsetpointer
>>>  xsetroot
>>>  xsm
>>>  xstdcmap
>>>  xterm
>>>  xtrap
>>>  xvinfo
>>>  xwd
>>>  xwininfo
>>>  xwud
>>> Continue? [Y/n]: Y
>>> --->  Fetching archive for ossp-uuid
>>> --->  Attempting to fetch ossp-uuid-1.6.2_11+perl5_26.darwin_19.x86_64.tbz2 
>>> from https://packages.macports.org/ossp-uuid 
>>> <https://packages.macports.org/ossp-uuid>
>>> --->  Attempting to fetch ossp-uuid-1.6.2_11+perl5_26.darwin_19.x86_64.tbz2 
>>> from http://nue.de.packages.macports.org/ossp-uuid 
>>> <http://nue.de.packages.macports.org/ossp-uuid>
>>> --->  Attempting to fetch ossp-uuid-1.6.2_11+perl5_26.darwin_19.x86_64.tbz2 
>>> from http://lil.fr.packages.macports.org/ossp-uuid 
>>> <http://lil.fr.packages.macports.org/ossp-uuid>
>>> --->  Building ossp-uuid
&g

Re: Building xorg fails

[Christopher Jones]

you do not need to install all off xorg just to get the X11 server. You only 
need xorg-server for that.

> On 9 May 2020, at 9:12 am, Christoph Kukulies  wrote:
> 
> In my desperation about this - currently unresolvable x11/Quartz server 
> problem - I’m trying tp build Xorg/Quartz under Catalina 10.15.4, but I’m 
> running into an error right off:
> 
> 
> kuku@Christophs-MBP ~ % sudo port install xorg
> Password:
> --->  Computing dependencies for xorg
> The following dependencies will be installed: 
>  Xft2
>  font-adobe-100dpi
>  font-adobe-75dpi
>  font-adobe-utopia-100dpi
>  font-adobe-utopia-75dpi
>  font-adobe-utopia-type1
>  font-arabic-misc
>  font-bh-100dpi
>  font-bh-75dpi
>  font-bh-lucidatypewriter-100dpi
>  font-bh-lucidatypewriter-75dpi
>  font-bh-ttf
>  font-bh-type1
>  font-bitstream-100dpi
>  font-bitstream-75dpi
>  font-bitstream-speedo
>  font-bitstream-type1
>  font-cronyx-cyrillic
>  font-cursor-misc
>  font-daewoo-misc
>  font-dec-misc
>  font-ibm-type1
>  font-isas-misc
>  font-jis-misc
>  font-micro-misc
>  font-misc-cyrillic
>  font-misc-meltho
>  font-misc-misc
>  font-mutt-misc
>  font-schumacher-misc
>  font-screen-cyrillic
>  font-sony-misc
>  font-sun-misc
>  font-winitzki-cyrillic
>  font-xfree86-type1
>  fontconfig
>  ossp-uuid
>  x11perf
>  xbacklight
>  xcalc
>  xclipboard
>  xclock
>  xcmsdb
>  xcompmgr
>  xconsole
>  xcursorgen
>  xditview
>  xdm
>  xdpyinfo
>  xedit
>  xev
>  xeyes
>  xfd
>  xfindproxy
>  xfontsel
>  xfs
>  xfsinfo
>  xgamma
>  xgc
>  xinput
>  xkbevd
>  xkbprint
>  xkbutils
>  xkill
>  xload
>  xlogo
>  xlsatoms
>  xlsclients
>  xlsfonts
>  xmag
>  xman
>  xmessage
>  xmh
>  xmodmap
>  xmore
>  xorg-apps
>  xorg-fonts
>  xorg-libXTrap
>  xorg-libXtst
>  xorg-libXv
>  xorg-libdmx
>  xorg-scripts
>  xorg-server
>  xpr
>  xprop
>  xrandr
>  xrefresh
>  xsetmode
>  xsetpointer
>  xsetroot
>  xsm
>  xstdcmap
>  xterm
>  xtrap
>  xvinfo
>  xwd
>  xwininfo
>  xwud
> Continue? [Y/n]: Y
> --->  Fetching archive for ossp-uuid
> --->  Attempting to fetch ossp-uuid-1.6.2_11+perl5_26.darwin_19.x86_64.tbz2 
> from https://packages.macports.org/ossp-uuid 
> 
> --->  Attempting to fetch ossp-uuid-1.6.2_11+perl5_26.darwin_19.x86_64.tbz2 
> from http://nue.de.packages.macports.org/ossp-uuid 
> 
> --->  Attempting to fetch ossp-uuid-1.6.2_11+perl5_26.darwin_19.x86_64.tbz2 
> from http://lil.fr.packages.macports.org/ossp-uuid 
> 
> --->  Building ossp-uuid
> Error: Failed to build ossp-uuid: command execution failed
> Error: See 
> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_ossp-uuid/ossp-uuid/main.log
>  for details.
> Error: Follow https://guide.macports.org/#project.tickets 
>  to report a bug.
> Error: Processing of port xorg failed
> 
> tail of main.log:
> 
> 
> kuku@Christophs-MBP ~ % :info:build "/opt/local/bin/perl5.26" 
> -MExtUtils::Command::MM -e 'cp_nonempty' -- uuid.bs 
> blib/arch/auto/OSSP/uuid/uuid.bs 644
> :info:build Skip blib/lib/OSSP/uuid.pm (unchanged)
> :info:build Skip blib/lib/OSSP/../Data/UUID.pm (unchanged)
> :info:build Skip blib/lib/OSSP/../Data/UUID.pod (unchanged)
> :info:build Skip blib/lib/OSSP/uuid.pod (unchanged)
> :info:build 1 error generated.
> :info:build make[1]: *** [uuid.o] Error 1
> :info:build make[1]: Leaving directory 
> `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_ossp-uuid/ossp-uuid/work/uuid-1.6.2/perl'
> :info:build make: *** [perl/blib/lib/OSSP/uuid.pm] Error 2
> :info:build make: Leaving directory 
> `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_ossp-uuid/ossp-uuid/work/uuid-1.6.2'
> :info:build Command failed:  cd 
> "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_ossp-uuid/ossp-uuid/work/uuid-1.6.2"
>  && /usr/bin/make -j8 -w all
> :info:build Exit code: 2
> :error:build Failed to build ossp-uuid: command execution failed
> :debug:build Error code: CHILDSTATUS 3564 2
> :debug:build Backtrace: command execution failed
> :debug:build while executing
> :debug:build "system {*}$notty {*}$nice $fullcmdstring"
> :debug:build invoked from within
> :debug:build "command_exec build"
> :debug:build (procedure "portbuild::build_main" line 8)
> :debug:build invoked from within
> :debug:build "$procedure $targetname"
> :error:build See 
> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_ossp-uuid/ossp-uuid/main.log
>  for details.
> 



smime.p7s
Description: S/MIME cryptographic signature

Re: X11 no longer working

[Christopher Jones]

looks like your xorg-server installation is not working. Try removing it, 
reinstall, then log out and back in again.

> On 9 May 2020, at 12:39 pm, Christoph Kukulies  wrote:
> 
> 
> 
>> Am 09.05.2020 um 13:22 schrieb Richard Tobin > >:
>> 
>> 
> Does running xclock or other X clients locally work?
>> 
>>> No. xclock also hangs locally.
>> 
>> So it's not an ssh problem.
>> 
 Also, do ssh -v -Y and see what it says about X11 forwarding.
>> 
>>> Have gone through the ssh connection already in previous posts.
>> 
>> So you did, I missed that.
>> 
>>> What make me wonder is, when I'm looking at the process command 
>>> line of the Xquartz process that there is a -nolisten tcp (?!)
>>> 
>>> 6306 s003  S< 0:00.00 /opt/X11/bin/Xquartz :0 -nolisten tcp -iglx
>>> -auth /var/root/.serverauth.6258
>> 
>> That's ok, you're not trying to connect to X by TCP, but through
>> the unix socket :0.  (Just to be sure, try "xclock -display :0")
> 
> kuku@Christophs-MBP ~ % xclock -display :0
> Error: Can't open display: :0
> kuku@Christophs-MBP ~ % xclock -display \:0
> Error: Can't open display: :0
> kuku@Christophs-MBP ~ % echo $DISPLAY
> /private/tmp/com.apple.launchd.vabAbiJezH/org.macports:0
> kuku@Christophs-MBP ~ % 
> 
>> 
>> Is there a quartz-wm process running?
>> 
> 
> Not directy. WHat I see is:
> 
>  % ps ax | grep -i quartz
>   419   ??  Ss 0:00.09 
> /System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/QuickLookUI.framework/Versions/A/XPCServices/QuickLookUIService.xpc/Contents/MacOS/QuickLookUIService
> 13030 s008  R+ 0:00.00 grep -i quartz
> 
> 
>> -- Richard
>> 
>> -- 
>> The University of Edinburgh is a charitable body, registered in
>> Scotland, with registration number SC005336.



smime.p7s
Description: S/MIME cryptographic signature

Re: X11 Server (Quartz 1.20.4) not having security extensions

[Christopher Jones]

Hi,

I am not an expert on this, but my understanding is this was intentionally 
disabled by default by the Xorg server build system, when XACE was added. The 
MP port stays as close to the upstream defaults as it can.

That said, adding an optional variant to enable this, if the user wishes to, 
seems an option.

https://github.com/macports/macports-ports/pull/7027 


please give the update there a go and report back to the PR if it works for you.

Chris

> On 7 May 2020, at 3:15 pm, Christoph Kukulies  wrote:
> 
> That’s not the issue. I know that. My question see below (I’ll cite):
> 
> "Is there a way to make the server having these extensions? Or are there 
> reasons standing against this?"
> 
> —
> Christoph
> 
> 
>> Am 07.05.2020 um 15:53 schrieb Uli Wienands > >:
>> 
>> Try ssh -Y ...
>> 
>> Uli
>> 
>> On 5/7/20 2:43 AM, Christoph Kukulies wrote:
>>> I found that
>>> 
>>> ssh -X user@remote_host 
>>> 
>>> 
>>> doesn’t do X-forwarding, and that is - I’m told - because the X11 server 
>>> (XQuartz 1.20.4 (xorg-server 1.20.4) doesn’t have security extensions.
>>> 
>>> 
>>> $ xdpyinfo -queryExtensions
>>> 
>>> name of display:/private/tmp/com.apple.launchd.NM3gWpA6AH/org.macports:0
>>> version number:11.0
>>> vendor string:The X.Org  Foundation
>>> vendor release number:12004000
>>> X.Org  version: 1.20.4
>>> maximum request size:  16777212 bytes
>>> motion buffer size:  256
>>> bitmap unit, bit order, padding:32, LSBFirst, 32
>>> image byte order:LSBFirst
>>> number of supported pixmap formats:7
>>> supported pixmap formats:
>>>depth 1, bits_per_pixel 1, scanline_pad 32
>>>depth 4, bits_per_pixel 8, scanline_pad 32
>>>depth 8, bits_per_pixel 8, scanline_pad 32
>>>depth 15, bits_per_pixel 16, scanline_pad 32
>>>depth 16, bits_per_pixel 16, scanline_pad 32
>>>depth 24, bits_per_pixel 32, scanline_pad 32
>>>depth 32, bits_per_pixel 32, scanline_pad 32
>>> keycode range:minimum 8, maximum 255
>>> focus:  None
>>> number of extensions:21
>>>Apple-DRI  (opcode: 128, base event: 64, base error: 128)
>>>Apple-WM  (opcode: 129, base event: 68, base error: 130)
>>>BIG-REQUESTS  (opcode: 134)
>>>DAMAGE  (opcode: 142, base event: 97, base error: 154)
>>>DOUBLE-BUFFER  (opcode: 144, base error: 155)
>>>GLX  (opcode: 148, base event: 101, base error: 159)
>>>Generic Event Extension  (opcode: 130)
>>>MIT-SCREEN-SAVER  (opcode: 143, base event: 98)
>>>MIT-SHM  (opcode: 132, base event: 72, base error: 132)
>>>Present  (opcode: 145)
>>>RANDR  (opcode: 141, base event: 95, base error: 149)
>>>RENDER  (opcode: 140, base error: 144)
>>>SHAPE  (opcode: 131, base event: 71)
>>>SYNC  (opcode: 135, base event: 90, base error: 138)
>>>X-Resource  (opcode: 146)
>>>XC-MISC  (opcode: 137)
>>>XFIXES  (opcode: 139, base event: 93, base error: 142)
>>>XINERAMA  (opcode: 138)
>>>XInputExtension  (opcode: 133, base event: 73, base error: 133)
>>>XKEYBOARD  (opcode: 136, base event: 92, base error: 141)
>>>XVideo  (opcode: 147, base event: 99, base error: 156)
>>> default screen number:0
>>> number of screens:1
>>> 
>>> screen #0:
>>>  dimensions:1680x1028 pixels (445x272 millimeters)
>>>  resolution:96x96 dots per inch
>>>  depths (7):24, 1, 4, 8, 15, 16, 32
>>>  root window id:0x111
>>>  depth of root window:24 planes
>>>  number of colormaps:minimum 1, maximum 1
>>>  default colormap:0x21
>>>  default number of colormap cells:256
>>>  preallocated pixels:black 0, white 16777215
>>>  options:backing-store NO, save-unders NO
>>>  largest cursor:32x32
>>>  current input event mask:0x1a
>>>StructureNotifyMask  SubstructureNotifyMask   
>>> SubstructureRedirectMask 
>>>  number of visuals:80
>>>  default visual id:  0x22
>>>  visual:
>>>visual id:0x22
>>>class:TrueColor
>>>depth:24 planes
>>>available colormap entries:256 per subfield
>>>red, green, blue masks:0xff, 0xff00, 0xff
>>>significant bits in color specification:8 bits
>>> 
>>> 
>>> 
>>> Is there a way to make the server having these extensions? Or are there 
>>> reasons standing against this?
>>> 
>>> 
>>> —
>>> Christoph
> 



smime.p7s
Description: S/MIME cryptographic signature

Re: Cannot do anything with port - upgrade, uninstall not possible

[Christopher Jones]

Hi,

Thats because you starting following the instructions *after* upgrading, not 
before.

You need to reinstall macports over the top of your current installation, to 
update to the binary to that for your current system, then try again.

https://www.macports.org/install.php 

Chris

> On 7 May 2020, at 9:46 am, Christoph Kukulies  wrote:
> 
> Following the instructions of migrating macports is a dead end to me right 
> now.
> 
> all attempts to uninstall or do anything woth the port command ends with that:
> 
> kuku@Christophs-MBP ~ % port -qv installed >myports.txt
> Error: Current platform "darwin 19" does not match expected platform "darwin 
> 18"
> Error: If you upgraded your OS, please follow the migration instructions: 
> https://trac.macports.org/wiki/Migration 
> 
> Error: /opt/local/bin/port: Failed to initialize MacPorts, OS platform 
> mismatch
> kuku@Christophs-MBP ~ % sudo port -fp uninstall installed
> Password:
> Error: Current platform "darwin 19" does not match expected platform "darwin 
> 18"
> Error: If you upgraded your OS, please follow the migration instructions: 
> https://trac.macports.org/wiki/Migration 
> 
> OS platform mismatch
> while executing
> "mportinit ui_options global_options global_variations"
> Error: /opt/local/bin/port: Failed to initialize MacPorts, OS platform 
> mismatch
> kuku@Christophs-MBP ~ % 
> 



smime.p7s
Description: S/MIME cryptographic signature

Re: Is SSL really a dependant of everything?

[Christopher Jones]

> On 6 Apr 2020, at 8:42 am, Dave Horsfall  wrote:
> 
> On Mon, 6 Apr 2020, Ryan Schmidt wrote:
> 
>> You should not routinely use the -p flag like this.
> 
> I did that following advice on this list about a year ago, when some port 
> ("guile"?) that I'd never even heard of would not build.
> 
>> Do you mean openssl? or libressl? or something else?
> 
> openssl-1.1.1f_0+universal.darwin_16.i386-x86_64

So from the above you can tell you are using the universal variant of the 
package.

Looking at

http://packages.macports.org/openssl/

you can see these variants used to be built by the buildbots and thus 
distributed in binary form, however this appears to have stopped for the more 
recent versions. This is why you had to build it from source, and likely why 
you are having to build a lot of dependencies from source.

Why this was done, intentionally or otherwise, I do not know.

Chris

> All the same to me, and I don't touch any config files except under advice 
> (such as using Australian repositories etc); when it comes to the Mac I'm 
> just a dumb end-user (except for the Unix-like bits, in which case not many 
> people can match me...).
> 
> I'm about to go to bed (been a long day for me, and not because of this) so 
> I'll likely not reply in turn right away; yawn...
> 
> Current CPU temp is 81˚ C (I could have boiled an egg on the older MacBook by 
> now; this one has much better cooling).
> 
> -- Dave



smime.p7s
Description: S/MIME cryptographic signature

Re: installing patched okular: cannot open Portfile

[Christopher Jones]

> On 17 Mar 2020, at 6:11 pm, Ryan Schmidt  wrote:
> 
> 
> 
> On Mar 16, 2020, at 14:53, Ken Cunningham wrote:
> 
>> It is a permissions error. Although Chris and others seem to make this work, 
>> it has never worked for me to put a macports repo in my home folder. I don’t 
>> know why, and I gave up trying to fix it.
>> 
>> Just put it in /Users/Shared/MacPorts or, what I do, is put them all in /opt 
>> (but then you have to be careful with sudo, which I always am).
> 
> As far as I remember, this is the correct answer. The macports user (and any 
> user other than you) cannot read the contents of your home directory. So your 
> options are to either put the new ports tree outside of your home directory, 
> or else modify the permissions of your home directory to allow other users to 
> read its contents. The latter may be fine if you are the only user of your 
> computer but is not recommended if you share your computer with other users 
> who have their own accounts.

Its not necessary to give other users read access to your entire home area.

You just need to create a directory, give that read access, and then clone the 
git ports tree into that. Allowing other users to read *only* the ports git 
tree does not seem to me a security issue.

In fact, at least on my 10.15 machine I don’t need to give the new directory 
any new permissions, the defaults are exactly what I posted in my other mail. 
e.g.

Oberon ~ > mkdir ~/MPTest
Oberon ~ > ls -l

drwxr-xr-x   2 chris  staff64 17 Mar 18:36 MPTest


This tallies with what I recall setting up numerous MP installations in this 
way, as I do not recall ever having to set permissions of these sub-dirs to 
make it work. 

Chris

smime.p7s
Description: S/MIME cryptographic signature

Re: macports-users Digest, Vol 163, Issue 12

[Christopher Jones]

> On 17 Mar 2020, at 3:04 pm, Murray Eisenberg  
> wrote:
> 
> I did that: used mode 755 for directories, mode 644 for files there. 
> 
> Still, same error Unable to execute port: Could not open file: 
> /Users/murray/macports/myports/kde/okular/Portfile
> 
> Did you get this to work with your own version of a port already included in 
> MacPorts?

Yes. My primary (only) ports tree is a clone of the git repo. in a 
sub-directory of my home area.

Oberon ~/Projects > ls -lth 
total 0
drwxr-xr-x   8 chris  staff   256B  8 Oct 22:01 MacPorts


Oberon ~/Projects > cd MacPorts 

Oberon ~/Projects/MacPorts > ls -lth
total 0
drwxr-xr-x  64 chris  staff   2.0K 17 Mar 14:42 ports
drwxr-xr-x  30 chris  staff   960B 10 Oct 10:09 base
drwxr-xr-x   5 chris  staff   160B  8 Oct 22:03 info
drwxr-xr-x  12 chris  staff   384B 11 Aug  2019 legacy-support
drwxr-xr-x  10 chris  staff   320B 15 Nov  2018 guide

Oberon ~/Projects/MacPorts > ls -lth ports/science/root6/Portfile 
-rw-r--r--  1 chris  staff23K 17 Mar 14:43 ports/science/root6/Portfile

Oberon ~/Projects/MacPorts > cat /opt/local/etc/macports/sources.conf
# MacPorts system-wide configuration file for ports tree sources.

#rsync://rsync.macports.org/macports/release/tarballs/ports.tar [default]
file:///Users/chris/Projects/MacPorts/ports [default]


Works just fine. e.g.

Oberon ~/Projects/MacPorts > sudo port -d sync
DEBUG: Copying /Users/chris/Library/Preferences/com.apple.dt.Xcode.plist to 
/opt/local/var/macports/home/Library/Preferences
--->  Updating the ports tree
Synchronizing local ports tree from file:///Users/chris/Projects/MacPorts/ports
DEBUG: euid/egid changed to: 501/20, env: HOME=/Users/chris 
SSH_AUTH_SOCK=/private/tmp/com.apple.launchd.tBWSQExnkO/Listeners
DEBUG: /opt/local/bin/git pull --rebase --autostash
DEBUG: system -W /Users/chris/Projects/MacPorts/ports: /opt/local/bin/git pull 
--rebase --autostash
Created autostash: f6afbb3fb96
Current branch master is up to date.
Applied autostash.
DEBUG: euid/egid restored to: 0/0, env restored
DEBUG: system: /opt/local/bin/portindex /Users/chris/Projects/MacPorts/ports
Creating port index in /Users/chris/Projects/MacPorts/ports
Adding port science/root6

Total number of ports parsed:   1 
Ports successfully parsed:  1 
Ports failed:   0 
Up-to-date ports skipped:   23266

I can edit, maintain, interact with git,  the ports under 
~/Projects/Macports/ports using my regular user account, no sudo required.

Oberon ~/Projects/MacPorts/ports > git status
On branch master
Your branch is up to date with 'origin/master'.

Changes not staged for commit:
  (use "git add ..." to update what will be committed)
  (use "git restore ..." to discard changes in working directory)
modified:   science/root6/Portfile

no changes added to commit (use "git add" and/or "git commit -a")

> 
>> On16 Mar 2020 21:13:58 +0100,Pieter van Oostrum > > wrote:
>> 
>> Subject: Re: installing patched okular: cannot open Portfile
>> 
>> Ken Cunningham > > writes:
>> 
>>>gives error:
>>> 
>>>Unable to execute port: Could not open file: 
>>> /Users/murray/macports/myports/kde/okular/Portfile
>>> 
>>>Could it still be a permissions or ownership issue?
>>> 
>>> It is a permissions error. Although Chris and others seem to make this 
>>> work, it has never worked
>>> for me to put a macports repo in my home folder. I don’t know why, and I 
>>> gave up trying to fix it.
>>> 
>>> Just put it in /Users/Shared/MacPorts or, what I do, is put them all in 
>>> /opt (but then you have to
>>> be careful with sudo, which I always am).
>>> 
>> Very strange. I have been using this construction for years. I have all my 
>> directories in my private repository with mode 755, and the files 644.
>> -- 
>> Pieter van Oostrum
> 
> ---
> Murray Eisenberg  murrayeisenb...@gmail.com 
> 
> 503 King Farm Blvd #101   Home (240)-246-7240
> Rockville, MD 20850-6667  Mobile (413)-427-5334
> 
> 



smime.p7s
Description: S/MIME cryptographic signature

Re: Why are my por definitions still out of date after this?

[Christopher Jones]

> On 22 Feb 2020, at 1:39 pm, Gerben Wierda  wrote:
> 
> 
> 
>> On 22 Feb 2020, at 13:32, Christopher Jones > <mailto:jon...@hep.phy.cam.ac.uk>> wrote:
>> 
>> Have you told macports to use your git clone ?
>> 
>> i.e. 
>> 
>>  > cat /opt/local/etc/macports/sources.conf
>> 
>> #rsync://rsync.macports.org/macports/release/tarballs/ports.tar 
>>  [default]
>> file:///Users/chris/Projects/MacPorts/ports 
>>  [default]
>> 
>> where for me /Users/chris/Projects/MacPorts/ports is my local git clone.
> 
> Yes.
> 
> file:///Users/sysbh/MacPortsDev/macports-ports 
> 
> rsync://rsync.macports.org/macports/release/tarballs/ports.tar 
>  [default]

thats not the same. I recommend making your git clone the default, and just 
comment out the other one.

> 
>> b.t.w. Once you have done this, you don’t need to run all the git commands 
>> below. just running
>> 
>> > sudo port sync
>> 
>> will update your git clone, and run the portindex, for you.
> 
> With rsync, not with git.

once you make your git checkout the default, port sync will update with git, 
not rsync.

> So what about branches etc? Suppose I create a branch in my fork to work in? 
> And I want update my master to reflect the latest situation of the official 
> repo?

generally works fine.

run with

> sudo port -d sync

if you want to check what is happening under the hood.

Chris

> 
> G
> 
>> 
>> Chris
>> 
>>> On 22 Feb 2020, at 11:43 am, Gerben Wierda >> <mailto:gerben.wie...@rna.nl>> wrote:
>>> 
>>> I have my own fork of the macports-ports repository on GitHub so I can do 
>>> maintenance. I have a local clone of that fork
>>> 
>>> When I want to update ports I do not maintain, do the following. First I 
>>> make sure my clone is up to date with the upstream original, then I push 
>>> the clone back to my GitHub fork. Then I run portindex. ‘upstream’ is the 
>>> official repo, origin is my fork
>>> git fetch upstream
>>> git checkout master
>>> git reset --hard upstream/master
>>> git push origin master --force
>>> portindex
>>>  
>>> But when I do that, I still get:
>>> 
>>> albus:macports-ports sysbh$ port list updated
>>> Warning: port definitions are more than two weeks old, consider updating 
>>> them by running 'port selfupdate'.
>>> 
>>> (Should have said ‘outdated’ of course, this doesn’t give me a warning)
>>> 
>>> But port self update overwrites everything using rsync and doesn’t go via 
>>> git. So, it is a parallel and possibly trouble-creating route. I want 
>>> update my local tree entirely via git.
>>> 
>>> Still, with a clean clone of of an up-to-date fork, I can do it:
>>> 
>>> sudo port selfupdate
>>> Password:
>>> --->  Updating MacPorts base sources using rsync
>>> MacPorts base version 2.6.2 installed,
>>> MacPorts base version 2.6.2 downloaded.
>>> --->  Updating the ports tree
>>> --->  MacPorts base is already the latest version
>>> 
>>> What is the way to go when updating, using your own clone of your own fork 
>>> of the git repo?
>>> 
>>> G



smime.p7s
Description: S/MIME cryptographic signature

Re: catalena

[Christopher Jones]

Generally speaking mac OS 10.15 works just as well as any other, and as with 
other OSes there are some known issues. Like 32 bit support (not possible on 
10.15). Only you know which ports you use, and without this it is impossible to 
be any more specific.

note though, if you new machine was released with 10.15, you anyway will not be 
able to install an older OS on it. Macs only support the OS they where 
originally released with, and newer. So most likely you are stuck with 10.15 
anyway.

Chris

> On 22 Feb 2020, at 1:13 pm, James Linder  wrote:
> 
> Hi All
> 
> After 6 years my macbook battery is really past it’s use-by.
> The keyboard has become a sea of 
> won’t-push-this-week-and-hard-to-get-a-keypush so I decided to get a new 
> laptop, but of course it comes with catalena.
> I’ve been using high sierra and all my ports are good. Is catalena now stable 
> enough to ‘just work’ or need I consider installing (say) high sierra.
> 
> James
> 



smime.p7s
Description: S/MIME cryptographic signature