Re: How do you represent a host gcc and a cross gcc in lcitool?

[Erik Skultety <eskultet@redhat.com>]

[...]
> > >> >> RiscV guys,
> > >> >>
> > >> >> It's clear that relying on Debian Sid for the QEMU cross build for RiscV
> > >> >> is pretty flakey. Are you guys aware of any other distros that better
> > >> >> support cross compiling to a riscv64 target or is Debian still the best
> > >> >> bet? Could you be persuaded to build a binary docker image with the
> > >> >> cross compilers and libraries required for a decent cross build as an
> > >> >> alternative?
> > >
> > > It's probably not very helpful, but I find Arch based distros to be
> > > the best bet for this.
> >
> > I've never tried arch under docker, isn't it just as much of a moving
> > target?
> 
> I haven't really tried Arch under Docker. I agree that it is a fast
> moving target. I guess it's up for debate if it's too much churn or
> not
> 
> Would a working Arch image be helpful with lcitool?

Not sure from which angle to look at ^this question, so I just add a NB and if
I missed the point just ignore it - we currently don't support Arch as a target
in lcitool, but if this is kind of a dealbreaker for cross-arch QEMU CI,I don't
see a reason why we shouldn't add it. There'd be quite a few steps involved to
introduce it properly, especially wrt/ VM installation, hence we'd need an
issue to track all subgoals, but FWIW it's not needed to address all of the
problems at once if all that is sufficient for you is a working Dockerfile.

Regards,
Erik