In the debootstrap case, I'm not doing any toolchain bootstrap up
front, just downloading and creating a chroot from the base packages.
And in the case of starting with Linux From Scratch, I'm not sure what
would need to change in order for the resulting chroot to have
multilib support. (The latter is an archetype of the ability to
bootstrap Debian on a non-Debian system. These two cases aren't
actually all that different, except that in the second I have to add
bootstrapping dpkg early in the process.)
In the case of starting from a debootstrap chroot, I've gotten down to
downloading: the initial debootstrap packages, libecj-java,
libantlr-java, libaspectj-java, libxmlbeans-java,
libeigenbase-resgen-java, mingw32-runtime,
mingw-w64-{common,i686-dev,x86_64-dev}, ghc, happy, alex, gnat-4.6 and
dependencies, gforth*, mlton*, qmail-uids-gids, libgroboutils-java,
uuagc, sbcl, sbcl-source. And maybe gradle will also be necessary,
though currently that has other dependencies that FTBFS blocking it.
On Fri, Feb 7, 2014 at 9:05 AM, Matthias Klose <d...@debian.org> wrote:
> Am 07.02.2014 18:00, schrieb Daniel Schepler:
>> In both cases, the initial state doesn't allow for multilib compiles,
>
> there are no additional build-deps required for a stage1 multilib build.
> doing
> that in Ubuntu for some years now. So maybe it might be worth updating your
> bootstrap builds for the toolchain?
>
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
