All of lore.kernel.org
 help / color / mirror / Atom feed
* Trying to compile Xen 4 for a Debian package fail
@ 2010-04-16  6:09 Martinx - ジェームズ
  2010-04-16  6:33 ` Keir Fraser
  0 siblings, 1 reply; 5+ messages in thread
From: Martinx - ジェームズ @ 2010-04-16  6:09 UTC (permalink / raw)
  To: xen-devel


[-- Attachment #1.1: Type: text/plain, Size: 6457 bytes --]

Guys,

 I'm trying to compile the Xen 4.0.0 via debian/rules makefile but I got
this:

administrativo@sid01:~/xen/xen-4/xen-4.0.0$ *make -f debian/rules
build-tools*
.....
make -C lib all
make[7]: Entering directory
`/home/administrativo/xen/xen-4/xen-4.0.0/debian/build/build-tools/tools/blktap2/vhd/lib'
make[7]: Nothing to be done for `all'.
make[7]: Leaving directory
`/home/administrativo/xen/xen-4/xen-4.0.0/debian/build/build-tools/tools/blktap2/vhd/lib'
make[6]: Leaving directory
`/home/administrativo/xen/xen-4/xen-4.0.0/debian/build/build-tools/tools/blktap2/vhd'
gcc -O2 -fomit-frame-pointer -m32 -march=i686 -fno-strict-aliasing
-std=gnu99 -Wall -Wstrict-prototypes -Wno-unused-value
-Wdeclaration-after-statement  -D__XEN_TOOLS__ -MMD -MF .vhd-util.d
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE
-D_LARGEFILE64_SOURCE -mno-tls-direct-seg-refs -Werror -Wno-unused
-I../include -D_GNU_SOURCE -Wp,-MD,.vhd-util.d -o vhd-util
vhd-util.o           -L../../tools/libxc -lxenctrl    -L../../tools/libxc
-lxenctrl    -Llib -lvhd -luuid
*/usr/bin/ld: cannot find -lxenctrl*
*collect2: ld returned 1 exit status*
make[5]: *** [vhd-util] Error 1
make[5]: Leaving directory
`/home/administrativo/xen/xen-4/xen-4.0.0/debian/build/build-tools/tools/blktap2/vhd'
make[4]: *** [subdir-all-vhd] Error 2
make[4]: Leaving directory
`/home/administrativo/xen/xen-4/xen-4.0.0/debian/build/build-tools/tools/blktap2'
make[3]: *** [subdirs-all] Error 2
make[3]: Leaving directory
`/home/administrativo/xen/xen-4/xen-4.0.0/debian/build/build-tools/tools/blktap2'
make[2]: *** [subdir-all-blktap2] Error 2
make[2]: Leaving directory
`/home/administrativo/xen/xen-4/xen-4.0.0/debian/build/build-tools/tools'
make[1]: *** [subdirs-all] Error 2
make[1]: Leaving directory
`/home/administrativo/xen/xen-4/xen-4.0.0/debian/build/build-tools/tools'
make: *** [debian/stamps/build-tools] Error 2

 BUT, if I run:

