Re: Need help reverting to older library

> On Dec 9, 2020, at 01:30, list_email--- wrote: > > >> On Dec 6, 2020, at 9:35 AM, Ken Cunningham wrote: >> >> of course the simplest method of reverting to an older binary is to just >> reactivate it if you still have it installed, but inactive, after an update. >> >> This will show you

Re: Strange python-38 error when running pip search

On Dec 14, 2020, at 16:26, Carlo Tambuatco wrote: > I have python38 installed via macports. It is the default python > via python_select. > > I don’t think I should file a ticket in this case because this error isn’t > local to the python(s) > installed via macports. It even occurs when

Re: Binaries over different os10 versions

On Dec 12, 2020, at 15:23, dan d. wrote: > Does a binary, like lynx the browser, work over several versions of os10. I > have one older machine which version is 6 upgrades removed from > the most recent one. Will that lynx continue to work if most of the versions > are skipped by

Re: AnRe: latest update to BigSur 11.1 broke gcc

I recall this discussion and commit from last year about how gcc finds it’s SDK to use: https://gcc.gnu.org/git/?p=gcc.git=commit;h=24ec3cc957c4181d8da9972cb2aa212a3e0cec1c Notably, at this moment in time,

AnRe: latest update to BigSur 11.1 broke gcc

I tried it myself, and switching to --with-build-sysroot with gcc10 on big sur does seem to build. I haven't had time to run any tests to see exactly what this means w.r.t. the default sdk search paths. But in any case I think the best advice is anyway to explicitly set it yourself, using one

Re: latest update to BigSur 11.1 broke gcc

I'll try it. Things have changed in gcc -- after all, we don't bake any such path into our clang installs, and they don't exhibit this issue. K > On Dec 16, 2020, at 02:38, Christopher Jones wrote: > > From a combination of my memory, and reading the tickets referenced in the > gcc port

Re: latest update to BigSur 11.1 broke gcc

From a combination of my memory, and reading the tickets referenced in the gcc port file, if we don’t use —with-sysroot we would need to use --with-build-sysroot in order for the build to work, and last time that was tried it didn’t work correctly. > On 16 Dec 2020, at 3:37 am, Ken Cunningham