similar to: Bug#1065794: xen: FTBFS on armhf: xenstored_control.c:646:70: error: format ‘%ld’ expects argument of type ‘long int’, but argument 5 has type ‘time_t’ {aka ‘long long int’} [-Werror=format=]

Source: xen Version: 4.17.3+10-g091466ba55-1 Severity: serious Tags: patch pending sid trixie Justification: library ABI skew on upgrade User: debian-arm at lists.debian.org Usertags: time-t NOTICE: these changes must not be uploaded to unstable yet! Dear maintainer, As part of the 64-bit time_t transition required to support 32-bit architectures in 2038 and beyond

Source: xen Version: 4.3.0-1 Severity: serious Justification: FTBFS Hi New uploaded xen 4.3.0-1 FTBFS, see [1] for build log for i386. [1] https://buildd.debian.org/status/fetch.php?pkg=xen&arch=i386&ver=4.3.0-1&stamp=1378426577 Regards, Salvatore

Package: src:xen Version: 4.17.3+10-g091466ba55-1~deb12u1 Severity: wishlist I wasn't sure if this script comes from Debian or Xen or somewhere else, so I thought it safest to report it here. IPv6 on the Dom0 should be removed from switched/bridged interfaces. Earlier I would just sysctl disable_ipv6 on the interface, but the below diff seems to remove the link local address too. I've

FYI: The status of the xen source package in Debian's testing distribution has changed. Previous version: 4.17.3+10-g091466ba55-1 Current version: 4.17.3+36-g54dacb5c02-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See

Package: src:xen Version: 4.17.3+10-g091466ba55-1~deb12u1 Severity: wishlist I wasn't sure if this script comes from Debian or Xen or somewhere else, so I thought it safest to report it here. /etc/xen/scripts/vif-bridge handles MTU settings in the vif, but the otherwise similar /etc/xen/scripts/vif-openvswitch does not. I added it in, here's the diff-c and the full fixed file is also

Hi all, I am writing a R extensions, and I need pass time_t to R in C, but I don't know how to do. Can you give me some help? do not use double directly. Thanks, Bill -- *Travel | Programming* *http://freecnpro.net* <http://freecnpro.net> [[alternative HTML version deleted]]

The attached patch adds -Werror to HOSTCFLAGS in Config.mk, makes xen/tools actually use HOSTCFLAGS (it was already using HOSTCC), and fixes some gcc-4.0 signedness warnings in xen/tools/symbols.c. Signed-off-by: Josh Triplett <josht@us.ibm.com> - Josh Triplett _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

On Mon, Dec 15, 2014 at 05:54:51PM +0000, Richard W.M. Jones wrote: > No idea why this happens: > > index-parse.y: In function 'yyparse': > index-parse.c:1256:6: error: assuming pointer wraparound does not occur when comparing P +- C1 with P +- C2 [-Werror=strict-overflow] > if (yyss + yystacksize - 1 <= yyssp) > ^ > > It only happens on one machine,

GCC is concerned that if we never go round the loop then fd will be uninitialized. By asserting that getaddrinfo set result != NULL we can avoid this. nbd.c: In function ‘nbd_open_handle’: nbd.c:974:5: error: ‘fd’ may be used uninitialized in this function [-Werror=maybe-uninitialized] 974 | close (fd); | ^~~~~~~~~~ nbd.c:954:7: note: ‘fd’ was declared here 954 | int fd;

# HG changeset patch # User Olaf Hering <olaf@aepfle.de> # Date 1332942876 -7200 # Node ID d0fe664fca8a7e7db8b46b2f6c267acc88fa9c78 # Parent 4bd752a4cdf323c41c50f8cd6286f566d67adeae tools/memshr: fix build errors caused by Werror -O2 -Wall -Werror triggers these warnings: cc1: warnings being treated as errors interface.c: In function ''memshr_daemon_initialize'':

No idea why this happens: index-parse.y: In function 'yyparse': index-parse.c:1256:6: error: assuming pointer wraparound does not occur when comparing P +- C1 with P +- C2 [-Werror=strict-overflow] if (yyss + yystacksize - 1 <= yyssp) ^ It only happens on one machine, and not on any others, even though they have similar versions of gcc and bison installed. Rich. -- Richard

> # HG changeset patch > # User Olaf Hering <olaf@aepfle.de> > # Date 1332942876 -7200 > # Node ID d0fe664fca8a7e7db8b46b2f6c267acc88fa9c78 > # Parent 4bd752a4cdf323c41c50f8cd6286f566d67adeae > tools/memshr: fix build errors caused by Werror > > -O2 -Wall -Werror triggers these warnings: > > cc1: warnings being treated as errors > interface.c: In function

Could we change the buildbot config to treat warnings-as-errors-that-continue in the build step? (so we get the benefit of further execution tests, while still sending fail-mail, etc for the warning?) On Tue, Mar 22, 2016 at 5:00 PM, David Jones via cfe-dev < cfe-dev at lists.llvm.org> wrote: > Greetings, > > I would like to propose adding a buildbot which builds with -Werror. The

On Tue, Mar 22, 2016 at 5:06 PM Hal Finkel via llvm-dev < llvm-dev at lists.llvm.org> wrote: > I think having -Werror bots is a good idea, at least when self hosting. > Non-self-hosting -Werror (i.e. with older versions of Clang, or with GCC, > etc.) might also be useful, but I'm less sure (since we can't fix those > warnings if the warning is the problem). On Tue, Mar

On Tue, Mar 22, 2016 at 5:03 PM, David Blaikie <dblaikie at gmail.com> wrote: > Could we change the buildbot config to treat > warnings-as-errors-that-continue in the build step? (so we get the benefit > of further execution tests, while still sending fail-mail, etc for the > warning?) > > That sounds reasonable, although the buildbot implementation seems to be pretty

I just changed this build on green dragon to warn and email if warnings are found in the console log: http://lab.llvm.org:8080/green/job/clang-stage1-cmake-RA_build/ > On Mar 22, 2016, at 6:24 PM, David Jones via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > On Tue, Mar 22, 2016 at 5:06 PM Hal Finkel via llvm-dev <llvm-dev at lists.llvm.org <mailto:llvm-dev at

Package: xen Version: 4.1.0-3 Severity: important Tags: wheezy sid User: debian-gcc at lists.debian.org Usertags: ftbfs-gcc-4.6 ftbfs-werror This package builds with -Werror, and GCC 4.6 triggers new warnings which will make the package fail to build. Currently a Debian patch just passes -Wno-error=unused-but-set-variable and -Wno-error=unused-but-set-parameter to avoid build failures,

From: Gene Cumm <gene.cumm at gmail.com> Fix several calls to more_printf() as eventually printf() is called without a literal string which generate warnings with gcc and lead to errors when -Werror is active. Signed-off-by: Gene Cumm <gene.cumm at gmail.com> The message "format not a string literal and no format arguments" at first seems strange but by doing this change

----- Original Message ----- > From: "David Jones via cfe-dev" <cfe-dev at lists.llvm.org> > To: cfe-dev at lists.llvm.org, llvm-dev at lists.llvm.org > Cc: gkistanova at gmail.com > Sent: Tuesday, March 22, 2016 7:00:28 PM > Subject: [cfe-dev] New buildbot with -Werror > > Greetings, > > > I would like to propose adding a buildbot which builds with

My thought was that its reasonable to expect no warnings when building from bootstrap (as you say) and the last release of Clang. Generally, I think we should work around warnings in the last release of Clang if only for the convenience of folks using that release to build stage1 and using Werror. Certainly, we tend to fix warnings even from earlier Clang versions and from GCC in order to keep