search

dslm4515 / CMLFS

Clang-Built Musl Linux From Scratch
MIT License
106 stars 18 forks source link

Clarity on CMLFS_TARGET at 1-cgnutools/4-musl #82

Closed Intensity closed 1 year ago

Intensity commented 1 year ago

I wanted to ask for some clarity on CMLFS_TARGET, since step 4-musl appeared to be looking for a x86_64-cmlfs-linux-musl- prefixed GCC and yet from the previous step, x86_64-cross-linux-gnu-gcc was built.

On an x86_64 host (Debian bootstrap), according to 0-Preparation I have CMLFS_TARGET=x86_64-cmlfs-linux-musl and CMLFS_HOST=x86_64-cross-linux-gnu. That gives --with-target=x86_64-cmlfs-linux-musl --host=x86_64-cross-linux-gnu --build=x86_64-cross-linux-gnu in step 3 GCC configure line, which produces a GCC with the prefix x86_64-cross-linux-gnu-.

And yet, with step 4-musl setting CROSS_COMPILE=${CMLFS_TARGET}- in its configure line, it was looking for x86_64-cmlfs-linux-musl-gcc which wasn't built.

Is there something obvious I'm missing here?

dslm4515 commented 1 year ago

The master branch is currently broken and fails to produce a stable stage 1 & 2 clang.

The bsd-userland branch uses mussel to build cgnutools. This reduces development time on cgnutools. I plan to merge the bsd-userland into the master branch.

dslm4515 commented 1 year ago

closing due to ... 1.) no activity, no response 2.) Current build method used in master branch now uses mussel to bootstrap cgnutools