administrativo@sid01:~/xen/xen-4/xen-4.0.0$ *make -C
debian/build/build-tools/tools/blktap2/vhd*
make: Entering directory
`/home/administrativo/xen/xen-4/xen-4.0.0/debian/build/build-tools/tools/blktap2/vhd'
make[1]: Entering directory
`/home/administrativo/xen/xen-4/xen-4.0.0/debian/build/build-tools/tools/blktap2/vhd'
make -C lib all
make[2]: Entering directory
`/home/administrativo/xen/xen-4/xen-4.0.0/debian/build/build-tools/tools/blktap2/vhd/lib'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory
`/home/administrativo/xen/xen-4/xen-4.0.0/debian/build/build-tools/tools/blktap2/vhd/lib'
make[1]: Leaving directory
`/home/administrativo/xen/xen-4/xen-4.0.0/debian/build/build-tools/tools/blktap2/vhd'
gcc -O2 -fomit-frame-pointer -m32 -march=i686 -fno-strict-aliasing
-std=gnu99 -Wall -Wstrict-prototypes -Wno-unused-value
-Wdeclaration-after-statement  -D__XEN_TOOLS__ -MMD -MF .vhd-util.d
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE
-D_LARGEFILE64_SOURCE -mno-tls-direct-seg-refs -Werror -Wno-unused
-I../include -D_GNU_SOURCE -Wp,-MD,.vhd-util.d -o vhd-util vhd-util.o
-Llib -lvhd -luuid
gcc -O2 -fomit-frame-pointer -m32 -march=i686 -fno-strict-aliasing
-std=gnu99 -Wall -Wstrict-prototypes -Wno-unused-value
-Wdeclaration-after-statement  -D__XEN_TOOLS__ -MMD -MF .vhd-update.d
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE
-D_LARGEFILE64_SOURCE -mno-tls-direct-seg-refs -Werror -Wno-unused
-I../include -D_GNU_SOURCE -Wp,-MD,.vhd-update.d -o vhd-update
vhd-update.o    -Llib -lvhd -luuid
make: Leaving directory
`/home/administrativo/xen/xen-4/xen-4.0.0/debian/build/build-tools/tools/blktap2/vhd'
administrativo@sid01:~/xen/xen-4/xen-4.0.0$

...it finishes without problems...

 I'm not a programmer so, I appreciate any help...

 The debian/rules file runs the same command, I guess, look:

-- some content of debian/rules:
$(STAMPS_DIR)/build-tools: $(STAMPS_DIR)/setup-tools
        $(MAKE) -C $(DIR)/tools
        touch $@

build-tools:: $(STAMPS_DIR)/build-tools
--

 Also, if I manually run "$(MAKE) -C $(DIR)/tools" from the same subdir as:
"make -C debian/build/build-tools/tools" it works too, look:

......
make[6]: Leaving directory
`/home/administrativo/xen/xen-4/xen-4.0.0/debian/build/build-tools/tools/blktap2/vhd/lib'
make[5]: Leaving directory
`/home/administrativo/xen/xen-4/xen-4.0.0/debian/build/build-tools/tools/blktap2/vhd'
gcc -O2 -fomit-frame-pointer -m32 -march=i686 -fno-strict-aliasing
-std=gnu99 -Wall -Wstrict-prototypes -Wno-unused-value
-Wdeclaration-after-statement  -D__XEN_TOOLS__ -MMD -MF .vhd-util.d
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE
-D_LARGEFILE64_SOURCE -mno-tls-direct-seg-refs -Werror -Wno-unused
-I../include -D_GNU_SOURCE -Wp,-MD,.vhd-util.d -o vhd-util vhd-util.o
-Llib -lvhd -luuid
gcc -O2 -fomit-frame-pointer -m32 -march=i686 -fno-strict-aliasing
-std=gnu99 -Wall -Wstrict-prototypes -Wno-unused-value
-Wdeclaration-after-statement  -D__XEN_TOOLS__ -MMD -MF .vhd-update.d
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE
-D_LARGEFILE64_SOURCE -mno-tls-direct-seg-refs -Werror -Wno-unused
-I../include -D_GNU_SOURCE -Wp,-MD,.vhd-update.d -o vhd-update
vhd-update.o    -Llib -lvhd -luuid
make[4]: Leaving directory
`/home/administrativo/xen/xen-4/xen-4.0.0/debian/build/build-tools/tools/blktap2/vhd'
make[3]: Leaving directory
`/home/administrativo/xen/xen-4/xen-4.0.0/debian/build/build-tools/tools/blktap2'
make[3]: Entering directory
`/home/administrativo/xen/xen-4/xen-4.0.0/debian/build/build-tools/tools/blktap2'
make -C drivers all
make[4]: Entering directory
`/home/administrativo/xen/xen-4/xen-4.0.0/debian/build/build-tools/tools/blktap2/drivers'
Makefile:35: === libgcrypt not installed: falling back to libcrypto ===
make[4]: Nothing to be done for `all'.
make[4]: Leaving directory
`/home/administrativo/xen/xen-4/xen-4.0.0/debian/build/build-tools/tools/blktap2/drivers'
make[3]: Leaving directory
`/home/administrativo/xen/xen-4/xen-4.0.0/debian/build/build-tools/tools/blktap2'
make[2]: Leaving directory
`/home/administrativo/xen/xen-4/xen-4.0.0/debian/build/build-tools/tools/blktap2'
make[1]: Leaving directory
`/home/administrativo/xen/xen-4/xen-4.0.0/debian/build/build-tools/tools'
make[1]: Entering directory
`/home/administrativo/xen/xen-4/xen-4.0.0/debian/build/build-tools/tools'
make -C libfsimage all
make[2]: Entering directory
`/home/administrativo/xen/xen-4/xen-4.0.0/debian/build/build-tools/tools/libfsimage'
......

 Thanks in advance!

Regards,
Thiago

[-- Attachment #1.2: Type: text/html, Size: 6964 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Trying to compile Xen 4 for a Debian package fail
  2010-04-16  6:09 Trying to compile Xen 4 for a Debian package fail Martinx - ジェームズ
@ 2010-04-16  6:33 ` Keir Fraser
  2010-04-16 16:31   ` Martinx - ジェームズ
  0 siblings, 1 reply; 5+ messages in thread
From: Keir Fraser @ 2010-04-16  6:33 UTC (permalink / raw)
  To: Martinx - ジェームズ, xen-devel

Could be a build ordering problem -- building blktap2 before the libxc
library that it depends on -- perhaps? Unless this reproducible on one of
our mainstream trees, this is an issue to report to the debian maintainer.

 -- Keir

On 16/04/2010 07:09, "Martinx - ジェームズ" <thiagocmartinsc@gmail.com>
wrote:

> make -C lib all
> make[7]: Entering directory
> `/home/administrativo/xen/xen-4/xen-4.0.0/debian/build/build-tools/tools/blkta
> p2/vhd/lib'
> make[7]: Nothing to be done for `all'.
> make[7]: Leaving directory
> `/home/administrativo/xen/xen-4/xen-4.0.0/debian/build/build-tools/tools/blkta
> p2/vhd/lib'
> make[6]: Leaving directory
> `/home/administrativo/xen/xen-4/xen-4.0.0/debian/build/build-tools/tools/blkta
> p2/vhd'
> gcc -O2 -fomit-frame-pointer -m32 -march=i686 -fno-strict-aliasing -std=gnu99
> -Wall -Wstrict-prototypes -Wno-unused-value -Wdeclaration-after-statement
> -D__XEN_TOOLS__ -MMD -MF .vhd-util.d -D_LARGEFILE_SOURCE
> -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE
> -mno-tls-direct-seg-refs -Werror -Wno-unused -I../include -D_GNU_SOURCE
> -Wp,-MD,.vhd-util.d -o vhd-util vhd-util.o           -L../../tools/libxc
> -lxenctrl    -L../../tools/libxc -lxenctrl    -Llib -lvhd -luuid
> /usr/bin/ld: cannot find -lxenctrl
> collect2: ld returned 1 exit status

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Trying to compile Xen 4 for a Debian package fail
  2010-04-16  6:33 ` Keir Fraser
@ 2010-04-16 16:31   ` Martinx - ジェームズ
  2010-04-16 17:47     ` Keir Fraser
  0 siblings, 1 reply; 5+ messages in thread
From: Martinx - ジェームズ @ 2010-04-16 16:31 UTC (permalink / raw)
  To: Keir Fraser; +Cc: xen-devel


