From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Jan Beulich" Subject: Re: Build problems with xen 4.7 Date: Tue, 01 Dec 2015 09:09:10 -0700 Message-ID: <565DD43602000078000BAEA1@prv-mh.provo.novell.com> References: <565DAC7402000078000BACE9@prv-mh.provo.novell.com> <5BB49958-6315-4EAA-967C-73FC9B442B73@oracle.com> <565DD12302000078000BAE6B@prv-mh.provo.novell.com> <20151201155941.GG19885@char.us.oracle.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20151201155941.GG19885@char.us.oracle.com> Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Konrad Rzeszutek Wilk Cc: Marcos Matsunaga , xen-devel@lists.xen.org, M A Young List-Id: xen-devel@lists.xenproject.org >>> On 01.12.15 at 16:59, wrote: > On Tue, Dec 01, 2015 at 08:56:03AM -0700, Jan Beulich wrote: >> >>> On 01.12.15 at 15:36, wrote: >> > On December 1, 2015 8:19:32 AM EST, Jan Beulich wrote: >> >>>>> On 01.12.15 at 00:37, wrote: >> >>> When I try to build the current xen 4.7 master I get the following >> >>error >> >>> >> >>> :0:0: error: "__OBJECT_FILE__" redefined [-Werror] >> >>> :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. I.e. there must be something different in how make gets invoked or the environment set up. Jan