From: Roger Pau Monne <roger.pau@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: "andrew.cooper3@citrix.com" <andrew.cooper3@citrix.com>,
Razvan Cojocaru <rcojocaru@bitdefender.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: build issue on staging (was Re: [PATCH V5] x86/vm_event: Added support for VM_EVENT_REASON_INTERRUPT)
Date: Tue, 13 Dec 2016 17:15:56 +0000 [thread overview]
Message-ID: <20161213171556.c72fai4piu72gs3t@dhcp-3-221.uk.xensource.com> (raw)
In-Reply-To: <5850195E0200007800128ADF@prv-mh.provo.novell.com>
On Tue, Dec 13, 2016 at 07:53:02AM -0700, Jan Beulich wrote:
> >>> On 13.12.16 at 15:17, <rcojocaru@bitdefender.com> wrote:
> > While re-basing the patch on staging, I've got this (unrelated) error
> > while doing 'make dist':
> >
> > make[9]: Entering directory `~/work/xen.git/tools/firmware/rombios/32bit'
> > gcc -m32 -march=i686 -DBUILD_ID -g -fno-strict-aliasing -std=gnu99
> > -Wall -Wstrict-prototypes -Wdeclaration-after-statement
> > -Wno-unused-but-set-variable -Wno-unused-local-typedefs -O0 -g3
> > -fno-omit-frame-pointer
> > -D__XEN_INTERFACE_VERSION__=__XEN_LATEST_INTERFACE_VERSION__ -MMD -MF
> > .util.o.d -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE
> > -mno-tls-direct-seg-refs -Werror -fno-stack-protector -fno-exceptions
> > -fno-builtin -msoft-float
> > -I/home/red/work/xen.git/tools/firmware/rombios/32bit/../../../../tools/inclu
> > de
> > -I.. -I../../../libacpi -c -o util.o util.c
> > util.c: In function ‘get_s3_waking_vector’:
> > util.c:453:23: error: dereferencing pointer to incomplete type
> > if (!fadt || (fadt->header.signature != ACPI_2_0_FADT_SIGNATURE))
> > ^
> > util.c:453:45: error: ‘ACPI_2_0_FADT_SIGNATURE’ undeclared (first use in
> > this function)
> > if (!fadt || (fadt->header.signature != ACPI_2_0_FADT_SIGNATURE))
> > ^
> > util.c:453:45: note: each undeclared identifier is reported only once
> > for each function it appears in
> > util.c:456:45: error: dereferencing pointer to incomplete type
> > facs = (struct acpi_20_facs *)(long)fadt->x_firmware_ctrl;
> > ^
> > make[9]: *** [util.o] Error 1
>
> Roger, this indicates you didn't build everything that can be built
> with the libacpi changes which went in today. Please indicate
> whether you think a fix is easy to put together, or whether to
> revert.
Hello,
Sorry, rombios doesn't build on FreeBSD, neither I was expecting libacpi headers
to leak into it (TBH it looks like a layering violantion). Just send a patch to
fix the build.
Roger.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2016-12-13 17:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-11 16:09 [PATCH V5] x86/vm_event: Added support for VM_EVENT_REASON_INTERRUPT Razvan Cojocaru
2016-11-11 16:31 ` Jan Beulich
2016-11-16 7:22 ` Tian, Kevin
2016-11-16 7:48 ` Razvan Cojocaru
2016-11-17 5:11 ` Tian, Kevin
2016-12-13 8:50 ` Razvan Cojocaru
2016-12-13 9:09 ` Jan Beulich
2016-12-13 9:14 ` Razvan Cojocaru
2016-12-13 12:53 ` Julien Grall
2016-12-13 10:34 ` Suravee Suthikulpanit
2016-12-13 13:18 ` Jan Beulich
2016-12-13 13:42 ` Razvan Cojocaru
2016-12-13 14:17 ` Razvan Cojocaru
2016-12-13 14:53 ` build issue on staging (was Re: [PATCH V5] x86/vm_event: Added support for VM_EVENT_REASON_INTERRUPT) Jan Beulich
2016-12-13 17:15 ` Roger Pau Monne [this message]
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=20161213171556.c72fai4piu72gs3t@dhcp-3-221.uk.xensource.com \
--to=roger.pau@citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=rcojocaru@bitdefender.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 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).