time for another grind ;).  straight out of the gate is a bit rough.

a few signed warnings have crept in:
  socketutils.c: In function 'receive_responses':
  socketutils.c:145:110: warning: comparison between signed and unsigned 
integer expressions [-Wsign-compare]
  netlink_inet_diag.c: In function 'check_responses':
  netlink_inet_diag.c:67:112: warning: comparison between signed and unsigned 
integer expressions [-Wsign-compare]
  netlink_unix_diag.c: In function 'check_responses':
  netlink_unix_diag.c:75:112: warning: comparison between signed and unsigned 
integer expressions [-Wsign-compare]

guess this should be declared differently ?  maybe as a noinst_PROGRAM ?
  Makefile.am:411: warning: variable 'ioctlsort_LDFLAGS' is defined but no 
program or
  Makefile.am:411: library has 'ioctlsort' as canonical name (possible typo)
although the build settings look a bit dicey ... it's mixing target compiler & 
settings and the build compiler.  this leads to all cross-compiles failing:
  ./ioctlsort0 > ioctlent0.h
  /bin/sh: ./ioctlsort0: cannot execute binary file: Exec format error

otherwise the summary is below (and full logs attached).  i'll take a look at 
the ia64 build failure first.  probably can ignore the superh failure too as 
that looks like a build system issue.  the rest look legit although i haven't 
dived down into them just yet.

testing commit a671a2c7b4d0147fe280fbe9a5873a6b52f97d24

native (build+tests):
vFAIL: autotools; sh4/??? linux-2.6.30.9 kernel-headers-3.13.0 glibc-2.17 
gcc-4.7.3
vFAIL: build; ia64/64-bit/LSB linux-3.14.14-gentoo kernel-headers-3.16.0 
glibc-2.19 gcc-4.7.4
vFAIL: build; x86_64/32-bit/LSB linux-3.18.4 kernel-headers-3.19.0 glibc-2.21 
gcc-4.9.2
vFAIL: test; alpha/64-bit/LSB linux-3.18.1 kernel-headers-3.19.0 glibc-2.20 
gcc-4.9.2
vFAIL: test; i686/32-bit/LSB linux-3.18.4 kernel-headers-3.3.0 glibc-2.17 
gcc-4.7.2
vFAIL: test; parisc/32-bit/MSB linux-3.16.2-gentoo kernel-headers-3.16.0 
glibc-2.19 gcc-4.7.3
vFAIL: test; ppc/32-bit/MSB linux-3.12.20-gentoo kernel-headers-3.13.0 
glibc-2.21 gcc-4.8.4
vFAIL: test; ppc64/64-bit/MSB linux-3.12.20-gentoo kernel-headers-3.9.0 
glibc-2.17 gcc-4.7.3
vFAIL: test; s390/32-bit/MSB linux-3.18.1 kernel-headers-3.16.0 glibc-2.19 
gcc-4.8.3
vFAIL: test; s390x/64-bit/MSB linux-3.18.1 kernel-headers-3.16.0 glibc-2.19 
gcc-4.8.3
vFAIL: test; sparc/32-bit/MSB linux-3.17.2 kernel-headers-3.13.0 glibc-2.19 
gcc-4.7.3
vPASS: armv7l/32-bit/LSB linux-3.4.0-vapier kernel-headers-3.16.0 glibc-2.19 
gcc-4.7.3
vPASS: x86_64/64-bit/LSB linux-3.18.4 kernel-headers-3.4.0 glibc-2.4 gcc-4.5.4

cross (build only):
vFAIL: build; aarch64/??? cross kernel-headers-3.19.0 glibc-2.21 gcc-4.8.2
vFAIL: build; armv4/??? cross kernel-headers-3.19.0 glibc-2.21 gcc-4.8.0
vFAIL: build; bfin/??? cross kernel-headers-3.5.0 uclibc-0.9.33 gcc-4.5.3
vFAIL: build; bfin-fdpic/??? cross kernel-headers-3.5.0 uclibc-0.9.33 gcc-4.5.3
vFAIL: build; m68k/??? cross kernel-headers-3.19.0 glibc-2.21 gcc-4.8.0
vFAIL: build; mips-n32/??? cross kernel-headers-3.19.0 glibc-2.21 gcc-4.6.4
vFAIL: build; mips-n64/??? cross kernel-headers-3.19.0 glibc-2.21 gcc-4.6.4
vFAIL: build; mips-o32/??? cross kernel-headers-3.19.0 glibc-2.21 gcc-4.6.4
vFAIL: build; sparc64/??? cross kernel-headers-3.19.0 glibc-2.21 gcc-4.6.4
vFAIL: build; tilegx/??? cross kernel-headers-3.19.0 glibc-2.21 gcc-4.8.0
-mike

Attachment: logs.tar.xz
Description: application/xz

Attachment: signature.asc
Description: Digital signature

------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Strace-devel mailing list
Strace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/strace-devel

Reply via email to