[Pkg-xen-devel] Bug#968965: Bug#968965: Bug#968965: xen: FTBFS in sid

[Hans van Kranenburg]

notfixed -1 xen/4.14.0-1~exp1
reopen
found -1 xen/4.14.0-1~exp1
thanks

Hi,

On 9/4/20 1:55 PM, Hans van Kranenburg wrote:
> 
> On 8/24/20 7:03 PM, Gianfranco Costamagna wrote:
>> Source: xen
>> Version: 4.11.4+24-gddaaccbbab-1
>> Severity: serious
>>
>> Hello, looks like xen is FTBFS because of some bd-uninstallable python package and a gcc-10 related build failure. 
> 
> [...]
Well, it seems we have more FTBFS, let's reuse this bug number to track
it again?

https://buildd.debian.org/status/package.php?p=xen&suite=experimental

--->8--- arm64 --->8---

gcc -MMD -MP -MF ./.mem_access.o.d -DBUILD_ID -fno-strict-aliasing
-std=gnu99 -Wall -Wstrict-prototypes -Wdeclaration-after-statement
-Wno-unused-but-set-variable -Wno-unused-local-typedefs   -O2
-fomit-frame-pointer -nostdinc -fno-builtin -fno-common -Werror
-Wredundant-decls -Wno-pointer-arith -Wvla -pipe -D__XEN__ -include
/<<PKGBUILDDIR>>/xen/include/xen/config.h -Wa,--strip-local-absolute
-mcpu=generic -mgeneral-regs-only   -I/<<PKGBUILDDIR>>/xen/include
-fno-stack-protector -fno-exceptions -fno-asynchronous-unwind-tables
-fcf-protection=none -Wnested-externs '-D__OBJECT_FILE__="mem_access.o"'
 -c mem_access.c -o mem_access.o
mem_access.c: In function ‘p2m_mem_access_check’:
mem_access.c:227:6: note: parameter passing for argument of type ‘const
struct npfec’ changed in GCC 9.1
  227 | bool p2m_mem_access_check(paddr_t gpa, vaddr_t gla, const struct
npfec npfec)
      |      ^~~~~~~~~~~~~~~~~~~~

--->8--- armhf --->8---

gcc  -marm -DBUILD_ID -fno-strict-aliasing -std=gnu99 -Wall
-Wstrict-prototypes -Wdeclaration-after-statement
-Wno-unused-but-set-variable -Wno-unused-local-typedefs   -O2
-fomit-frame-pointer
-D__XEN_INTERFACE_VERSION__=__XEN_LATEST_INTERFACE_VERSION__ -MMD -MP
-MF .xenpmd.o.d -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE
-D_LARGEFILE64_SOURCE  -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=.
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
-D_FORTIFY_SOURCE=2 -Werror
-I/<<PKGBUILDDIR>>/tools/xenpmd/../../tools/xenstore/include
-I/<<PKGBUILDDIR>>/tools/xenpmd/../../tools/include  -c -o xenpmd.o
xenpmd.c
xenpmd.c: In function ‘get_next_battery_file’:
xenpmd.c:92:37: error: ‘%s’ directive output may be truncated writing
between 4 and 2147483645 bytes into a region of size 271
[-Werror=format-truncation=]
   92 |     #define BATTERY_STATE_FILE_PATH "/tmp/battery/%s/state"
      |                                     ^~~~~~~~~~~~~~~~~~~~~~~
xenpmd.c:117:52: note: in expansion of macro ‘BATTERY_STATE_FILE_PATH’
  117 |             snprintf(file_name, sizeof(file_name),
BATTERY_STATE_FILE_PATH,
      |
^~~~~~~~~~~~~~~~~~~~~~~
xenpmd.c:92:51: note: format string is defined here
   92 |     #define BATTERY_STATE_FILE_PATH "/tmp/battery/%s/state"
      |                                                   ^~
In file included from /usr/include/stdio.h:867,
                 from xenpmd.c:35:
/usr/include/arm-linux-gnueabihf/bits/stdio2.h:67:10: note:
‘__builtin___snprintf_chk’ output between 24 and 2147483665 bytes into a
destination of size 284
   67 |   return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL
- 1,
      |
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   68 |        __bos (__s), __fmt, __va_arg_pack ());
      |        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
xenpmd.c:91:36: error: ‘%s’ directive output may be truncated writing
between 4 and 2147483645 bytes into a region of size 271
[-Werror=format-truncation=]
   91 |     #define BATTERY_INFO_FILE_PATH "/tmp/battery/%s/info"
      |                                    ^~~~~~~~~~~~~~~~~~~~~~
xenpmd.c:114:52: note: in expansion of macro ‘BATTERY_INFO_FILE_PATH’
  114 |             snprintf(file_name, sizeof(file_name),
BATTERY_INFO_FILE_PATH,
      |
^~~~~~~~~~~~~~~~~~~~~~
xenpmd.c:91:50: note: format string is defined here
   91 |     #define BATTERY_INFO_FILE_PATH "/tmp/battery/%s/info"
      |                                                  ^~
In file included from /usr/include/stdio.h:867,
                 from xenpmd.c:35:
/usr/include/arm-linux-gnueabihf/bits/stdio2.h:67:10: note:
‘__builtin___snprintf_chk’ output between 23 and 2147483664 bytes into a
destination of size 284
   67 |   return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL
- 1,
      |
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   68 |        __bos (__s), __fmt, __va_arg_pack ());
      |        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

--->8--- i386 --->8---

gcc    -Wl,-z,relro -Wl,-z,now -pthread -Wl,-soname
-Wl,libxentoolcore.so.1 -shared -Wl,--version-script=libxentoolcore.map
-o libxentoolcore.so.1.0 handlereg.opic
/usr/bin/ld: i386:x86-64 architecture of input file `handlereg.opic' is
incompatible with i386 output
/usr/bin/ld: handlereg.opic: file class ELFCLASS64 incompatible with
ELFCLASS32
/usr/bin/ld: final link failed: file in wrong format
collect2: error: ld returned 1 exit status

Hans