Your message dated Sat, 21 Mar 2020 11:53:01 +0100
with message-id <[email protected]>
and subject line Re: openvswitch: FTBFS on m68k: opf10_packet_in size wrong
has caused the Debian Bug report #880517,
regarding openvswitch: FTBFS on m68k: opf10_packet_in size wrong
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
880517: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880517
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: openvswitch
Version: 2.8.1+dfsg1-2
Severity: important
Tags: upstream
Justification: fails to build from source
User: [email protected]
Usertags: m68k
Builds of openvswitch for m68k (admittedly not a release architecture)
have been failing. At least at present, the (immediate) cause of
failure is
./include/openflow/openflow-common.h:61:34: error: negative width in
bit-field 'build_assert_failed'
unsigned int build_assert_failed : (EXPR) ? 1 : -1; })]
./include/openflow/openflow-1.0.h:211:1: note: in expansion of macro
'OFP_ASSERT'
OFP_ASSERT(sizeof(struct ofp10_packet_in) == 12);
Could you please take a look?
Thanks!
--
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/[email protected]
--- End Message ---
--- Begin Message ---
At this point, not only the tests fails (which I could have fixed by
blacklisting the wrong tests), but also GCC building (see OVS 2.13 build
in Experimental). So I'm giving up and closing this bug, unless porters
do the work of fixing GCC.
Cheers,
Thomas Goirand (zigo)
--- End Message ---
