Daniel Nachun

I opened https://github.com/Homebrew/brew/pull/13626 so that we can just hardcode `ENV["CC"]` and `ENV["CXX"]` to the host compiler. Once that is merged I'll update this one last time and then we should...

Aside from addressing the above feedback, I tested this on a completely clean CentOS 7 Docker image and realized it made no sense to try check if `make` is present...

Based on the feedback I've gotten here now, I am heavily leaning towards keeping things very simple here by just unconditionally vendoring these dependencies to make sure all parts of...

After thinking about this more I think have a compromise that should balance formula complexity with flexibility pretty evenly. I think we should unconditionally vendor the build dependencies other than...

There isn’t supposed to be any code that’s run only when GCC isn’t vendored (if there is please let me know). Vendoring all the dependencies means all the code I’m...

I've pushed a commit now that greatly simplifies things. I think we've gotten a bit lost in the weeds so I'll summarize very succinctly the two goals of the commit...

> > Definitely looking better but I'd really love if there's a way we can avoid the vendoring entirely in favour of requiring all this stuff to be installed from...

> We're not vendoring `gcc` and pretty much an entire `build-essentials`-like toolchain. This is true but I guess from what I've seen now from working on this, that toolchain is...

I figured out how to build everything from formulae!!! @MikeMcQuaid you were totally right and I should have tried this a lot sooner, as it's actually much cleaner and simpler....

> * are the RPATH/specs issues not fixable? The are two RPATH/specs issues. In the build dependencies, the problem is that both our superenv and brewed GCC spec add RPATHs...