Qemu 4.0 FTBFS in Eoan

Bug #1836159 reported by Christian Ehrhardt 
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
qemu (Ubuntu)
New
Low
Unassigned

Bug Description

I'm not sure yet if this is the gcc9 transition or any other.
But recently builds of qemu 4.0 broke in Eoan

An example build is at https://launchpad.net/ubuntu/+source/qemu/1:4.0+dfsg-0ubuntu2/+build/17252328

From the amd64 log:
9197 cc -iquote /<<BUILDDIR>>/qemu-4.0+dfsg/b/qemu/linux-user -iquote linux-user -iquote /<<BUILDDIR>>/qemu-4.0+dfsg/tcg -iquote /<<BUILDDIR>>/qemu-4.0+dfsg/tcg/i386 -I/<<BUILDDIR>>/qemu-4.0
9198 /<<BUILDDIR>>/qemu-4.0+dfsg/linux-user/ioctls.h:222:9: error: ‘SIOCGSTAMP’ undeclared here (not in a function); did you mean ‘SIOCSRARP’?
9199 222 | IOCTL(SIOCGSTAMP, IOC_R, MK_PTR(MK_STRUCT(STRUCT_timeval)))
9200 | ^~~~~~~~~~
9201 /<<BUILDDIR>>/qemu-4.0+dfsg/linux-user/syscall.c:4812:23: note: in definition of macro ‘IOCTL’
9202 4812 | { TARGET_ ## cmd, cmd, #cmd, access, 0, { __VA_ARGS__ } },
9203 | ^~~
9204 /<<BUILDDIR>>/qemu-4.0+dfsg/linux-user/ioctls.h:223:9: error: ‘SIOCGSTAMPNS’ undeclared here (not in a function); did you mean ‘SIOCGSTAMP_OLD’?
9205 223 | IOCTL(SIOCGSTAMPNS, IOC_R, MK_PTR(MK_STRUCT(STRUCT_timespec)))
9206 | ^~~~~~~~~~~~
9207 /<<BUILDDIR>>/qemu-4.0+dfsg/linux-user/syscall.c:4812:23: note: in definition of macro ‘IOCTL’
9208 4812 | { TARGET_ ## cmd, cmd, #cmd, access, 0, { __VA_ARGS__ } },
9209 | ^~~
9210 make[2]: *** [/<<BUILDDIR>>/qemu-4.0+dfsg/rules.mak:69: linux-user/syscall.o] Error 1
9211 make[2]: Leaving directory '/<<BUILDDIR>>/qemu-4.0+dfsg/b/qemu/aarch64-linux-user'

That build error is the same across all architectures.

summary: - Qmeu 4.0 FTBFS in Eoan
+ Qemu 4.0 FTBFS in Eoan
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

https://<email address hidden>/

Revision history for this message
Christian Ehrhardt  (paelzer) wrote :
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

https://<email address hidden>/

Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

We will take the same interim fix, but this isn't the true solution as one can read in the upstream discussion (size dependencies). Hence I'll not close, but mention this bug in the upload.

At the same time I asked on the upstream discussion (which fell dormant a while ago) if there is a related kernel fix or anything else.
=> https://lists.gnu.org/archive/html/qemu-devel/2019-07/msg02644.html

Revision history for this message
Christian Ehrhardt  (paelzer) wrote :
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Test builds succeeded, uploading to Eoan.
This will -intentionally- not close the bug as I'd want to know how upstream eventually wants to resolve it.

Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Interim fix is in Eoan for now, upstream discussion continues ...

Changed in qemu (Ubuntu):
importance: Undecided → Low
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.