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 <ken.cunningham.web...@gmail.com> > 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 <mac...@t-online.de >> <mailto:mac...@t-online.de>> wrote: >> >> I simply try to include stdio.h like this: >> >> // Compiler Test >> >> // #include <assert.h> >> #include <stdio.h> >> >> 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 <ken.cunningham.web...@gmail.com >>> <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 >> >