On Wed, May 31, 2023 at 12:23:34PM +0100, Alex Bennée wrote: > Hi, > > While trying to convert the debian-riscv64-cross docker container to an > lcitool based one I ran into a problem building QEMU. The configure step > fails because despite cross compiling we still need a host compiler to > build the hexagon codegen tooling. > > After scratching my head for a while I discovered we did have host GCC's > in our cross images despite there being no explicit request for them in > the docker description. It turned out that the gcovr requirement pulled > in lcov which itself had a dependency on gcc. However this is a bug: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987818 > > which has been fixed in bookworm (and of course sid which is the only > way we can get a riscv64 build of QEMU at the moment). Hence my hacky > attempts to get gcc via side effect of another package failed. > > Hence the question in $SUBJECT. I tried to add a mapping to lcitool for > a pseudo hostgcc package: > > + hostgcc: > + default: gcc > + pkg: > + MacOS: > + cross-policy-default: skip > > however this didn't work. Do we need a new mechanism for this or am I > missing a way to do this?
The last case we had this was with glib2 and in that case we modified mappings.yml so that it has both 'glib2' and 'glib2-native' I guess we want the same for gcc in this case. With regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
