MIME-Version: 1.0
References: <CAMmSBy8WR2FgKEMApDFTYqSeuA1=H107wWZ-UpE3ZbqGhqnXeQ@mail.gmail.com>
 <b0654142-781b-e527-32f2-551fd17ec5e0@dereferenced.org> <CAMmSBy_umr3OqThczKQPcb3_Ofd7=orreGVqr3+iuY+7zm8MMg@mail.gmail.com>
 <58dfb596-223f-8845-bab1-dbf1aad56fa6@dereferenced.org>
In-Reply-To: <58dfb596-223f-8845-bab1-dbf1aad56fa6@dereferenced.org>
From: Roman Shaposhnik <roman@zededa.com>
Date: Mon, 10 May 2021 19:38:29 -0700
Message-ID: <CAMmSBy8RzrQYW+fX=GB2O=XqJ+-dt=MXyd5P+bgrsV4QL3EaRw@mail.gmail.com>
Subject: Re: Progress on Alpine for RISC-V (and BeagleV)
To: Ariadne Conill <ariadne@dereferenced.org>
Cc: ~alpine/devel@lists.alpinelinux.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Mon, May 10, 2021 at 7:06 PM Ariadne Conill <ariadne@dereferenced.org> w=
rote:
>
> Hi,
>
> On Mon, 10 May 2021, Roman Shaposhnik wrote:
>
> > On Sun, May 9, 2021 at 8:35 AM Ariadne Conill <ariadne@dereferenced.org=
> wrote:
> >>
> >> Hello,
> >>
> >> On Sat, 8 May 2021, Roman Shaposhnik wrote:
> >>
> >>> Hi!
> >>>
> >>> A few updates for anyone interested in Alpine bringup on the board:
> >>>
> >>> I=E2=80=99ve bootstrapped quite a bit of Alpine packages and publishe=
d updated
> >>> aports here https://github.com/rvs/aports
> >>>
> >>> A growing collection of packages is now available under
> >>>   https://eve-alpine-packages.s3.amazonaws.com/edge/{main,community}
> >>>
> >>> It is enough to generate basic images, so for example, here=E2=80=99s=
 a minirootfs
> >>> published that can be used to bootstrap your own containers
> >>>   https://eve-alpine-packages.s3.amazonaws.com/edge/images/alpine-min=
irootfs-210509-riscv64.tar.gz
> >>
> >> Very good!
> >
> > There's also binary install images available now:
> >    https://eve-alpine-packages.s3.amazonaws.com/edge/images/alpine-risc=
v-210511-riscv64.tar.gz
> > and
> >    https://eve-alpine-packages.s3.amazonaws.com/edge/images/alpine-netb=
oot-210511-riscv64.tar.gz
> >
> >>> I still need TONS of help to fix/bootstrap more packages =E2=80=94 an=
d for that
> >>> I published a builder environment =E2=80=94 so if you (on a latest Do=
cker for Mac
> >>> or docker + qemu-user-riscv64) do:
> >>>         $ docker build -t alpine-riscv64
> >>> https://eve-alpine-packages.s3.amazonaws.com/edge/images/Dockerfile
> >>>         $ docker run -it --rm alpine-riscv64
> >>>         builder$ cd aports
> >>> You will end up in an environment that I=E2=80=99m using to build all=
 of these
> >>> packages and can help me with:
> >>>          cd <YOUR FAVORITE PACKAGE>
> >>>          hack APKBUILD (or not)
> >>>          abuild -r
> >>>
> >>> Now, for the most perplexing question of all: it is pretty clear that
> >>> it may be a bit overwhelming for a single person (like me) to make
> >>> sure that we do ALL of the packages at once to support RISC-V.
> >>
> >> When we first got mips64 bootstrapped, I just blocked packages on mips
> >> that were non-essential that didn't build.
> >
> > Aha! Quick question: from that experience -- do you remember what were
> > the packages that were deemed a MUST for the port?
> >
> >> Most maintainers want to see
> >> their packages be portable across architectures and will work to fix t=
hem
> >> when they notice arch=3D"all !riscv64" in their APKBUILDs.
> >
> > For sure! But are you saying that it would be acceptable to first bulk =
update
> > all the APKBUILD files with arch=3D"all !riscv64" (sans those that actu=
ally
> > compile just fine)?
>
> At least with mips, most compiled just fine.

I think here it will be less "out of the box" experience (I actually expect
a LOT of packages to compile with just tiny tweaks to APKBUILD tho --
but those tweaks add up and I don't think I can do it in one go -- hence
this thread).

> I only had to block about
> 100 packages total.  So lets avoid doing that.  You can use buildrepo -k
> to keep going on build failure.

This brings up a good question -- if I spin a beefy box on Packet, what's
the easiest way for me to try and build it all? Basically just to see what
happens (sorry -- not super familiar with buildrepo -- been mostly using
abuild directly).

Thanks,
Roman.