From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Marcos Matsunaga <marcos.matsunaga@oracle.com>,
xen-devel@lists.xen.org, M A Young <m.a.young@durham.ac.uk>
Subject: Re: Build problems with xen 4.7
Date: Tue, 1 Dec 2015 10:59:41 -0500 [thread overview]
Message-ID: <20151201155941.GG19885@char.us.oracle.com> (raw)
In-Reply-To: <565DD12302000078000BAE6B@prv-mh.provo.novell.com>
On Tue, Dec 01, 2015 at 08:56:03AM -0700, Jan Beulich wrote:
> >>> On 01.12.15 at 15:36, <konrad.wilk@oracle.com> wrote:
> > On December 1, 2015 8:19:32 AM EST, Jan Beulich <JBeulich@suse.com> wrote:
> >>>>> On 01.12.15 at 00:37, <m.a.young@durham.ac.uk> wrote:
> >>> When I try to build the current xen 4.7 master I get the following
> >>error
> >>>
> >>> <command-line>:0:0: error: "__OBJECT_FILE__" redefined [-Werror]
> >>> <command-line>:0:0: note: this is the location of the previous
> >>definition
> >>> cc1: all warnings being treated as errors
> >>>
> >>> The problem seems to be that -D__OBJECT_FILE__= is set each time
> >>> xen/Rules.mk is called, which happens more than once because of
> >>nested
> >>> makes resulting in multiple diffent values for -D__OBJECT_FILE__=
> >>
> >>Considering you're the first one to have such a problem, I think the
> >>precise compiler version you use matters here. Also the redundant
> >>definitions shouldn't be different, and identical re-definition should
> >>not yield a diagnostic. So I think there's a little more data you need
> >>to supply in order to determine whether we need to adjust something.
> >>
> >
> > Ccing Marcos who also saw this. Marcos do you remember the git commit that
> > caused this?
>
> There's no question about when this got introduced. What we need
> to understand is why this is an issue only for very few people.
It is only an issue when doing rpmbuilds.
Not when doing the build outside of that.
>
> Jan
>
next prev parent reply other threads:[~2015-12-01 15:59 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-30 23:37 Build problems with xen 4.7 M A Young
2015-12-01 13:19 ` Jan Beulich
2015-12-01 14:36 ` Konrad Rzeszutek Wilk
2015-12-01 14:50 ` Marcos E. Matsunaga
2015-12-01 15:56 ` Jan Beulich
2015-12-01 15:59 ` Konrad Rzeszutek Wilk [this message]
2015-12-01 16:09 ` Jan Beulich
2015-12-01 18:47 ` M A Young
2015-12-01 19:40 ` Olaf Hering
2015-12-01 19:53 ` Andrew Cooper
2015-12-02 10:05 ` Jan Beulich
2016-05-13 13:49 ` Konrad Rzeszutek Wilk
2016-05-13 14:01 ` Jan Beulich
2016-05-13 14:25 ` M A Young
2016-05-13 15:23 ` Konrad Rzeszutek Wilk
2016-05-31 18:27 ` George Dunlap
2016-05-31 20:57 ` Konrad Rzeszutek Wilk
2016-06-03 11:20 ` George Dunlap
2016-06-03 17:03 ` Konrad Rzeszutek Wilk
2016-06-07 10:35 ` George Dunlap
2016-06-07 10:42 ` M A Young
2016-06-07 10:50 ` George Dunlap
2016-06-07 11:33 ` Doug Goldstein
2016-06-07 13:48 ` George Dunlap
2016-06-07 14:00 ` Olaf Hering
2016-06-07 14:04 ` George Dunlap
2016-06-07 14:10 ` Olaf Hering
2016-06-08 10:20 ` George Dunlap
2016-06-07 10:43 ` Jan Beulich
2016-06-07 10:52 ` M A Young
2016-08-08 14:37 ` Peng Fan
2016-08-08 19:22 ` M A Young
2015-12-01 14:49 ` M A Young
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=20151201155941.GG19885@char.us.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=JBeulich@suse.com \
--cc=m.a.young@durham.ac.uk \
--cc=marcos.matsunaga@oracle.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).