First off, thanks for everything thus far. Your patience is godlike. I'll definitely check out GrandPerspective.... in a bit. I think I'm getting somewhere but want to run it by you to see if you think I'm off in the weeds again or not.
I use this laptop to do Rails dev, well, I did Rails dev for about 6 months before getting pulled back into the consulting world for a 3 year gig. I only recently picked up my personal project around June (in earnest) while still have an MVP of my web project running for about 10 users. I was hesitant on upgrading anything, especially to Catalina due to a fear (probably wrongly founded) of breaking compatibility of many things my old project may have depended on.
I vaguely recall needing to upgrade openssl from 1.0 to 1.1 for some reason. (Ruby or Rails upgrade would be my guess) but needed to upgrade XCode, which required a macOS upgrade (don't count all that as gossip) and ended up using (I think) homebrew to do it.
Again, I'm not noticing any failures or super noticeable poor performance in most of my tasks.... just the ugly console log. I'm starting to think it's because of two conflicting XCode Command Line Tools installations. Here's a console blurb:
But that may mean nothing. Here's my Terminal output while running down this vague thread. I'll explain on the other side.
So first I confirm that I have XCode installed, and then try gcc as that is supposed to work if the Command Line Tools are installed, but it fails with
clang: error: no input files
yet gcc -v works, as does gcc --print-search-dirs
I could be going down the wrong path here so I'll just get to my question. Do any of those items listed after my brew list look like an XCode Command Line Tools? If so, then that's most likely the issue. Here's my brew config output:
It looks like I'm on the right path as I get no results when running the command found https://github.com/nodejs/node-gyp/issues/1927#issuecomment-544450426-permalink:~:text=com.apple.pkg.CLTools_macOS_SDK-,If%20you%20get%20nothing%20returned%2C%20please%20do%20sudo
I'm going to continue down this rabbit hole. Would love to know if anything jumps out at you or not on what I've written above. Besides that I know just enough to be dangerous....