All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jerone Young <jyoung5@us.ibm.com>
To: "Nakajima, Jun" <jun.nakajima@intel.com>
Cc: David F Barrera <dfbp@us.ibm.com>,
	Xen Development List <xen-devel@lists.xensource.com>
Subject: RE: x86_64 build broken?
Date: Mon, 16 May 2005 12:58:49 -0500	[thread overview]
Message-ID: <1116266329.4807.55.camel@thinkpad> (raw)
In-Reply-To: <7F740D512C7C1046AB53446D3720017303FE5C78@scsmsx402.amr.corp.intel.com>

I can look at this.

On Mon, 2005-05-16 at 10:49 -0700, Nakajima, Jun wrote:
> Jerone,
> 
> Do you want to look at this? Or is anyone working on this?
> 
> Jun
> -----Original Message-----
> From: xen-devel-bounces@lists.xensource.com
> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of David F
> Barrera
> Sent: Monday, May 16, 2005 10:39 AM
> To: Puthiyaparambil, Aravindh
> Cc: Xen Development List
> Subject: Re: [Xen-devel] x86_64 build broken?
> 
> On Mon, 2005-05-16 at 13:33 -0400, Puthiyaparambil, Aravindh wrote:
> > I am not able to build the latest x86_64 xen-unstable on SLES9 SP1
> > x86_64. Here is the build output. Am I doing anything wrong here?
> 
> No, I am seeing the same thing. There is a defect open in the Xensource
> Bugzilla, http://bugzilla.xensource.com/cgi-bin/bugzilla/show_bug.cgi?
> id=34
> 
> > 
> > Aravindh
> > 
> > gcc  -DPIC  -m64 -Wall -Werror -O3 -fno-strict-aliasing -
> > I ../../tools/libxutil -I. -Wp,-MD,.xc_ptrace.opic.d -fPIC -c -o
> > xc_ptrace.opic xc_ptrace.c
> > 
> > In file included from /usr/include/asm/sigcontext.h:4,
> > 
> >                  from /usr/include/asm-x86_64/processor.h:13,
> > 
> >                  from /usr/include/asm/processor.h:4,
> > 
> >                  from /usr/include/asm-x86_64/elf.h:10,
> > 
> >                  from /usr/include/asm/elf.h:4,
> > 
> >                  from xc_ptrace.c:4:
> > 
> > /usr/include/asm-x86_64/sigcontext.h:9: error: redefinition of `struct
> > _fpstate'
> > 
> > /usr/include/asm-x86_64/sigcontext.h:23: error: redefinition of
> > `struct sigcontext'
> > 
> > In file included from /usr/include/asm/pda.h:4,
> > 
> >                  from /usr/include/asm-x86_64/current.h:7,
> > 
> >                  from /usr/include/asm/current.h:4,
> > 
> >                  from /usr/include/asm-x86_64/processor.h:18,
> > 
> >                  from /usr/include/asm/processor.h:4,
> > 
> >                  from /usr/include/asm-x86_64/elf.h:10,
> > 
> >                  from /usr/include/asm/elf.h:4,
> > 
> >                  from xc_ptrace.c:4:
> > 
> > /usr/include/asm-x86_64/pda.h:26: error: `CONFIG_X86_L1_CACHE_SHIFT'
> > undeclared here (not in a function)
> > 
> > /usr/include/asm-x86_64/pda.h:26: error: requested alignment is not a
> > constant
> > 
> > In file included from /usr/include/asm/system.h:4,
> > 
> >                  from /usr/include/asm-x86_64/processor.h:19,
> > 
> >                  from /usr/include/asm/processor.h:4,
> > 
> >                  from /usr/include/asm-x86_64/elf.h:10,
> > 
> >                  from /usr/include/asm/elf.h:4,
> > 
> >                  from xc_ptrace.c:4:
> > 
> > /usr/include/asm-x86_64/system.h: In function `__cmpxchg':
> > 
> > /usr/include/asm-x86_64/system.h:249: error: `LOCK_PREFIX' undeclared
> > (first use in this function)
> > 
> > /usr/include/asm-x86_64/system.h:249: error: (Each undeclared
> > identifier is reported only once
> > 
> > /usr/include/asm-x86_64/system.h:249: error: for each function it
> > appears in.)
> > 
> > /usr/include/asm-x86_64/system.h:249: error: parse error before string
> > constant
> > 
> > /usr/include/asm-x86_64/system.h:255: error: parse error before string
> > constant
> > 
> > /usr/include/asm-x86_64/system.h:261: error: parse error before string
> > constant
> > 
> > /usr/include/asm-x86_64/system.h:267: error: parse error before string
> > constant
> > 
> > In file included from /usr/include/asm/processor.h:4,
> > 
> >                  from /usr/include/asm-x86_64/elf.h:10,
> > 
> >                  from /usr/include/asm/elf.h:4,
> > 
> >                  from xc_ptrace.c:4:
> > 
> > /usr/include/asm-x86_64/processor.h: At top level:
> > 
> > /usr/include/asm-x86_64/processor.h:229: error:
> > `CONFIG_X86_L1_CACHE_SHIFT' undeclared here (not in a function)
> > 
> > /usr/include/asm-x86_64/processor.h:229: error: requested alignment is
> > not a constant
> > 
> > /usr/include/asm-x86_64/processor.h: In function `prefetchw':
> > 
> > /usr/include/asm-x86_64/processor.h:396: error: called object is not a
> > function
> > 
> > make[4]: *** [xc_ptrace.opic] Error 1
> > 
> > make[4]: Leaving directory `/root/xen/xeno-unstable.bk/tools/libxc'
> > 
> > make[3]: *** [build] Error 2
> > 
> > make[3]: Leaving directory `/root/xen/xeno-unstable.bk/tools/libxc'
> > 
> > make[2]: *** [install] Error 2
> > 
> > make[2]: Leaving directory `/root/xen/xeno-unstable.bk/tools'
> > 
> > make[1]: *** [tools] Error 2
> > 
> > make[1]: Leaving directory `/root/xen/xeno-unstable.bk'
> > 
> > make: *** [world] Error 2
> > 
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xensource.com
> > http://lists.xensource.com/xen-devel
-- 
Jerone Young
IBM Linux Technology Center
jyoung5@us.ibm.com
512-838-1157 (T/L: 678-1157)

  reply	other threads:[~2005-05-16 17:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-16 17:49 x86_64 build broken? Nakajima, Jun
2005-05-16 17:58 ` Jerone Young [this message]
2005-05-16 18:02   ` Kip Macy
  -- strict thread matches above, loose matches on Subject: below --
2005-05-16 18:47 Nakajima, Jun
2005-05-16 18:33 Nakajima, Jun
2005-05-16 17:33 Puthiyaparambil, Aravindh
2005-05-16 17:38 ` David F Barrera

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=1116266329.4807.55.camel@thinkpad \
    --to=jyoung5@us.ibm.com \
    --cc=dfbp@us.ibm.com \
    --cc=jun.nakajima@intel.com \
    --cc=xen-devel@lists.xensource.com \
    /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.