Re: latest update to BigSur 11.1 broke gcc

2020-12-15 Thread Ken Cunningham
we might just delete this line from the portfile, perhaps: configure.args-append --with-sysroot="${configure.sdkroot}"

Re: latest update to BigSur 11.1 broke gcc

2020-12-15 Thread Ken Cunningham
> --with-sysroot=/Library/Developer/CommandLineTools/SDKs/MacOSX11.0.sdk gcc is supposed to respond to the SDKROOT env var now, and base sets this (most of the time … sigh). perhaps we should find a way to stop baking in —with-sysroot altogether now… Ken

Re: latest update to BigSur 11.1 broke gcc

2020-12-15 Thread Andreas Skarlatoudis via macports-users
Hi Chris, thanks for the reply. I got a feeling that the problem you describe is behind this error but I didn’t know how to fix it. I’ve added the export you suggest in my profile and it worked. Thanks again for the help, much appreciated! Andreas Dr. Seismologist > On Dec 15, 2020,

Re: latest update to BigSur 11.1 broke gcc

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

latest update to BigSur 11.1 broke gcc

2020-12-15 Thread Andreas Skarlatoudis via macports-users
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

Re: clamav-server notes question

2020-12-15 Thread Lenore Horner
Thank you. > The binary daemondo is part of MacPorts: So the notes indicated - or at any rate that “a” daemondo is part of MacPorts. > > $ which daemondo > /opt/local/bin/daemondo I found that but didn’t know how to tell if it was the right one. It isn’t in a MacPorts directory so I didn’t see