Shouldn't Build.sh properly declare the Target (this is arm64, not x86_64) and InstallDir above? Why was /opt/pkg/bin identified as target and my declared prefix /opt/pkg-2022Q4 ignored? (FWIW there is no cc in my /opt/pkg/bin and that dir is not writeable by this user).
The above PATH export seems to fix my bootstrap issue, but this could be a full stop for new users? Was it wrong to prepend (vs append) my path env with /opt/pkg/bin? Should this situation be addressed in Build.sh? It looks like more full (bootstrap) paths should be set and used in Build.sh vs relying on env PATH? What is the best approach here?
...simplifying my question. Although cc was not provided in /opt/pkg/bin, clang is, and it looks like the build target (arch) should be declared to it, vs detected by clang.
Why /usr/bin/clang works but /opt/pkg/bin/clang does not, I am not sure, but shouldn't ./bootstrap detect the local target (arch) and set an appropriate env (and/or config) for clang to do the right thing? What about the InstallDir mixup?
Thanks,
-George
--