All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: Wei Liu <wei.liu2@citrix.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>, xen-devel@lists.xen.org
Subject: Re: staging: libxl compile error in libxl__domain_save
Date: Sat, 27 Feb 2016 16:25:31 +0100	[thread overview]
Message-ID: <20160227152531.GA15754@aepfle.de> (raw)
In-Reply-To: <20160227144410.GB20235@citrix.com>

On Sat, Feb 27, Wei Liu wrote:

> And fwiw even if I manually added that option to libxl build, gcc
> doesn't complain.

Well, Debian is appearently not the first choice anymore...

My cmdline is like this, fails with gcc4.3 ... 5.3:

 gcc  -O1 -fno-omit-frame-pointer -m64 -g -fno-strict-aliasing -std=gnu99 -Wall
-Wstrict-prototypes -Wdeclaration-after-statement -Wno-unused-but-set-variable
-Wno-unused-local-typedefs   -O0 -g3
-D__XEN_INTERFACE_VERSION__=__XEN_LATEST_INTERFACE_VERSION__ -MMD -MF
.libxl_dom_save.o.d -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE
-fno-optimize-sibling-calls -fmessage-length=0 -grecord-gcc-switches -O2 -Wall
-D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables
-fasynchronous-unwind-tables -g -Werror -Wno-format-zero-length
-Wmissing-declarations -Wno-declaration-after-statement -Wformat-nonliteral -I.
-fPIC -pthread
-I/home/abuild/rpmbuild/BUILD/xen-4.7.20160226T190133.3dd926a/non-dbg/tools/libxl/../../tools/libs/toollog/include
-I/home/abuild/rpmbuild/BUILD/xen-4.7.20160226T190133.3dd926a/non-dbg/tools/libxl/../../tools/include
-I/home/abuild/rpmbuild/BUILD/xen-4.7.20160226T190133.3dd926a/non-dbg/tools/libxl/../../tools/libs/evtchn/include
-I/home/abuild/rpmbuild/BUILD/xen-4.7.20160226T190133.3dd926a/non-dbg/tools/libxl/../../tools/include
-I/home/abuild/rpmbuild/BUILD/xen-4.7.20160226T190133.3dd926a/non-dbg/tools/libxl/../../tools/libxc/include
-I/home/abuild/rpmbuild/BUILD/xen-4.7.20160226T190133.3dd926a/non-dbg/tools/libxl/../../tools/libs/toollog/include
-I/home/abuild/rpmbuild/BUILD/xen-4.7.20160226T190133.3dd926a/non-dbg/tools/libxl/../../tools/include
-I/home/abuild/rpmbuild/BUILD/xen-4.7.20160226T190133.3dd926a/non-dbg/tools/libxl/../../tools/libs/foreignmemory/include
-I/home/abuild/rpmbuild/BUILD/xen-4.7.20160226T190133.3dd926a/non-dbg/tools/libxl/../../tools/include
-I/home/abuild/rpmbuild/BUILD/xen-4.7.20160226T190133.3dd926a/non-dbg/tools/libxl/../../tools/include
-D__XEN_TOOLS__
-I/home/abuild/rpmbuild/BUILD/xen-4.7.20160226T190133.3dd926a/non-dbg/tools/libxl/../../tools/libxc/include
-I/home/abuild/rpmbuild/BUILD/xen-4.7.20160226T190133.3dd926a/non-dbg/tools/libxl/../../tools/libs/evtchn/include
-I/home/abuild/rpmbuild/BUILD/xen-4.7.20160226T190133.3dd926a/non-dbg/tools/libxl/../../tools/include
-I/home/abuild/rpmbuild/BUILD/xen-4.7.20160226T190133.3dd926a/non-dbg/tools/libxl/../../tools/libs/foreignmemory/include
-I/home/abuild/rpmbuild/BUILD/xen-4.7.20160226T190133.3dd926a/non-dbg/tools/libxl/../../tools/include
-I/home/abuild/rpmbuild/BUILD/xen-4.7.20160226T190133.3dd926a/non-dbg/tools/libxl/../../tools/include
-I/home/abuild/rpmbuild/BUILD/xen-4.7.20160226T190133.3dd926a/non-dbg/tools/libxl/../../tools/xenstore/include
-I/home/abuild/rpmbuild/BUILD/xen-4.7.20160226T190133.3dd926a/non-dbg/tools/libxl/../../tools/include
-I/home/abuild/rpmbuild/BUILD/xen-4.7.20160226T190133.3dd926a/non-dbg/tools/libxl/../../tools/blktap2/control
-I/home/abuild/rpmbuild/BUILD/xen-4.7.20160226T190133.3dd926a/non-dbg/tools/libxl/../../tools/blktap2/include
-I/home/abuild/rpmbuild/BUILD/xen-4.7.20160226T190133.3dd926a/non-dbg/tools/libxl/../../tools/include
-I/usr/include/libnl3  -Wshadow -include
/home/abuild/rpmbuild/BUILD/xen-4.7.20160226T190133.3dd926a/non-dbg/tools/libxl/../../tools/config.h
-c -o libxl_dom_save.o libxl_dom_save.c

Olaf

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2016-02-27 15:25 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-27  8:14 staging: libxl compile error in libxl__domain_save Olaf Hering
2016-02-27 12:35 ` Andrew Cooper
2016-02-27 14:44   ` Wei Liu
2016-02-27 15:25     ` Olaf Hering [this message]
2016-02-28  9:39       ` Olaf Hering
2016-02-28 15:47         ` Wei Liu
2016-02-28 15:55           ` Andrew Cooper
2016-02-29  6:54           ` Olaf Hering
2016-02-29  9:59             ` Andrew Cooper
2016-02-29 10:32               ` Olaf Hering
2016-02-27 13:47 ` Wei Liu
2016-02-27 14:18   ` Wei Liu
2016-02-28  2:01 ` Doug Goldstein
2016-02-28 14:10   ` Andrew Cooper
2016-02-28 20:20     ` Doug Goldstein
2016-02-28 21:06     ` Konrad Rzeszutek Wilk

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=20160227152531.GA15754@aepfle.de \
    --to=olaf@aepfle.de \
    --cc=andrew.cooper3@citrix.com \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.