Decompose mk_CHROOT make target into before/gcc/after

"\"md\"" ([email protected] via alfs-discuss Mailing List) <[email protected]>
Newsgroups gmane.linux.lfs.automated
Message-ID <[email protected]>
Hi,

Please let me know what do you think about a feasibility of decomposing the
mk_CHROOT target
into "_before_gcc", "_gcc", and "_after_gcc" targets, so that they could be
executed separately, if desired.

I'm experimenting with jhalfs https://github.com/marcindulak/jhalfs-ci,
but getting limited by the github actions runners limit of 6 hours per job
https://docs.github.com/en/actions/learn-github-actions/usage-limits-billing-and-administration#usage-limits.

6 hours, even after properly (see
https://lists.linuxfromscratch.org/sympa/arc/alfs-discuss/2022-09/msg00008.html)
setting make to run two jobs in paralell may be insufficient to perform
chapter8
https://www.linuxfromscratch.org/lfs/view/systemd/chapter08/chapter08.html.
A github action runner has 2 cores
https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners#supported-runners-and-hardware-resources.

Do you think a change like that would be feasible in jhalfs?
If yes, any recommendations how roughly an implementation would proceed,
which parts of the code would need to be modified?

I prefer to keep all tests run, but in case 824-gcc alone does not fit into 6
hours,
what would it take to implement a selective test-skip for it?

-- 
http://lists.linuxfromscratch.org/sympa/info/alfs-discuss
Unsubscribe: See the above information page
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.