Boud<p>The <a href="https://framapiaf.org/tags/Maneage" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Maneage</span></a> <a href="https://framapiaf.org/tags/reproducibility" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>reproducibility</span></a> system for scientific research papers that starts from a minimal POSIX-like host OS does not yet build [1] the <a href="https://framapiaf.org/tags/GNUCLibrary" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>GNUCLibrary</span></a> = <a href="https://framapiaf.org/tags/GLibC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>GLibC</span></a> . We have a draft implementation building glibc *after* <a href="https://framapiaf.org/tags/GCC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>GCC</span></a> [2]; and an alternative proposal arguing that building glibc *first* and gcc second would be more long-term sustainable [[1] comment18].</p><p>Should GLibC be built first? Why (or why not)?</p><p>[1] <a href="https://savannah.nongnu.org/task/?15390" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">savannah.nongnu.org/task/?1539</span><span class="invisible">0</span></a><br>[2] <a href="https://gitlab.com/maneage/project-dev/-/blob/glibc/reproduce/software/make/core-gnu.mk#L718" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">gitlab.com/maneage/project-dev</span><span class="invisible">/-/blob/glibc/reproduce/software/make/core-gnu.mk#L718</span></a></p>