Fix build in specific Linux environment #106
Conversation
This is necessary on systems where the binaries don't contain the architecture names, which doesn't mean they don't support the required architectures.
This is necessary on systems where clang is installed gcc and is also preferred over gcc.
|
hmm, this builds successfully on Travis, so at least it works on one other linux env. it'll definitely break the makefile on my mac, though, where the system hmm, as much as i hate the thought of it, this does seem like a job for Autoconf... |
I have zero experience with Autoconf and can't intuitively identify macros to find a compatible version of Do you have any pointers? |
Same, actually; that's part of why I'm so loath to start using it (well, that and an idealistic belief that "we should be able to build the kernel with a modern toolchain").
My current solution to this kind of problem is a bunch of flaky shell scripts which work around system inconsistencies mostly by symlinking things to have the names and/or locations the Makefile expects. Considered objectively, this is... probably a worse solution than just having a |
Before these changes the Makefile makes the assumption of architecture targeted binaries for
objcopyandstrip. These are not available in my environment which is based on a custom nix-shell derivation.I'm curious if this breaks in other environments :-)