Re: Python

[Tom]

World of Tanks crashes with this error log. Can there be something done about 
it?

> Termination Reason:Namespace DYLD, Code 1 Library missing
> Library not loaded: 
> /System/Library/Frameworks/Python.framework/Versions/2.7/Python
> Referenced from: /Volumes/VOLUME/*/Wargaming.net Game 
> Center.app/Contents/MacOS/Wargaming.net Game Center
> Reason: tried: 
> '/System/Library/Frameworks/Python.framework/Versions/2.7/Python' (no such 
> file)
> (terminated at launch; ignore backtrace)

Python

[Tom]

Hello people, how do I install a python replacement for macOS 12.3?

xorg-server

[Tom]

Hi,
I have reinstalled MacPorts, but I still can’t get xorg-server to work.
It is contantly starting and quitting, when trying to run an x11 app.
What could be the problem?
Where does it store its settings? Perhaps deleting them could help.

gcc10

[Tom]

Hi,
gcc10 does not build. How can I fix that?

Re: xorg-server

[Tom]

Same problem with xclock. Where can I find the log file of the xorg-server?

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

xorg-server

[Tom]

>> Hi, 
>> 
>> when trying to run an X11 program, I get the following error message:
>> 
>> (putty:8198): Gtk-WARNING **: 00:06:49.190: cannot open display: :0
>> 
>> How can I fix that?
> 
> Assuming you are running Mac OS X 10.5 or later:
> 
> Check your .zprofile or .profile or .bash_profile for a line like:
> 
> DISPLAY=:0
> 
> Delete it.
> 
> The MacPorts 2.6.4 installer for macOS 11 erroneously added this line. This 
> problem has been fixed in newer versions of the MacPorts installer but any 
> erroneous DISPLAY line added by the 2.6.4 installer needs to be removed 
> manually.

Now xorg-server is starting and quiting. The app does not appear.
What could be the problem?

xorg

[Tom]

Hi, 

when trying to run an X11 program, I get the following error message:

(putty:8198): Gtk-WARNING **: 00:06:49.190: cannot open display: :0

How can I fix that?

Re: XCode reinstall command-line tools

[Tom]

Can’t you simply just ignore that error message?

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

xorg-server crashes

[Tom]

Hi,
xorg-server tries to start, but crashes and then tries to start again.
What could be the problem?
I am using Big Sur 11.5 Beta

port update outdated 'Failed to archivefetch aom: version @3.1.0_0'

[tom eee]

The following is the terminal output, and the main.log is attached.

DING!-17> sudo port upgrade outdated
--->  Fetching archive for aom
--->  Attempting to fetch aom-3.1.0_0.darwin_11.x86_64.tbz2 from
http://packages.macports.org/aom
--->  Attempting to fetch aom-3.1.0_0.darwin_11.x86_64.tbz2.rmd160 from
http://packages.macports.org/aom
Warning: Failed to verify signature for archive!
Error: Failed to archivefetch aom: version @3.1.0_0
Error: See
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_multimedia_aom/aom/main.log
for details.
Error: Follow https://guide.macports.org/#project.tickets to report a bug.

Thank you,
Tom


main.log
Description: Binary data

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

[tom eee]

I did this first:

0:56-43> /opt/local/bin/clang-mp-9.0 --version
clang version 9.0.1
Target: x86_64-apple-darwin11.4.2
Thread model: posix
InstalledDir: /opt/local/libexec/llvm-9.0/bin

For the last attempt to install source-highlight I did not include the '
configure.compiler=macports-clang-9.0' portion. So I did  the following and
got:

1:49-45> sudo port clean source-highlight
Password:
--->  Cleaning source-highlight
1:53-46> sudo port -s install source-highlight
configure.compiler=macports-clang-9.0
--->  Computing dependencies for source-highlight
--->  Fetching distfiles for source-highlight
--->  Verifying checksums for source-highlight
--->  Extracting source-highlight
--->  Configuring source-highlight
--->  Building source-highlight
--->  Staging source-highlight into destroot
--->  Installing source-highlight @3.1.9_0
--->  Deactivating source-highlight @3.1.8_2
--->  Cleaning source-highlight
--->  Activating source-highlight @3.1.9_0
--->  Cleaning source-highlight
--->  Updating database of binaries
--->  Updating database of C++ stdlib usage
--->  Scanning binaries for linking errors
--->  Found 18 broken files, matching files to ports
--->  Found 4 broken ports, determining rebuild order
You can always run 'port rev-upgrade' again to fix errors.
The following ports will be rebuilt:
 ffmpeg @3.2.4+gpl2+x11
 lcms @1.19
 dvdauthor @0.7.1
 wget @1.19.1+ssl
Continue? [Y/n]:

I think this means source-highlight is now OK, so I thought I would let you
know.  Now I am going to say yes to the continue question and move on to
whatever happens next.  Thank you very much for your help, patiences, and
understanding.
Tom

On Wed, May 5, 2021 at 9:53 PM Bill Cole <
macportsusers-20171...@billmail.scconsult.com> wrote:

> On 2021-05-05 at 19:39:33 UTC-0400 (Wed, 5 May 2021 19:39:33 -0400)
> tom eee 
> is rumored to have said:
>
> > /Developer is gone and Xcode 4.6.3 in service.  Still failing build.
> > See
> > attachment.  Thanks, Tom
>
> That log shows that you are back at the original problem, whose proposed
> solution was to force the use of a newer version of the clang compiler
> by running these:
>
> sudo port clean source-highlight
> sudo port -s install source-highlight
> configure.compiler=macports-clang-9.0
>
>
> However, I've lost track of whether we've actually solved the problem
> you hit the last time you tried that: a broken installation of
> clang-9.0. To make sure that problem is fixed, run this:
>
> /opt/local/bin/clang-mp-9.0 --version
>
> That should put out something like this:
>
> clang version 9.0.1
> Target: i386-apple-darwin11.4.2
> Thread model: posix
> InstalledDir: /opt/local/libexec/llvm-9.0/bin
>
>
>
> > On Wed, May 5, 2021 at 5:14 PM Ryan Schmidt 
> > wrote:
> >
> >>
> >>
> >> On May 5, 2021, at 12:19, tom eee wrote:
> >>
> >>> Second, I retried 'sudo port install source-light' with no success.
> >>> The
> >> main.log was very big, so I cut out a big portion of the middle and
> >> attached it to this email.
> >>
> >> The log still shows the same error described in
> >> https://trac.macports.org/ticket/59258 and shows that MacPorts still
> >> recognizes that you have Xcode 4.2.
> >>
> >> Deleting parts of logs can make it harder for us to help you. A
> >> better
> >> file size reduction choice is to compress the log.
> >>
> >>
> >>> Third, I downloaded Xcode 4.6.3 and when the opened dmg directed me
> >>> to
> >> install the Xcode in my Application folder, I checked for what was
> >> already
> >> there first, only to discover that I had Xcode 4.6.3 installed in the
> >> Application folder since 2013!  I then looked in the Developer folder
> >> and
> >> discovered Xcode 4.2 was there.  So I am confused about how to make
> >> Xcode
> >> 4.6.3 the version that MacPorts sees when it is doing it's thing and
> >> do I
> >> now have to do some update for Developer?
> >>
> >> The /Developer folder is obsolete. You can delete it. It is where
> >> Apple
> >> used to install Xcode and associated files, but sometime after Xcode
> >> 4.2
> >> they stopped doing that. Xcode now belongs in /Applications.
> >>
> >> You can use "xcode-select -print-path" to see what Xcode your system
> >> is
> >> configured to use. MacPorts will use this Xcode.
> >>
> >> Assuming it does not say the path is
> >> /Applications/Xcode.app/Contents/Developer, change it to that by
> >> running
> >> "sudo xcode-select -switch
> >> /Applications/Xcode.app/Contents/Developer"
> >>
> >> Then you can run "sudo port clean source-highlight" and try to
> >> install it
> >> again.
> >>
> >>
>
>
> --
> Bill Cole
> b...@scconsult.com or billc...@apache.org
> (AKA @grumpybozo and many *@billmail.scconsult.com addresses)
> Not Currently Available For Hire
>

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

[tom eee]

/Developer is gone and Xcode 4.6.3 in service.  Still failing build.  See
attachment.  Thanks, Tom

On Wed, May 5, 2021 at 5:14 PM Ryan Schmidt  wrote:

>
>
> On May 5, 2021, at 12:19, tom eee wrote:
>
> > Second, I retried 'sudo port install source-light' with no success.  The
> main.log was very big, so I cut out a big portion of the middle and
> attached it to this email.
>
> The log still shows the same error described in
> https://trac.macports.org/ticket/59258 and shows that MacPorts still
> recognizes that you have Xcode 4.2.
>
> Deleting parts of logs can make it harder for us to help you. A better
> file size reduction choice is to compress the log.
>
>
> > Third, I downloaded Xcode 4.6.3 and when the opened dmg directed me to
> install the Xcode in my Application folder, I checked for what was already
> there first, only to discover that I had Xcode 4.6.3 installed in the
> Application folder since 2013!  I then looked in the Developer folder and
> discovered Xcode 4.2 was there.  So I am confused about how to make Xcode
> 4.6.3 the version that MacPorts sees when it is doing it's thing and do I
> now have to do some update for Developer?
>
> The /Developer folder is obsolete. You can delete it. It is where Apple
> used to install Xcode and associated files, but sometime after Xcode 4.2
> they stopped doing that. Xcode now belongs in /Applications.
>
> You can use "xcode-select -print-path" to see what Xcode your system is
> configured to use. MacPorts will use this Xcode.
>
> Assuming it does not say the path is
> /Applications/Xcode.app/Contents/Developer, change it to that by running
> "sudo xcode-select -switch /Applications/Xcode.app/Contents/Developer"
>
> Then you can run "sudo port clean source-highlight" and try to install it
> again.
>
>


source-highlight-main.log.tbz2
Description: Binary data

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

[tom eee]

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: incompatible Xcode version
Error: See
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_libsdl2/libsdl2/main.log
for details.
Error: rev-upgrade failed: Error rebuilding ffmpeg

I went to Apple Developer to get Xcode 4.3 and the log in screen just spins
at me after entering my id and password.
So I guess I am just hosed until I can figure out how to get Xcode 4.3.  I
do not really understand all of this and how it all fits together, the best
I can do is just keep going until I run out of windmills to tilt.  Is there
any value to just erasing everything and starting over?

Thanks everybody for all your help,
Tom

On Fri, Apr 30, 2021 at 1:31 PM Bill Cole <
macportsusers-20171...@billmail.scconsult.com> wrote:

> On 30 Apr 2021, at 11:48, tom eee wrote:
>
> > The following is my terminal output for the clean/install commands you
> > ask
> > me to run.  Attached is the install config.log and main.log.
>
> The config.log indicates a serious problem with your clang-9.0
> installation:
>
> > configure:4766: checking for C compiler version
> > configure:4775: /opt/local/bin/clang-mp-9.0 --version >&5
> > xcodebuild: error: '/opt/local/libexec/llvm-9.0/bin/clang' not found.
> > /Developer/usr/bin/xcodebuild fails with 17664 - Unknown error: 17664
>
> Because the clang-9.0 port installs both /opt/local/bin/clang-mp-9.0 (a
> shell script) and /opt/local/libexec/llvm-9.0/bin/clang (the actual
> compiler binary, which is called by that script) it should not be
> possible to get that error unless damage has been done to the clang-9.0
> installation.
>
> You should try to uninstall and reinstall clang-9.0, then try the
> installation of source-highlight again.
>
>
>
>
> > Do you want
> > me to run the 'port -v installed boost' command also?
> >
> > Last login: Fri Apr 30 11:26:05 on ttys000
> > 11:29-1> sudo port clean source-highlight
> > Password:
> > --->  Cleaning source-highlight
> > 11:30-2> sudo port -s install source-highlight
> > configure.compiler=macports-clang-9.0
> > --->  Computing dependencies for source-highlight
> > --->  Fetching distfiles for source-highlight
> > --->  Verifying checksums for source-highlight
> > --->  Extracting source-highlight
> > --->  Configuring source-highlight
> > Error: Failed to configure source-highlight, consult
> >
> /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_textproc_source-highlight/source-highlight/work/source-highlight-3.1.9/config.log
> > Error: Failed to configure source-highlight: configure failure:
> > command
> > execution failed
> > Error: See
> >
> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_textproc_source-highlight/source-highlight/main.log
> > for details.
> > Error: Follow https://guide.macports.org/#project.tickets to report a
> > bug.
> > Error: Processing of port source-highlight failed
> >
> > Thank you for your help,
> > Tom
> >
> >
> > On Thu, Apr 29, 2021 at 5:59 PM Ryan Schmidt 
> > wrote:
> >
> >>
> >>
> >> On Apr 29, 2021, at 10:54, tom eee wrote:
> >>
> >>> Hello Ryan,  I have been watching the ticket 59258 that you
> >>> associated
> >> with my problem and it is not quite clear to me whether I am being
> >> asked to
> >> do something with boost.  Please update me with how I should proceed.
> >> Thank you, Tom
> >>
> >> In that ticket, I asked you to run:
> >>
> >> port -v installed boost
> >>
> >> However, since we also see the problem on our 10.7 build machine,
> >> that
> >> suggests it's not a problem with your machine, so the results of the
> >> above
> >> command may not turn out to be useful.
> >>
> >> In that ticket, René mentioned that building source-highlight with a
> >> newer
> >> compiler worked for him. So you could try running:
> >>
> >> sudo port clean source-highlight
> >> sudo port -s install source-highlight
> >> configure.compiler=macports-clang-9.0
> >>
> >> If that works, let us know; it at least gives us a workaround we can
> >> apply
> >> to the port until the developers respond to the upstream bug report I
> >> filed.
>
>
> --
> Bill Cole
> b...@scconsult.com or billc...@apache.org
> (AKA @grumpybozo and many *@billmail.scconsult.com addresses)
> Not Currently Available For Hire
>

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

[tom eee]

Hello Ryan,  I have been watching the ticket 59258 that you associated with
my problem and it is not quite clear to me whether I am being asked to do
something with boost.  Please update me with how I should proceed.  Thank
you, Tom

On Fri, Apr 23, 2021 at 12:39 PM Ryan Schmidt 
wrote:

>
>
> On Apr 23, 2021, at 10:37, tom eee wrote:
>
> > I was doing 'sudo port install boost' and got the following error:
> >
> > Error: Failed to build source-highlight: command execution failed
> >
> > OS X 10.7.5
> > Mac Mini mid-2011
> >
> > main.log is attached.
>
> That looks like https://trac.macports.org/ticket/59258.
>
> Looks like nobody has worked on trying to fix that yet.
>
> If anybody knows how to fix it, please leave a comment in the ticket or
> submit a pull request.
>
>

Error: Failed to configure boost

[tom eee]

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


main.log
Description: Binary data

-march arm64

[Tom]

Hi,

gcc does not seem to support -arch arm64
Can ti be build with arm64 support?

Regards

Gnome, Glade, GNUStep

[Tom]

Gnome, Glade and GNUStep are not building.
Can somebody fix that?

Re: MacPorts upgrade outdated taking forever after Big Sur 11.2.1 update

[Tom Gederberg]

It finally finished.  The lines scroll by so fast it was hard to see what it 
was doing, but it is completed successfully.

> On Feb 11, 2021, at 7:57 PM, Ryan Schmidt  wrote:
> 
> 
> 
> On Feb 11, 2021, at 19:27, Tom Gederberg wrote:
> 
>> I just upgraded from Big Sur 11.1 to 11.2.1 and then did a
>> 
>> sudo port -v selfupdate
>> sudo port -v upgrade outdated
>> 
>> It is taking hours and seems to be compiling everything from scratch.  It 
>> have Neve taken this log before and I usually update my ports every week.
>> 
>> Is anyone else experiencing this?
> 
> Do you see lines of output indicating that it is trying to download packages 
> and failing to find them, or do you not see any such lines?
> 
> If you do see those lines, what are some of the package names? We may simply 
> not have built them yet.
> 

MacPorts upgrade outdated taking forever after Big Sur 11.2.1 update

[Tom Gederberg]

I just upgraded from Big Sur 11.1 to 11.2.1 and then did a

sudo port -v selfupdate
sudo port -v upgrade outdated

It is taking hours and seems to be compiling everything from scratch.  It have 
Neve taken this log before and I usually update my ports every week.

Is anyone else experiencing this?

Tom Gederberg

Re: SDK does not appear to be installed

[Tom]

That does not seem to work for Big Sur 11.2 and Xcode 12.4 this time.

> On 3. Feb 2021, at 22:33, Henning Hraban Ramm  wrote:
> 
> For MacOS 10.14 (XCode 11.3) I solved the same problem by downloading the CLI 
> tools from developer.apple.com and installing them.
> 
> Hraban
> 
>> Am 03.02.2021 um 21:12 schrieb Marius Schamschula :
>> 
>> Indeed!
>> 
>> I just upgraded a machine to Big Sur, installed Xcode and the CLI tools. I 
>> got the same message. I used the reinstall procedure - no change.
>> 
>> My guess is that the CLI tools for 11.2 are not out yet.
>> 
>>> On Feb 3, 2021, at 2:08 PM, Tom  wrote:
>>> 
>>> Hello people,
>>> 
>>> what was the solution to this problem?
>>> I cannot find the e-mail anymore.
>>> 
>>>> 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'.
> 

SDK does not appear to be installed

[Tom]

Hello people,

what was the solution to this problem?
I cannot find the e-mail anymore.

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

Desolate Condition

[Tom]

MacPorts is in a desolate condition.
Nearly nothing is building.
Can somebody try to build everything and fix the errors?

building clang

[Tom]

Hi,

how can I build clang with -ilocal option support in order to build CrossOver 
Wine for 32on64?

Regards

build clang

[Tom]

Hi,

how can I build clang that supports -ilocal to build to Wine for 32on64?

Regards

Re: Qt

[Tom]

Thank you very much.
Now macports has compiled gcc and it is working.
But I am drinking beer for now.

> On 1. Jan 2021, at 05:11, Ken Cunningham  
> wrote:
> 
> It is most likely our fault.
> 
> gcc is not finding the MacOSX.sdk probably because it no longer exists.
> 
> so do this (hate to say it):
> 
> sudo port -f uninstall gcc10
> sudo port -v -s install gcc10
> 
> and then go have a nice New Year’s Eve soda, and come back in four hours or 
> so when it is finished rebuilding.
> 
> Then I bet it works for you.
> 
> Best,
> 
> Ken
> 
>> On Dec 31, 2020, at 7:32 PM, Tom > <mailto:mac...@t-online.de>> wrote:
>> 
>> I simply try to include stdio.h like this:
>> 
>> // Compiler Test
>> 
>> // #include 
>> #include 
>> 
>> int main() {
>>   printf("Hallo\n");
>>   // assert(2 != 1);
>>   return 0;
>> }
>> 
>> tom@Toms-Mac-Pro Misc % gcc-mp-10 test.c -o test
>> In file included from test.c:4:
>> /opt/local/lib/gcc10/gcc/x86_64-apple-darwin20/10.2.0/include-fixed/stdio.h:78:10:
>>  fatal error: _stdio.h: No such file or directory
>>78 | #include <_stdio.h>
>>   |  ^~
>> compilation terminated.
>> 
>> 
>>> On 1. Jan 2021, at 04:19, Ken Cunningham >> <mailto:ken.cunningham.web...@gmail.com>> wrote:
>>> 
>>>> But gcc 10/9/8/7/6 does not work. It does not find even stdio.h
>>>> How can I fix this?
>>> 
>>> Hello! 
>>> 
>>> Now you know we want to help you — that’s just who we are, crazy as it 
>>> seems — but there is just not enough information in this question to make 
>>> any headway.
>>> 
>>> Don’t keep us hanging! Give us a clue what is wrong :>
>>> 
>>> K
>> 
> 

Re: Qt

[Tom]

I simply try to include stdio.h like this:

// Compiler Test

// #include 
#include 

int main() {
  printf("Hallo\n");
  // assert(2 != 1);
  return 0;
}

tom@Toms-Mac-Pro Misc % gcc-mp-10 test.c -o test
In file included from test.c:4:
/opt/local/lib/gcc10/gcc/x86_64-apple-darwin20/10.2.0/include-fixed/stdio.h:78:10:
 fatal error: _stdio.h: No such file or directory
   78 | #include <_stdio.h>
  |  ^~
compilation terminated.


> On 1. Jan 2021, at 04:19, Ken Cunningham  
> wrote:
> 
>> But gcc 10/9/8/7/6 does not work. It does not find even stdio.h
>> How can I fix this?
> 
> Hello! 
> 
> Now you know we want to help you — that’s just who we are, crazy as it seems 
> — but there is just not enough information in this question to make any 
> headway.
> 
> Don’t keep us hanging! Give us a clue what is wrong :>
> 
> K

Re: Qt

[Tom]

qt is building now.
But gcc 10/9/8/7/6 does not work. It does not find even stdio.h
How can I fix this?

> On 29. Dec 2020, at 20:46, Ruben Di Battista  
> wrote:
> 
> Hello Tom,
> 
> theoretically the QT5 ports are building correctly. Can you maybe
> provide more information?
> 
> * What's your Macports version?
> * What's your macOs version?
> * Can you attach the build log?
> 
> On Tue, Dec 29, 2020 at 8:38 PM Tom  wrote:
>> 
>> Hello,
>> 
>> is there a qt port, which ist building?
>> All I have tried so far, are not building.
>> 
>> Regards
> 
> 
> 
> -- 
>  _
> -. .´  |
>  ',  ;|∞∞
>˜˜   |∞ RdB
>,.,|∞∞
>  .'   '.  |
> -'   `'
> https://rdb.is

Py38-spyder missing dependancy

[Tom Gederberg]

Sorry, if this is not the proper place to report this - I’m new at this.

I have installed py38-spyder @4.1.4_1 and when I try running it, I get the 
warning/error below about a missing dependancy of parso.



I do have py38-parso @0.8.0_1 installed.

Thanks and Happy New Year (I hope),

Tom Gederberg

Qt

[Tom]

Hello,

is there a qt port, which ist building?
All I have tried so far, are not building.

Regards

macOS 11.1 SDK does not appear to be installed

[Tom Gederberg]

Sorry, if this question has already been answered.

I updated my system to Big Sur and followed the MacPorts migration instructions 
and updated Xcode to version 12.3.

However, when I try to build ports in MacPorts, I now get the following 
warnings.

Warning: The macOS 11.1 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’.

What am I doing wrong?

Re: macports-users Digest, Vol 172, Issue 20

[Tom]

Hi,
how can I build a port with a MacPorts gcc compiler?
For example gcc9.
Regards

CLI Tool Problem

[Tom]

Hi,

I get the following Error Message, although Xcode 12 and the CLI Tools are 
installed:

>> Warning: The macOS 11.0 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’.

What could be the Problem?