Closed FiloSottile closed 8 years ago
I moved everything in a non-linked folder, linked only the contents of bin
and everything worked.
Curiosity: how can the toolchain be relocatable? Does it know to look for libs and headers via paths relative to the compiler binary?
I'm not sure how you produced that conflict list, but yes, just symlinking the bins is the easiest way to put your cross compilers in the standard path. gcc always looks for its executable tools and gcc lib dir and such relative to the location of the binary, and when build with sysroot set to a descendant of the install prefix, gcc also applies this logic to sysroot, and thus looks for libs and headers at the appropriate location relative to its binary.
Wonderful, thanks.
This might not be a problem with musl-cross-make, but I'm out of my depth to judge: when trying to link the cross compiler into
/usr/local
, I get the following conflicts:Maybe I should only link the bin folder contents, but maybe those assets should not be installed in the first place?