Re: Fwd: [Xen-ia64-devel] Installing XEN/ia64 on Debian

["Rodrigo Lord" <lord.listas@xxxxxxxxx>]

Hello!

I fixed the HAVE_SERIALIZE_DIRECTIVE as you talked! It`s ok! :)
But... when it was almost finishing (make world), the following error occurred:

.
.
.
AS      arch/ia64/lib/strncpy_from_user.o
  AS      arch/ia64/lib/strnlen_user.o
  AR      arch/ia64/lib/lib.a
  GEN     .version
  CHK     include/linux/compile.h
  UPD     include/linux/compile.h
  CC      init/version.o
  LD      init/built-in.o
  LD      .tmp_vmlinux1
drivers/built-in.o(.text+0x92f12): In function `acpi_rs_convert_aml_to_resource':
: undefined reference to `acpi_rs_move_data'
drivers/built-in.o(.text+0x93062): In function `acpi_rs_convert_aml_to_resource':
: undefined reference to `acpi_rs_get_resource_source'
drivers/built-in.o(.text+0x930e2): In function `acpi_rs_convert_aml_to_resource':
: undefined reference to `acpi_rs_decode_bitmask'
drivers/built-in.o(.text+0x933c2): In function `acpi_rs_convert_resource_to_aml':
: undefined reference to `acpi_rs_set_resource_header'
drivers/built-in.o(.text+0x93582): In function `acpi_rs_convert_resource_to_aml':
: undefined reference to `acpi_rs_move_data'
drivers/built-in.o(.text+0x93602): In function `acpi_rs_convert_resource_to_aml':
: undefined reference to `acpi_rs_set_resource_source'
drivers/built-in.o(.text+0x93622): In function `acpi_rs_convert_resource_to_aml':
: undefined reference to `acpi_rs_set_resource_length'
drivers/built-in.o(.text+0x93662): In function `acpi_rs_convert_resource_to_aml':
: undefined reference to `acpi_rs_encode_bitmask'
drivers/built-in.o(.text+0x936a2): In function `acpi_rs_convert_resource_to_aml':
: undefined reference to `acpi_rs_encode_bitmask'
drivers/built-in.o(.text+0x93872): In function `acpi_get_irq_routing_table':
: undefined reference to `acpi_rs_get_prt_method_data'
drivers/built-in.o(.text+0x93912): In function `acpi_get_current_resources':
: undefined reference to `acpi_rs_get_crs_method_data'
drivers/built-in.o(.text+0x93a52): In function `acpi_walk_resources':
: undefined reference to `acpi_rs_get_method_data'
drivers/built-in.o(.text+0x93c52): In function `acpi_set_current_resources':
: undefined reference to `acpi_rs_set_srs_method_data'
make[4]: ** [.tmp_vmlinux1] Erro 1
make[4]: Saindo do diretório `/home/peso/xen-ia64-unstable.hg/linux-2.6.16-xen'
make[3]: ** [build] Erro 2
make[3]: Saindo do diretório `/home/peso/xen-ia64-unstable.hg'
make[2]: ** [linux-2.6-xen-install] Erro 2
make[2]: Saindo do diretório `/home/peso/xen-ia64-unstable.hg'
make[1]: ** [install-kernels] Erro 1
make[1]: Saindo do diretório `/home/peso/xen-ia64-unstable.hg'
make: ** [world] Erro 2

Thanks! :)

2006/5/3, Tristan Gingold <Tristan.Gingold@xxxxxxxx>:

Le Mardi 02 Mai 2006 14:42, Rodrigo Lord a écrit :
> ---------- Forwarded message ----------
> From: Rodrigo Lord <lord.listas@xxxxxxxxx>
> Date: 02/05/2006 09:39
> Subject: Re: [Xen-ia64-devel] Installing XEN/ia64 on Debian
> To: "Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>
>
> Hello again! :)
Hi,

>
> I tryied to update my bin-utils, but it`s updated! :)
What is the version of your binutils ?  try as --version.