[-- Attachment #1.1: Type: text/plain, Size: 1614 bytes --]

Well, thank you anyway Keir... But I'm the maintainer of this unofficial
package... I
just trying to do a new package based on my experiences with the Xen...

Regards,
Thiago

2010/4/16 Keir Fraser <keir.fraser@eu.citrix.com>

> Could be a build ordering problem -- building blktap2 before the libxc
> library that it depends on -- perhaps? Unless this reproducible on one of
> our mainstream trees, this is an issue to report to the debian maintainer.
>
>  -- Keir
>
> On 16/04/2010 07:09, "Martinx - ジェームズ" <thiagocmartinsc@gmail.com>
> wrote:
>
> > make -C lib all
> > make[7]: Entering directory
> >
> `/home/administrativo/xen/xen-4/xen-4.0.0/debian/build/build-tools/tools/blkta
> > p2/vhd/lib'
> > make[7]: Nothing to be done for `all'.
> > make[7]: Leaving directory
> >
> `/home/administrativo/xen/xen-4/xen-4.0.0/debian/build/build-tools/tools/blkta
> > p2/vhd/lib'
> > make[6]: Leaving directory
> >
> `/home/administrativo/xen/xen-4/xen-4.0.0/debian/build/build-tools/tools/blkta
> > p2/vhd'
> > gcc -O2 -fomit-frame-pointer -m32 -march=i686 -fno-strict-aliasing
> -std=gnu99
> > -Wall -Wstrict-prototypes -Wno-unused-value -Wdeclaration-after-statement
> > -D__XEN_TOOLS__ -MMD -MF .vhd-util.d -D_LARGEFILE_SOURCE
> > -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE
> > -mno-tls-direct-seg-refs -Werror -Wno-unused -I../include -D_GNU_SOURCE
> > -Wp,-MD,.vhd-util.d -o vhd-util vhd-util.o           -L../../tools/libxc
> > -lxenctrl    -L../../tools/libxc -lxenctrl    -Llib -lvhd -luuid
> > /usr/bin/ld: cannot find -lxenctrl
> > collect2: ld returned 1 exit status
>
>
>

[-- Attachment #1.2: Type: text/html, Size: 2217 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Trying to compile Xen 4 for a Debian package fail
  2010-04-16 16:31   ` Martinx - ジェームズ
@ 2010-04-16 17:47     ` Keir Fraser
  2010-04-16 18:23       ` Martinx - ジェームズ
  0 siblings, 1 reply; 5+ messages in thread
From: Keir Fraser @ 2010-04-16 17:47 UTC (permalink / raw)
  To: Martinx - ジェームズ; +Cc: xen-devel

Okay, well then I can tell you that it is almost certainly a build-ordering
problem. Do your packages have patches on top of our build system? Because
we do parallel builds all the time and we would generally know pretty
quickly if our build dependencies and orderings are wrong.

 -- Keir

On 16/04/2010 17:31, "Martinx - ジェームズ" <thiagocmartinsc@gmail.com>
wrote:

> Well, thank you anyway Keir... But I'm the maintainer of this unofficial
> package... I  
> just trying to do a new package based on my experiences with the Xen...
> 
> Regards,
> Thiago
> 
> 2010/4/16 Keir Fraser <keir.fraser@eu.citrix.com>
>> Could be a build ordering problem -- building blktap2 before the libxc
>> library that it depends on -- perhaps? Unless this reproducible on one of
>> our mainstream trees, this is an issue to report to the debian maintainer.
>> 
>>  -- Keir
>> 
>> On 16/04/2010 07:09, "Martinx - ジェームズ" <thiagocmartinsc@gmail.com>
>> wrote:
>> 
>>> make -C lib all
>>> make[7]: Entering directory
>>> `/home/administrativo/xen/xen-4/xen-4.0.0/debian/build/build-tools/tools/blk
>>> ta
>>> p2/vhd/lib'
>>> make[7]: Nothing to be done for `all'.
>>> make[7]: Leaving directory
>>> `/home/administrativo/xen/xen-4/xen-4.0.0/debian/build/build-tools/tools/blk
>>> ta
>>> p2/vhd/lib'
>>> make[6]: Leaving directory
>>> `/home/administrativo/xen/xen-4/xen-4.0.0/debian/build/build-tools/tools/blk
>>> ta
>>> p2/vhd'
>>> gcc -O2 -fomit-frame-pointer -m32 -march=i686 -fno-strict-aliasing
>>> -std=gnu99
>>> -Wall -Wstrict-prototypes -Wno-unused-value -Wdeclaration-after-statement
>>> -D__XEN_TOOLS__ -MMD -MF .vhd-util.d -D_LARGEFILE_SOURCE
>>> -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE
>>> -mno-tls-direct-seg-refs -Werror -Wno-unused -I../include -D_GNU_SOURCE
>>> -Wp,-MD,.vhd-util.d -o vhd-util vhd-util.o           -L../../tools/libxc
>>> -lxenctrl    -L../../tools/libxc -lxenctrl    -Llib -lvhd -luuid
>>> /usr/bin/ld: cannot find -lxenctrl
>>> collect2: ld returned 1 exit status
>> 
>> 
> 
> 

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Trying to compile Xen 4 for a Debian package fail
  2010-04-16 17:47     ` Keir Fraser
@ 2010-04-16 18:23       ` Martinx - ジェームズ
  0 siblings, 0 replies; 5+ messages in thread
From: Martinx - ジェームズ @ 2010-04-16 18:23 UTC (permalink / raw)
  To: Keir Fraser; +Cc: xen-devel


[-- Attachment #1.1.1: Type: text/plain, Size: 2462 bytes --]

Thank you again Keir!  [?]

I have not applied any patch to the original Xen, I'm just trying to
pack/compile the original xen-4.0.0.tar.gz (hypervisor, tools and docs)
using the debian/rules makefile file.
I will investigate more deeply the order.

Cheers,
Thiago

2010/4/16 Keir Fraser <keir.fraser@eu.citrix.com>

> Okay, well then I can tell you that it is almost certainly a build-ordering
> problem. Do your packages have patches on top of our build system? Because
> we do parallel builds all the time and we would generally know pretty
> quickly if our build dependencies and orderings are wrong.
>
>  -- Keir
>
> On 16/04/2010 17:31, "Martinx - ジェームズ" <thiagocmartinsc@gmail.com>
> wrote:
>
> > Well, thank you anyway Keir... But I'm the maintainer of this unofficial
> > package... I
> > just trying to do a new package based on my experiences with the Xen...
> >
> > Regards,
> > Thiago
> >
> > 2010/4/16 Keir Fraser <keir.fraser@eu.citrix.com>
> >> Could be a build ordering problem -- building blktap2 before the libxc
> >> library that it depends on -- perhaps? Unless this reproducible on one
> of
> >> our mainstream trees, this is an issue to report to the debian
> maintainer.
> >>
> >>  -- Keir
> >>
> >> On 16/04/2010 07:09, "Martinx - ジェームズ" <thiagocmartinsc@gmail.com>
> >> wrote:
> >>
> >>> make -C lib all
> >>> make[7]: Entering directory
> >>>
> `/home/administrativo/xen/xen-4/xen-4.0.0/debian/build/build-tools/tools/blk
> >>> ta
> >>> p2/vhd/lib'
> >>> make[7]: Nothing to be done for `all'.
> >>> make[7]: Leaving directory
> >>>
> `/home/administrativo/xen/xen-4/xen-4.0.0/debian/build/build-tools/tools/blk
> >>> ta
> >>> p2/vhd/lib'
> >>> make[6]: Leaving directory
> >>>
> `/home/administrativo/xen/xen-4/xen-4.0.0/debian/build/build-tools/tools/blk
> >>> ta
> >>> p2/vhd'
> >>> gcc -O2 -fomit-frame-pointer -m32 -march=i686 -fno-strict-aliasing
> >>> -std=gnu99
> >>> -Wall -Wstrict-prototypes -Wno-unused-value
> -Wdeclaration-after-statement
> >>> -D__XEN_TOOLS__ -MMD -MF .vhd-util.d -D_LARGEFILE_SOURCE
> >>> -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE
> >>> -mno-tls-direct-seg-refs -Werror -Wno-unused -I../include -D_GNU_SOURCE
> >>> -Wp,-MD,.vhd-util.d -o vhd-util vhd-util.o
> -L../../tools/libxc
> >>> -lxenctrl    -L../../tools/libxc -lxenctrl    -Llib -lvhd -luuid
> >>> /usr/bin/ld: cannot find -lxenctrl
> >>> collect2: ld returned 1 exit status
> >>
> >>
> >
> >
>
>
>

[-- Attachment #1.1.2: Type: text/html, Size: 3675 bytes --]

[-- Attachment #1.2: 360.gif --]
[-- Type: image/gif, Size: 453 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2010-04-16 18:23 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-04-16  6:09 Trying to compile Xen 4 for a Debian package fail Martinx - ジェームズ
2010-04-16  6:33 ` Keir Fraser
2010-04-16 16:31   ` Martinx - ジェームズ
2010-04-16 17:47     ` Keir Fraser
2010-04-16 18:23       ` Martinx - ジェームズ

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.