xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Sander Eikelenboom <linux@eikelenboom.it>,
	stefano.stabellini@eu.citrix.com, xen-devel@lists.xenproject.org
Subject: Re: xen-unstable stubdom build-failure when debug=n
Date: Mon, 21 Jul 2014 18:31:26 +0200	[thread overview]
Message-ID: <20140721163126.GA26816@aepfle.de> (raw)
In-Reply-To: <20140721162118.GA20873@aepfle.de>

On Mon, Jul 21, Olaf Hering wrote:

> On Mon, Jul 21, Ian Campbell wrote:
> 
> > If that were the case then I'd expect
> >         git clean -ffffdqx && ./configure && make debug=n ; make debug=n
> > to work as well, which it doesn't seem to.
> > 
> > My guest is that turning off debug increases the optimisation level
> > which somehow makes gcc decide this code is now wrong.
> 
> How does stubdom the build tests anyway?

Here is the actual log:

[  6%] Building C object tpm/CMakeFiles/tpm.dir/tpm_credentials.o
cd /home/olaf/work/github/olafhering/xen/stubdom/tpm_emulator-x86_64/build/tpm && /usr/bin/gcc   -std=c99 -DTPM_NO_EXTERN -isystem /home/olaf/work/github/olafhering/xen/stubdom/../extras/mini-os/include -D__MINIOS__ -DHAVE_LIBC -isystem /home/olaf/work/github/olafhering/xen/stubdom/../extras/mini-os/include/posix -isystem /home/olaf/work/github/olafhering/xen/stubdom/../tools/xenstore  -isystem /home/olaf/work/github/olafhering/xen/stubdom/../extras/mini-os/include/x86 -isystem /home/olaf/work/github/olafhering/xen/stubdom/../extras/mini-os/include/x86/x86_64 -U __linux__ -U __FreeBSD__ -U __sun__ -nostdinc -isystem /home/olaf/work/github/olafhering/xen/stubdom/../extras/mini-os/include/posix -isystem /home/olaf/work/github/olafhering/xen/stubdom/cross-root-x86_64/x86_64-xen-elf/include -i
 system /usr/lib64/gcc/x86_64-suse-linux/4.3/include -isystem /home/olaf/work/github/olafhering/xen/stubdom/lwip-x86_64/src/include -isystem /home/olaf/work/github/olafhering/xen/stubdom/lwip-x86_64/src/include/ipv4 -I/home/olaf/work/github/olafhering/xen/stubdom/include -I/home/olaf/work/github/olafhering/xen/stubdom/../xen/include -mno-red-zone -O2 -O1 -fomit-frame-pointer  -m64 -mno-red-zone -fno-reorder-blocks -fno-asynchronous-unwind-tables -m64 -fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes -Wdeclaration-after-statement   -fno-stack-protector -fno-exceptions -Wno-declaration-after-statement -I/opt/local/include -I/home/olaf/work/github/olafhering/xen/stubdom/tpm_emulator-x86_64 -I/home/olaf/work/github/olafhering/xen/stubdom/tpm_emulator-x86_64/build   -Wall -Werror -Wno-
 unused-parameter -Wpointer-arith -Wcast-align -Wwrite-strings -Wextra -o CMakeFiles/tpm.dir/tpm_credentials.o   -c /home/olaf/work/github/olafhering/xen/stubdom/tpm_emulator-x86_64/tpm/tpm_credentials.c
cc1: warnings being treated as errors
/home/olaf/work/github/olafhering/xen/stubdom/tpm_emulator-x86_64/tpm/tpm_credentials.c: In function 'TPM_CreateEndorsementKeyPair':
/home/olaf/work/github/olafhering/xen/stubdom/tpm_emulator-x86_64/tpm/tpm_credentials.c:52: error: unused parameter 'antiReplay'
/home/olaf/work/github/olafhering/xen/stubdom/tpm_emulator-x86_64/tpm/tpm_credentials.c:53: error: unused parameter 'keyInfo'
/home/olaf/work/github/olafhering/xen/stubdom/tpm_emulator-x86_64/tpm/tpm_credentials.c:54: error: unused parameter 'pubEndorsementKey'
/home/olaf/work/github/olafhering/xen/stubdom/tpm_emulator-x86_64/tpm/tpm_credentials.c:55: error: unused parameter 'checksum'
make[5]: *** [tpm/CMakeFiles/tpm.dir/tpm_credentials.o] Error 1


Why does that only fail for me?
Is "-Wall -Werror -Wextra" different in sles11?

Looks like it should fail everywhere:
stubdom/tpm_emulator-x86_64/CMakeLists.txt
 43 add_definitions(-Wall -Werror -Wno-unused-parameter -Wpointer-arith -Wcast-align -Wwrite-strings)
 44 if("${CMAKE_SYSTEM}" MATCHES "Linux")
 45     add_definitions(-Wextra)
 46 endif()

Olaf

  parent reply	other threads:[~2014-07-21 16:31 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-17  8:27 xen-unstable stubdom build-failure when debug=n Sander Eikelenboom
2014-07-17 14:13 ` Ian Campbell
2014-07-17 14:25   ` Sander Eikelenboom
2014-07-21 16:13     ` Ian Campbell
2014-07-21 16:21       ` Olaf Hering
2014-07-21 16:27         ` Ian Campbell
2014-07-22  7:09           ` Olaf Hering
2014-07-21 16:31         ` Olaf Hering [this message]
2014-07-21 16:43           ` Olaf Hering
2014-07-21 16:48             ` Ian Campbell
2014-07-21 16:51               ` Olaf Hering
2014-07-21 16:24       ` Ian Campbell
2014-07-21 17:43         ` Olaf Hering
2014-07-21 18:13           ` Daniel De Graaf
2014-07-22  6:13             ` Olaf Hering
2014-07-22  7:11         ` Sander Eikelenboom
2014-07-26 15:14           ` Sander Eikelenboom
2014-07-28  9:09             ` Ian Campbell
2014-07-28  9:47               ` Sander Eikelenboom
2014-07-28  9:51                 ` Ian Campbell
2014-07-28  9:55                 ` Olaf Hering
2014-07-28  9:22           ` Ian Campbell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140721163126.GA26816@aepfle.de \
    --to=olaf@aepfle.de \
    --cc=Ian.Campbell@citrix.com \
    --cc=linux@eikelenboom.it \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xenproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).