> So, I look at xen/include/asm-ia64/linux/asm/asmmacro.h. but I don`t know
> about ASM. :(
>
> Anybody that have XEN/ia64 installed on your Debian can help me?
Undef HAVE_SERIALIZE_DIRECTIVE in xen/include/asm-ia64/config.h

Tristan.

>
> Thanks!
>
> 2006/4/28, Magenheimer, Dan (HP Labs Fort Collins) <dan.magenheimer@xxxxxx>:
> >  Hmmm... perhaps you need to update your bin-utils?
> >
> > As a workaround, look at HAVE_SERIALIZE_DIRECTIVE in
> > xen/include/asm-ia64/linux/asm/asmmacro.h.
> > All the warnings are harmless if you can avoid that one error message.
> >
> > Dan
> >
> >  ------------------------------
> > *From:* xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx [mailto:
> > xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx ] *On Behalf Of *Rodrigo Lord
> > *Sent:* Friday, April 28, 2006 8:44 AM
> > *To:* Yang, Fred
> >
> > *Cc:* xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> > *Subject:* Re: [Xen-ia64-devel] Installing XEN/ia64 on Debian
> >
> > Hello!
> >
> > I tryied to install XEN using this method, but when in the step "make
> > world", happens the error below:
> >
> > hyperprivop.S:69:2: warning: #warning "FIXME: ptc.ga instruction requires
> > spinlock for SMP"
> > hyperprivop.S: Assembler messages:
> > hyperprivop.S:2089: Error: unknown pseudo-op: `.serialize.data'
> > hyperprivop.S:2096: Warning: Use of 'st8' violates RAW dependency 'DTC'
> > (data)
> > hyperprivop.S:2096: Warning: Only the first path encountering the
> > conflict is reported
> > hyperprivop.S:2087: Warning: This is the location of the conflicting
> > usage hyperprivop.S:2096: Warning: Use of 'st8' violates RAW dependency
> > 'DTC' (data)
> > hyperprivop.S:2096: Warning: Only the first path encountering the
> > conflict is reported
> > hyperprivop.S:2088: Warning: This is the location of the conflicting
> > usage hyperprivop.S :2098: Warning: Use of 'st8' violates RAW dependency
> > 'DTC' (data)
> > hyperprivop.S:2098: Warning: Only the first path encountering the
> > conflict is reported
> > hyperprivop.S:2087: Warning: This is the location of the conflicting
> > usage hyperprivop.S:2098: Warning: Use of 'st8' violates RAW dependency
> > 'DTC' (data)
> > hyperprivop.S:2098: Warning: Only the first path encountering the
> > conflict is reported
> > hyperprivop.S:2088: Warning: This is the location of the conflicting
> > usage hyperprivop.S:2099: Warning: Use of 'st8' violates RAW dependency
> > 'DTC' (data)
> > hyperprivop.S:2099: Warning: Only the first path encountering the
> > conflict is reported
> > hyperprivop.S:2087: Warning: This is the location of the conflicting
> > usage hyperprivop.S:2099: Warning: Use of 'st8' violates RAW dependency
> > 'DTC' (data)
> > hyperprivop.S:2099: Warning: Only the first path encountering the
> > conflict is reported
> > hyperprivop.S:2088: Warning: This is the location of the conflicting
> > usage hyperprivop.S :2104: Warning: Use of 'ld8' violates RAW dependency
> > 'DTC' (data)
> > hyperprivop.S:2104: Warning: Only the first path encountering the
> > conflict is reported
> > hyperprivop.S:2087: Warning: This is the location of the conflicting
> > usage hyperprivop.S:2104: Warning: Use of 'ld8' violates RAW dependency
> > 'DTC' (data)
> > hyperprivop.S:2104: Warning: Only the first path encountering the
> > conflict is reported
> > hyperprivop.S:2088: Warning: This is the location of the conflicting
> > usage hyperprivop.S:2108: Warning: Use of 'st8' violates RAW dependency
> > 'DTC' (data)
> > hyperprivop.S:2108: Warning: Only the first path encountering the
> > conflict is reported
> > hyperprivop.S:2087: Warning: This is the location of the conflicting
> > usage hyperprivop.S:2108: Warning: Use of 'st8' violates RAW dependency
> > 'DTC' (data)
> > hyperprivop.S:2108: Warning: Only the first path encountering the
> > conflict is reported
> > hyperprivop.S:2088: Warning: This is the location of the conflicting
> > usage hyperprivop.S :2109: Warning: Use of 'st8' violates RAW dependency
> > 'DTC' (data)
> > hyperprivop.S:2109: Warning: Only the first path encountering the
> > conflict is reported
> > hyperprivop.S:2087: Warning: This is the location of the conflicting
> > usage hyperprivop.S:2109: Warning: Use of 'st8' violates RAW dependency
> > 'DTC' (data)
> > hyperprivop.S:2109: Warning: Only the first path encountering the
> > conflict is reported
> > hyperprivop.S:2088: Warning: This is the location of the conflicting
> > usage hyperprivop.S:2112: Warning: Use of 'st8' violates RAW dependency
> > 'DTC' (data)
> > hyperprivop.S:2112: Warning: Only the first path encountering the
> > conflict is reported
> > hyperprivop.S:2087: Warning: This is the location of the conflicting
> > usage hyperprivop.S:2112: Warning: Use of 'st8' violates RAW dependency
> > 'DTC' (data)
> > hyperprivop.S:2112: Warning: Only the first path encountering the
> > conflict is reported
> > hyperprivop.S:2088: Warning: This is the location of the conflicting
> > usage hyperprivop.S :2116: Warning: Use of 'ld8' violates RAW dependency
> > 'DTC' (data)
> > hyperprivop.S:2116: Warning: Only the first path encountering the
> > conflict is reported
> > hyperprivop.S:2087: Warning: This is the location of the conflicting
> > usage hyperprivop.S:2116: Warning: Use of 'ld8' violates RAW dependency
> > 'DTC' (data)
> > hyperprivop.S:2116: Warning: Only the first path encountering the
> > conflict is reported
> > hyperprivop.S:2088: Warning: This is the location of the conflicting
> > usage hyperprivop.S:2119: Warning: Use of 'st8' violates RAW dependency
> > 'DTC' (data)
> > hyperprivop.S:2119: Warning: Only the first path encountering the
> > conflict is reported
> > hyperprivop.S:2087: Warning: This is the location of the conflicting
> > usage hyperprivop.S:2119: Warning: Use of 'st8' violates RAW dependency
> > 'DTC' (data)
> > hyperprivop.S:2119: Warning: Only the first path encountering the
> > conflict is reported
> > hyperprivop.S:2088: Warning: This is the location of the conflicting
> > usage hyperprivop.S :2135: Warning: Use of 'ld8' violates RAW dependency
> > 'DTC' (data)
> > hyperprivop.S:2135: Warning: Only the first path encountering the
> > conflict is reported
> > hyperprivop.S:2087: Warning: This is the location of the conflicting
> > usage hyperprivop.S:2135: Warning: Use of 'ld8' violates RAW dependency
> > 'DTC' (data)
> > hyperprivop.S:2135: Warning: Only the first path encountering the
> > conflict is reported
> > hyperprivop.S:2088: Warning: This is the location of the conflicting
> > usage hyperprivop.S:2137: Warning: Use of 'st8' violates RAW dependency
> > 'DTC' (data)
> > hyperprivop.S:2137: Warning: Only the first path encountering the
> > conflict is reported
> > hyperprivop.S:2087: Warning: This is the location of the conflicting
> > usage hyperprivop.S:2137: Warning: Use of 'st8' violates RAW dependency
> > 'DTC' (data)
> > hyperprivop.S:2137: Warning: Only the first path encountering the
> > conflict is reported
> > hyperprivop.S:2088: Warning: This is the location of the conflicting
> > usage hyperprivop.S :2138: Warning: Use of 'ld8' violates RAW dependency
> > 'DTC' (data)
> > hyperprivop.S:2138: Warning: Only the first path encountering the
> > conflict is reported
> > hyperprivop.S:2087: Warning: This is the location of the conflicting
> > usage hyperprivop.S:2138: Warning: Use of 'ld8' violates RAW dependency
> > 'DTC' (data)
> > hyperprivop.S:2138: Warning: Only the first path encountering the
> > conflict is reported
> > hyperprivop.S:2088: Warning: This is the location of the conflicting
> > usage hyperprivop.S:2145: Warning: Use of 'st8' violates RAW dependency
> > 'DTC' (data)
> > hyperprivop.S:2145: Warning: Only the first path encountering the
> > conflict is reported
> > hyperprivop.S:2087: Warning: This is the location of the conflicting
> > usage hyperprivop.S:2145: Warning: Use of 'st8' violates RAW dependency
> > 'DTC' (data)
> > hyperprivop.S:2145: Warning: Only the first path encountering the
> > conflict is reported
> > hyperprivop.S:2088: Warning: This is the location of the conflicting
> > usage hyperprivop.S :2149: Warning: Use of 'ld8' violates RAW dependency
> > 'DTC' (data)
> > hyperprivop.S:2149: Warning: Only the first path encountering the
> > conflict is reported
> > hyperprivop.S:2087: Warning: This is the location of the conflicting
> > usage hyperprivop.S:2149: Warning: Use of 'ld8' violates RAW dependency
> > 'DTC' (data)
> > hyperprivop.S:2149: Warning: Only the first path encountering the
> > conflict is reported
> > hyperprivop.S:2088: Warning: This is the location of the conflicting
> > usage hyperprivop.S:2153: Warning: Use of 'st8' violates RAW dependency
> > 'DTC' (data)
> > hyperprivop.S:2153: Warning: Only the first path encountering the
> > conflict is reported
> > hyperprivop.S:2087: Warning: This is the location of the conflicting
> > usage hyperprivop.S:2153: Warning: Use of 'st8' violates RAW dependency
> > 'DTC' (data)
> > hyperprivop.S:2153: Warning: Only the first path encountering the
> > conflict is reported
> > hyperprivop.S:2088: Warning: This is the location of the conflicting
> > usage make[5]: ** [ hyperprivop.o] Erro 1
> > make[5]: Saindo do diretório `/home/peso/xen-ia64-unstable.hg
> > /xen/arch/ia64/xen'
> > make[4]: ** [xen/built_in.o] Erro 2
> > make[4]: Saindo do diretório `/home/peso/xen- ia64-unstable.hg
> > /xen/arch/ia64'
> > make[3]: ** [/home/peso/xen-ia64-unstable.hg/xen/arch/ia64/built_in.o]
> > Erro 2
> > make[3]: Saindo do diretório `/home/peso/xen-ia64-unstable.hg
> > /xen/arch/ia64'
> > make[2]: ** [/home/peso/xen-ia64-unstable.hg/xen/xen] Erro 2
> > make[2]: Saindo do diretório `/home/peso/xen-ia64-unstable.hg/xen'
> > make[1]: ** [install] Erro 2
> > make[1]: Saindo do diretório `/home/peso/xen-ia64-unstable.hg/xen'
> > make: ** [install-xen] Erro 2
> >
> > Thanks!
> >
> > 2006/4/28, Yang, Fred < fred.yang@xxxxxxxxx>:
> > > Due to build steps changed since the message got posted, you also want
> > > to
> > >
> > >       ==> Add "make KERNELS="linux-2.6-xen0 linux-2.6-xenU"  " after
> > > "make world" in XenBuild.sh
> > >      ==> modify corresponding Xen0 and XenU build paths after the first
> > > Build
> > >
> > > By following Kanno's instruction below.
> > >
> > > -Fred
> > >
> > > >-----Original Message-----
> > > >From: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
> > > >[mailto:xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf
> > > >Of Masaki Kanno
> > > >Sent: Thursday, April 27, 2006 6:51 PM
> > > >To: Rodrigo Lord
> > > >Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> > > >Subject: Re: [Xen-ia64-devel] Installing XEN/ia64 on Debian
> > > >
> > > >Hi,
> > > >
> > > >This is a method in case of RHEL4, but please refer to it.
> > > >
> > > >http://lists.xensource.com/archives/html/xen-ia64-devel/2006-03
> > > >/msg00362.html
> > > >
> > > >Best regards,
> > > > Kan
> > > >
> > > >Rodrigo Lord wrote:
> > > >>Hello!
> > > >>
> > > >>I'm trying to install XEN/ia64 on my Debian!
> > > >>So, I'm using Mercurial and downloaded in the link below:
> > > >>
> > > >> http://xenbits.xensource.com/ext/xen-ia64-unstable.hg
> > > >>
> > > >>Now, should I install normally? (as a x86)
> > > >>Is it a patch? Or should I apply a patch?
> > > >>I would like some information to complete my installation on my
> > > >> Debian
> > > >>
> > > >>system!
> > > >>
> > > >>(Sorry for my bad english)
> > > >>
> > > >>Thanks!
> > > >>_____________________________________________________________________
> > > >>_
> > > >>
> > > >>_______________________________________________
> > > >>Xen-ia64-devel mailing list
> > > >>Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> > > >> http://lists.xensource.com/xen-ia64-devel
> > > >
> > > >_______________________________________________
> > > >Xen-ia64-devel mailing list
> > > > Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> > > > http://lists.xensource.com/xen-ia64-devel

_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel