Re: Error: Failed to build source-highlight: command execution failed

2021-05-01 Thread Ken Cunningham
To hopefully solve your browser spinning-beachball problem at developer.apple.com, the browsers-for-older-systems market has had a lot of activity lately. For 10.7 (and probably 10.7 to 10.9) the nicest, most capable one I have seen lately is a legacy version of Chromium that seems to work really

Re: Error: Failed to build source-highlight: command execution failed

2021-05-01 Thread Ryan Schmidt
On Apr 30, 2021, at 18:11, tom eee wrote: > I did as you suggested and after a lengthy period of time I got the following: > > Error: On macOS 10.7, libsdl2 @2.0.14 requires Xcode 4.3 or later but you > have Xcode 4.2. > Error: See https://guide.macports.org/chunked/installing.xcode.html for

Re: clang: error: invalid version number in 'MACOSX_DEPLOYMENT_TARGET=11.3'

2021-05-01 Thread Ryan Schmidt
On May 1, 2021, at 06:33, Mojca Miklavec wrote: > Hi, > > On Sat, 1 May 2021 at 12:22, Joshua Root wrote: >> >> This usually indicates that your Command Line Tools are outdated. If >> Software Update won't update them, you are affected by an Apple bug, and >> will need to follow the instructi

[Solved]: clang: error: invalid version number in 'MACOSX_DEPLOYMENT_TARGET=11.3'

2021-05-01 Thread lars.sonchocky-helld...@hamburg.de
> Am 01.05.2021 um 12:21 schrieb Joshua Root : > >> I’ve got a brand new MBP 16’’ from my employer and tried to use MacPorts on >> that. >> Since it is so new it sports macOS Big Sur 11.3 and Xcode 12.5 >> I know both are very recent and came out just a couple of days ago, so I am >> not expe

Re: clang: error: invalid version number in 'MACOSX_DEPLOYMENT_TARGET=11.3'

2021-05-01 Thread Mojca Miklavec
Hi, On Sat, 1 May 2021 at 12:22, Joshua Root wrote: > > This usually indicates that your Command Line Tools are outdated. If > Software Update won't update them, you are affected by an Apple bug, and > will need to follow the instructions here: >

Re: clang: error: invalid version number in 'MACOSX_DEPLOYMENT_TARGET=11.3'

2021-05-01 Thread Joshua Root
I’ve got a brand new MBP 16’’ from my employer and tried to use MacPorts on that. Since it is so new it sports macOS Big Sur 11.3 and Xcode 12.5 I know both are very recent and came out just a couple of days ago, so I am not expecting the impossible. Installing MacPorts itself went flawlessly

Re: Error: Failed to build source-highlight: command execution failed

2021-05-01 Thread Joshua Root
I did as you suggested and after a lengthy period of time I got the following: Error: On macOS 10.7, libsdl2 @2.0.14 requires Xcode 4.3 or later but you have Xcode 4.2. Error: See https://guide.macports.org/chunked/installing.xcode.html for download links. Error: Failed to extract libsdl2: incomp

Re: MacPorts 2.7.0-beta2 now available for testing

2021-05-01 Thread Andrew Udvare
Any chance this can get in to the final release? https://github.com/macports/macports-base/pull/225 On 01/05/2021 06:01, Joshua Root wrote: Source code and pkgs for MacPorts 2.7.0-beta2 are now available [1]. Testing of either of these install methods is helpful. Be prepared to encounter bugs.

MacPorts 2.7.0-beta2 now available for testing

2021-05-01 Thread Joshua Root
Source code and pkgs for MacPorts 2.7.0-beta2 are now available [1]. Testing of either of these install methods is helpful. Be prepared to encounter bugs. As always, having a recent backup would be wise. Please report any bugs that you find [2] (after first searching Trac [3], of course!) There