Jonathan Wight

@schwa @rosyna @filcab Getting compilers and associated tools to be independent of the traditional UNIX path structure is brutally hard.

@schwa @rosyna @filcab Paths. Are Hardcoded. EVERYWHERE. And vendors can’t fix it because BC.

@ameaijou @schwa @filcab But yeah, I'm not sure many people have ever used code-select —install

@schwa @rosyna @filcab It pretty much never works, no matter how many configuration switches and paths and env vars you screw with.

@ameaijou @schwa @filcab I'm guessing it'll be even harder with rootless. (rootless bans some locations bad software uses like /bin/)

@rosyna @schwa @filcab I mean, look at how many dirs even traditional LFS has: /bin, /usr/bin, /usr/local/bin, /opt/bin, all the /sbin’s…

@rosyna @schwa @filcab And let’s not even talk about --sysroot and all its variants in Clang et al…

@ameaijou @rosyna @schwa Yes. Let us not talk about anything that’s in ToolChains.cpp and friends. Which reminds me I have stuff to do there

@filcab @rosyna @schwa I’ve discovered a rule - don’t build compilers using a non-/usr compiler as the build toolchain EVER.

@ameaijou @rosyna @schwa ~/…/llvm-cmake works as expected. At least to build llvm et al. Had to do some juggling with one or two env vars…