Re: Qt

2020-12-31 Thread Ken Cunningham
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

Re: Qt

2020-12-31 Thread 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:

Re: Qt

2020-12-31 Thread Ken Cunningham
> 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

Re: Qt

2020-12-31 Thread 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

Py38-spyder missing dependancy

2020-12-31 Thread 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

Re: Warning: All compilers are either blacklisted or unavailable

2020-12-31 Thread Michael Newman via macports-users
On Jan 1, 2021, at 01:47, Ryan Schmidt wrote: > If you see this warning when doing actions other than > configuring/building/installing (such as when cleaning) ignore it. Maybe we > shouldn't even display the warning in those cases, though I'm not sure if > there's a good way for us to do

Re: Warning: All compilers are either blacklisted or unavailable

2020-12-31 Thread Ryan Schmidt
On Dec 31, 2020, at 03:12, Michael Newman wrote: > Some months ago I upgraded the OS on a remote 2010 MacBook (the white one) to > High Sierra (10.13.16). After the upgrade I did the recommended MacPorts > migration without problems. > > I don’t visit this machine very regularly, so only

Re: Why is ${prefix}/var/macports/home not owned by the macports user?

2020-12-31 Thread Ryan Schmidt
On Dec 31, 2020, at 09:49, Janosch Peters wrote: > I am currently preparing a port file for the new port MacPass [1]. Installing > and building works fine, but I do get some warnings because a tool preparing > the build called carthage wants to create a file in >

Re: Why is ${prefix}/var/macports/home not owned by the macports user?

2020-12-31 Thread Andrew Udvare
> On 2020-12-31, at 10:49, Janosch Peters via macports-users > wrote: > > [1] > https://github.com/Janosch/macports-ports/blob/new-port-macpass/security/MacPass/Portfile Just some comments on the port: Line 13 (name) is not necessary because github.setup sets the name (second argument).

Why is ${prefix}/var/macports/home not owned by the macports user?

2020-12-31 Thread Janosch Peters via macports-users
Hi, I am currently preparing a port file for the new port MacPass [1]. Installing and building works fine, but I do get some warnings because a tool preparing the build called carthage wants to create a file in ${prefix}/var/macports/home/Library. This fails because the folder is owned by

Warning: All compilers are either blacklisted or unavailable

2020-12-31 Thread Michael Newman via macports-users
Some months ago I upgraded the OS on a remote 2010 MacBook (the white one) to High Sierra (10.13.16). After the upgrade I did the recommended MacPorts migration without problems. I don’t visit this machine very regularly, so only recently remembered to run port clean all after doing a