compilation fail, xen staging-4.6, vnc.c, qemu-tradintional issues under ubuntu 16.04

compilation fail, xen staging-4.6, vnc.c, qemu-tradintional issues under ubuntu 16.04

[Éliás Tamás]

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

Hi.

Previously I was using debian 8 to compile my xen 4.6 with hvm
stubdomain support. We recently switched to ubuntu servers, thus I
needed to change my compilation environment not to have lib dependency
issues.

My problem is: I get the staging 4.6 xen
(http://xenbits.xen.org/gitweb/?p=xen.git;a=snapshot;h=8e89d43867922abaa67e894938c655a6fa82affe;sf=tgz),
installed all required prereqs for my compilaton environment, but during
compilation I get errors (I do not get them using debian 8). I'm sure
that all prereq is met, becasuse ./configure runs correctly, I'm using
--enable-systemd --enable-stubdom )

Most of the problems could be solved by dirty hacks for myself, but I
belive they require some attention of qemu/xen developers to make
compilation work under ubuntu 16.04 out of the box:

The first issue

/usr/src/xen-staging-4.6/tools/qemu-xen-traditional-dir/vnc.c:2180:
undefined reference to `gnutls_kx_set_priority'

could be solved by applying these patches over the auto downloaded qemu
sources:

https://gitlab.com/johnth/aur-xen/raw/f9d0b40e240add9a136483a450c6a1b39a685808/qemu-xen-traditional-gnutls-compilation.patch

https://gitlab.com/johnth/aur-xen/raw/f9d0b40e240add9a136483a450c6a1b39a685808/qemu-xen-traditional-gnutls-functions.patch

after that I got

vl.c:2784:5: error: ‘g_mem_set_vtable’ is deprecated
[-Werror=deprecated-declarations]
     g_mem_set_vtable(&mem_trace);


I had to apply

https://lists.gnu.org/archive/html/qemu-devel/2015-09/msg01262.html

which seemes that only partially been applied (has rejects), but after
modifying the sources by hand, it seemes working.

Just after this, Mini-OS failed to compile:

Makefile:17: /config/MiniOS.mk: No such file or directory

But, the MiniOS.mk DOES exists.

I had to manually add

XEN_ROOT=mysourcedir

to mini-os/Config.mk to continue. and now I'm stuck here:

gcc -mno-red-zone -O1 -fno-omit-frame-pointer  -m64 -mno-red-zone
-fno-reorder-blocks -fno-asynchronous-unwind-tables -m64 -g
-fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes
-Wdeclaration-after-statement -Wno-unused-but-set-variable
-Wno-unused-local-typedefs   -fno-stack-protector -fno-exceptions
-DCONFIG_BLKFRONT -DCONFIG_TPMFRONT -DCONFIG_NETFRONT -DCONFIG_KBDFRONT
-DCONFIG_FBFRONT -DCONFIG_CONSFRONT -DCONFIG_XENBUS -fno-builtin -Wall
-Werror -Wredundant-decls -Wno-format -Wno-redundant-decls -Wformat
-fno-stack-protector -fgnu89-inline -Wstrict-prototypes -Wnested-externs
-Wpointer-arith -Winline -g -D__INSIDE_MINIOS__ -m64 -mno-red-zone
-fno-reorder-blocks -fno-asynchronous-unwind-tables -isystem
/usr/src/xen-staging-4.6/extras/mini-os/include -D__MINIOS__ -DHAVE_LIBC
-isystem /usr/src/xen-staging-4.6/extras/mini-os/include/posix -isystem
/usr/src/xen-staging-4.6/tools/xenstore/include  -isystem
/usr/src/xen-staging-4.6/extras/mini-os/include/x86 -isystem
/usr/src/xen-staging-4.6/extras/mini-os/include/x86/x86_64 -U __linux__
-U __FreeBSD__ -U __sun__ -nostdinc -isystem
/usr/src/xen-staging-4.6/extras/mini-os/include/posix -isystem
/usr/src/xen-staging-4.6/stubdom/cross-root-x86_64/x86_64-xen-elf/include -isystem
/usr/lib/gcc/x86_64-linux-gnu/5/include -isystem
/usr/src/xen-staging-4.6/stubdom/lwip-x86_64/src/include -isystem
/usr/src/xen-staging-4.6/stubdom/lwip-x86_64/src/include/ipv4
-I/usr/src/xen-staging-4.6/stubdom/include
-I/usr/src/xen-staging-4.6/xen/include -isystem
/usr/src/xen-staging-4.6/extras/mini-os/include -D__MINIOS__ -DHAVE_LIBC
-isystem /usr/src/xen-staging-4.6/extras/mini-os/include/posix -isystem
/usr/src/xen-staging-4.6/tools/xenstore/include
-D__XEN_INTERFACE_VERSION__=0x00030205  -isystem
/usr/src/xen-staging-4.6/extras/mini-os/include/x86 -isystem
/usr/src/xen-staging-4.6/extras/mini-os/include/x86/x86_64 -c
console/xenbus.c -o
/usr/src/xen-staging-4.6/stubdom/mini-os-x86_64-grub/console/xenbus.o
ld -r -d -nostdlib
-L/usr/src/xen-staging-4.6/stubdom/cross-root-x86_64/x86_64-xen-elf/lib
 -m elf_x86_64 -\( /usr/src/xen-staging-4.6/stubdom/grub-x86_64/main.a
app.lds -\)  -L/usr/src/xen-staging-4.6/stubdom/libs-x86_64/toollog
-whole-archive -lxentoollog -no-whole-archive
-L/usr/src/xen-staging-4.6/stubdom/libs-x86_64/evtchn -whole-archive
-lxenevtchn -no-whole-archive
-L/usr/src/xen-staging-4.6/stubdom/libs-x86_64/gnttab -whole-archive
-lxengnttab -no-whole-archive
-L/usr/src/xen-staging-4.6/stubdom/libs-x86_64/call -whole-archive
-lxencall -no-whole-archive
-L/usr/src/xen-staging-4.6/stubdom/libs-x86_64/foreignmemory
-whole-archive -lxenforeignmemory -no-whole-archive
-L/usr/src/xen-staging-4.6/stubdom/libxc-x86_64 -whole-archive
-lxenguest -lxenctrl -no-whole-archive -lpci -lz -lm --undefined main -o
/usr/src/xen-staging-4.6/stubdom/mini-os-x86_64-grub/mini-os_app.o
ld: warning: app.lds contains output sections; did you forget -T?
ld: cannot find -lxentoollog
ld: cannot find -lxenevtchn
ld: cannot find -lxengnttab
ld: cannot find -lxencall
ld: cannot find -lxenforeignmemory
Makefile:186: recipe for target
'/usr/src/xen-staging-4.6/stubdom/mini-os-x86_64-grub/mini-os_app.o' failed
make[2]: ***
[/usr/src/xen-staging-4.6/stubdom/mini-os-x86_64-grub/mini-os_app.o] Error 1
make[2]: Leaving directory '/usr/src/xen-staging-4.6/extras/mini-os-remote'
Makefile:455: recipe for target 'pv-grub' failed
make[1]: *** [pv-grub] Error 2
make[1]: Leaving directory '/usr/src/xen-staging-4.6/stubdom'
Makefile:106: recipe for target 'install-stubdom' failed
make: *** [install-stubdom] Error 2

Can someone advise?

So I belive, that these important patches / fixes are missing from xen
version of qemu (at least prevents compiling it without hacks on newer
systems) and also the mini-os port needs some polishing. Maybe ubuntu
has newer build tools which ones causing some incompatibilities, I do
not know.

Is it possible fixing any of these problems?


-- 


Éliás Tamás
Thomas Elias

ETIT[nwpro] KFT, Ügyvezető-Hálózatbiztonsági specialista
ETIT[nwpro] Ltd, General Manager-Network security specialist

Tel. HU: +36/30-497-1626
Tel. DE: +49/160-651-8723
OpenPGP pubkey: http://etit.hu/doc/et-pub.asc

Okleveles mérnök-informatikus (MSC)
Master of Science in Information Technology (MSC)

Kapcsolat: http://etit.hu/index.php/hu/kapcsolat
Jogi nyilatkozat: http://etit.hu/disclaimer-email-hu.txt
Contact: http://etit.hu/index.php/en/contact
Disclaimer: http://etit.hu/disclaimer-email-en.txt


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

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

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

Re: compilation fail, xen staging-4.6, vnc.c, qemu-tradintional issues under ubuntu 16.04

[Dario Faggioli]

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

Cc-ing some tools, Qemu, and Stubdom/MiniOS people, and dropping xen-
users (Bcc-ed)...

On Fri, 2016-03-25 at 18:53 +0100, Éliás Tamás wrote:
> Hi.
> 
> Previously I was using debian 8 to compile my xen 4.6 with hvm
> stubdomain support. We recently switched to ubuntu servers, thus I
> needed to change my compilation environment not to have lib
> dependency
> issues.
> 
> My problem is: I get the staging 4.6 xen
> (http://xenbits.xen.org/gitweb/?p=xen.git;a=snapshot;h=8e89d43867922a
> baa67e894938c655a6fa82affe;sf=tgz),
> installed all required prereqs for my compilaton environment, but
> during
> compilation I get errors (I do not get them using debian 8). I'm sure
> that all prereq is met, becasuse ./configure runs correctly, I'm
> using
> --enable-systemd --enable-stubdom )
> 
> Most of the problems could be solved by dirty hacks for myself, but I
> belive they require some attention of qemu/xen developers to make
> compilation work under ubuntu 16.04 out of the box:
> 
> The first issue
> 
> /usr/src/xen-staging-4.6/tools/qemu-xen-traditional-dir/vnc.c:2180:
> undefined reference to `gnutls_kx_set_priority'
> 
> could be solved by applying these patches over the auto downloaded
> qemu
> sources:
> 
> https://gitlab.com/johnth/aur-xen/raw/f9d0b40e240add9a136483a450c6a1b
> 39a685808/qemu-xen-traditional-gnutls-compilation.patch
> 
> https://gitlab.com/johnth/aur-xen/raw/f9d0b40e240add9a136483a450c6a1b
> 39a685808/qemu-xen-traditional-gnutls-functions.patch
> 
> after that I got
> 
> vl.c:2784:5: error: ‘g_mem_set_vtable’ is deprecated
> [-Werror=deprecated-declarations]
>      g_mem_set_vtable(&mem_trace);
> 
> 
> I had to apply
> 
> https://lists.gnu.org/archive/html/qemu-devel/2015-09/msg01262.html
> 
> which seemes that only partially been applied (has rejects), but
> after
> modifying the sources by hand, it seemes working.
> 
> Just after this, Mini-OS failed to compile:
> 
> Makefile:17: /config/MiniOS.mk: No such file or directory
> 
> But, the MiniOS.mk DOES exists.
> 
> I had to manually add
> 
> XEN_ROOT=mysourcedir
> 
> to mini-os/Config.mk to continue. and now I'm stuck here:
> 
> gcc -mno-red-zone -O1 -fno-omit-frame-pointer  -m64 -mno-red-zone
> -fno-reorder-blocks -fno-asynchronous-unwind-tables -m64 -g
> -fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes
> -Wdeclaration-after-statement -Wno-unused-but-set-variable
> -Wno-unused-local-typedefs   -fno-stack-protector -fno-exceptions
> -DCONFIG_BLKFRONT -DCONFIG_TPMFRONT -DCONFIG_NETFRONT
> -DCONFIG_KBDFRONT
> -DCONFIG_FBFRONT -DCONFIG_CONSFRONT -DCONFIG_XENBUS -fno-builtin
> -Wall
> -Werror -Wredundant-decls -Wno-format -Wno-redundant-decls -Wformat
> -fno-stack-protector -fgnu89-inline -Wstrict-prototypes -Wnested-
> externs
> -Wpointer-arith -Winline -g -D__INSIDE_MINIOS__ -m64 -mno-red-zone
> -fno-reorder-blocks -fno-asynchronous-unwind-tables -isystem
> /usr/src/xen-staging-4.6/extras/mini-os/include -D__MINIOS__
> -DHAVE_LIBC
> -isystem /usr/src/xen-staging-4.6/extras/mini-os/include/posix
> -isystem
> /usr/src/xen-staging-4.6/tools/xenstore/include  -isystem
> /usr/src/xen-staging-4.6/extras/mini-os/include/x86 -isystem
> /usr/src/xen-staging-4.6/extras/mini-os/include/x86/x86_64 -U
> __linux__
> -U __FreeBSD__ -U __sun__ -nostdinc -isystem
> /usr/src/xen-staging-4.6/extras/mini-os/include/posix -isystem
> /usr/src/xen-staging-4.6/stubdom/cross-root-x86_64/x86_64-xen-
> elf/include -isystem
> /usr/lib/gcc/x86_64-linux-gnu/5/include -isystem
> /usr/src/xen-staging-4.6/stubdom/lwip-x86_64/src/include -isystem
> /usr/src/xen-staging-4.6/stubdom/lwip-x86_64/src/include/ipv4
> -I/usr/src/xen-staging-4.6/stubdom/include
> -I/usr/src/xen-staging-4.6/xen/include -isystem
> /usr/src/xen-staging-4.6/extras/mini-os/include -D__MINIOS__
> -DHAVE_LIBC
> -isystem /usr/src/xen-staging-4.6/extras/mini-os/include/posix
> -isystem
> /usr/src/xen-staging-4.6/tools/xenstore/include
> -D__XEN_INTERFACE_VERSION__=0x00030205  -isystem
> /usr/src/xen-staging-4.6/extras/mini-os/include/x86 -isystem
> /usr/src/xen-staging-4.6/extras/mini-os/include/x86/x86_64 -c
> console/xenbus.c -o
> /usr/src/xen-staging-4.6/stubdom/mini-os-x86_64-grub/console/xenbus.o
> ld -r -d -nostdlib
> -L/usr/src/xen-staging-4.6/stubdom/cross-root-x86_64/x86_64-xen-
> elf/lib
>  -m elf_x86_64 -\( /usr/src/xen-staging-4.6/stubdom/grub-
> x86_64/main.a
> app.lds -\)  -L/usr/src/xen-staging-4.6/stubdom/libs-x86_64/toollog
> -whole-archive -lxentoollog -no-whole-archive
> -L/usr/src/xen-staging-4.6/stubdom/libs-x86_64/evtchn -whole-archive
> -lxenevtchn -no-whole-archive
> -L/usr/src/xen-staging-4.6/stubdom/libs-x86_64/gnttab -whole-archive
> -lxengnttab -no-whole-archive
> -L/usr/src/xen-staging-4.6/stubdom/libs-x86_64/call -whole-archive
> -lxencall -no-whole-archive
> -L/usr/src/xen-staging-4.6/stubdom/libs-x86_64/foreignmemory
> -whole-archive -lxenforeignmemory -no-whole-archive
> -L/usr/src/xen-staging-4.6/stubdom/libxc-x86_64 -whole-archive
> -lxenguest -lxenctrl -no-whole-archive -lpci -lz -lm --undefined main
> -o
> /usr/src/xen-staging-4.6/stubdom/mini-os-x86_64-grub/mini-os_app.o
> ld: warning: app.lds contains output sections; did you forget -T?
> ld: cannot find -lxentoollog
> ld: cannot find -lxenevtchn
> ld: cannot find -lxengnttab
> ld: cannot find -lxencall
> ld: cannot find -lxenforeignmemory
> Makefile:186: recipe for target
> '/usr/src/xen-staging-4.6/stubdom/mini-os-x86_64-grub/mini-os_app.o'
> failed
> make[2]: ***
> [/usr/src/xen-staging-4.6/stubdom/mini-os-x86_64-grub/mini-os_app.o]
> Error 1
> make[2]: Leaving directory '/usr/src/xen-staging-4.6/extras/mini-os-
> remote'
> Makefile:455: recipe for target 'pv-grub' failed
> make[1]: *** [pv-grub] Error 2
> make[1]: Leaving directory '/usr/src/xen-staging-4.6/stubdom'
> Makefile:106: recipe for target 'install-stubdom' failed
> make: *** [install-stubdom] Error 2
> 
> Can someone advise?
> 
> So I belive, that these important patches / fixes are missing from
> xen
> version of qemu (at least prevents compiling it without hacks on
> newer
> systems) and also the mini-os port needs some polishing. Maybe ubuntu
> has newer build tools which ones causing some incompatibilities, I do
> not know.
> 
> Is it possible fixing any of these problems?
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
-- 
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)


[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

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

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

Re: [Xen-users] compilation fail, xen staging-4.6, vnc.c, qemu-tradintional issues under ubuntu 16.04

[Éliás Tamás]

[-- Attachment #1.1.1.1: Type: text/plain, Size: 7757 bytes --]

Guys.

Let me share the information I got a day ago from Pry Mar
<pryorm09@gmail.com> (attachement). He did marvellous work on xen 4.6.1+
on ubuntu 16.04.

Pls check his work, there are lot of issues there, and finally I have a
working HVM STUBDOMAIN thx to him!

2016-03-30 16:58 keltezéssel, Dario Faggioli írta:
> Cc-ing some tools, Qemu, and Stubdom/MiniOS people, and dropping xen-
> users (Bcc-ed)...
> 
> On Fri, 2016-03-25 at 18:53 +0100, Éliás Tamás wrote:
>> Hi.
>>
>> Previously I was using debian 8 to compile my xen 4.6 with hvm
>> stubdomain support. We recently switched to ubuntu servers, thus I
>> needed to change my compilation environment not to have lib
>> dependency
>> issues.
>>
>> My problem is: I get the staging 4.6 xen
>> (http://xenbits.xen.org/gitweb/?p=xen.git;a=snapshot;h=8e89d43867922a
>> baa67e894938c655a6fa82affe;sf=tgz),
>> installed all required prereqs for my compilaton environment, but
>> during
>> compilation I get errors (I do not get them using debian 8). I'm sure
>> that all prereq is met, becasuse ./configure runs correctly, I'm
>> using
>> --enable-systemd --enable-stubdom )
>>
>> Most of the problems could be solved by dirty hacks for myself, but I
>> belive they require some attention of qemu/xen developers to make
>> compilation work under ubuntu 16.04 out of the box:
>>
>> The first issue
>>
>> /usr/src/xen-staging-4.6/tools/qemu-xen-traditional-dir/vnc.c:2180:
>> undefined reference to `gnutls_kx_set_priority'
>>
>> could be solved by applying these patches over the auto downloaded
>> qemu
>> sources:
>>
>> https://gitlab.com/johnth/aur-xen/raw/f9d0b40e240add9a136483a450c6a1b
>> 39a685808/qemu-xen-traditional-gnutls-compilation.patch
>>
>> https://gitlab.com/johnth/aur-xen/raw/f9d0b40e240add9a136483a450c6a1b
>> 39a685808/qemu-xen-traditional-gnutls-functions.patch
>>
>> after that I got
>>
>> vl.c:2784:5: error: ‘g_mem_set_vtable’ is deprecated
>> [-Werror=deprecated-declarations]
>>      g_mem_set_vtable(&mem_trace);
>>
>>
>> I had to apply
>>
>> https://lists.gnu.org/archive/html/qemu-devel/2015-09/msg01262.html
>>
>> which seemes that only partially been applied (has rejects), but
>> after
>> modifying the sources by hand, it seemes working.
>>
>> Just after this, Mini-OS failed to compile:
>>
>> Makefile:17: /config/MiniOS.mk: No such file or directory
>>
>> But, the MiniOS.mk DOES exists.
>>
>> I had to manually add
>>
>> XEN_ROOT=mysourcedir
>>
>> to mini-os/Config.mk to continue. and now I'm stuck here:
>>
>> gcc -mno-red-zone -O1 -fno-omit-frame-pointer  -m64 -mno-red-zone
>> -fno-reorder-blocks -fno-asynchronous-unwind-tables -m64 -g
>> -fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes
>> -Wdeclaration-after-statement -Wno-unused-but-set-variable
>> -Wno-unused-local-typedefs   -fno-stack-protector -fno-exceptions
>> -DCONFIG_BLKFRONT -DCONFIG_TPMFRONT -DCONFIG_NETFRONT
>> -DCONFIG_KBDFRONT
>> -DCONFIG_FBFRONT -DCONFIG_CONSFRONT -DCONFIG_XENBUS -fno-builtin
>> -Wall
>> -Werror -Wredundant-decls -Wno-format -Wno-redundant-decls -Wformat
>> -fno-stack-protector -fgnu89-inline -Wstrict-prototypes -Wnested-
>> externs
>> -Wpointer-arith -Winline -g -D__INSIDE_MINIOS__ -m64 -mno-red-zone
>> -fno-reorder-blocks -fno-asynchronous-unwind-tables -isystem
>> /usr/src/xen-staging-4.6/extras/mini-os/include -D__MINIOS__
>> -DHAVE_LIBC
>> -isystem /usr/src/xen-staging-4.6/extras/mini-os/include/posix
>> -isystem
>> /usr/src/xen-staging-4.6/tools/xenstore/include  -isystem
>> /usr/src/xen-staging-4.6/extras/mini-os/include/x86 -isystem
>> /usr/src/xen-staging-4.6/extras/mini-os/include/x86/x86_64 -U
>> __linux__
>> -U __FreeBSD__ -U __sun__ -nostdinc -isystem
>> /usr/src/xen-staging-4.6/extras/mini-os/include/posix -isystem
>> /usr/src/xen-staging-4.6/stubdom/cross-root-x86_64/x86_64-xen-
>> elf/include -isystem
>> /usr/lib/gcc/x86_64-linux-gnu/5/include -isystem
>> /usr/src/xen-staging-4.6/stubdom/lwip-x86_64/src/include -isystem
>> /usr/src/xen-staging-4.6/stubdom/lwip-x86_64/src/include/ipv4
>> -I/usr/src/xen-staging-4.6/stubdom/include
>> -I/usr/src/xen-staging-4.6/xen/include -isystem
>> /usr/src/xen-staging-4.6/extras/mini-os/include -D__MINIOS__
>> -DHAVE_LIBC
>> -isystem /usr/src/xen-staging-4.6/extras/mini-os/include/posix
>> -isystem
>> /usr/src/xen-staging-4.6/tools/xenstore/include
>> -D__XEN_INTERFACE_VERSION__=0x00030205  -isystem
>> /usr/src/xen-staging-4.6/extras/mini-os/include/x86 -isystem
>> /usr/src/xen-staging-4.6/extras/mini-os/include/x86/x86_64 -c
>> console/xenbus.c -o
>> /usr/src/xen-staging-4.6/stubdom/mini-os-x86_64-grub/console/xenbus.o
>> ld -r -d -nostdlib
>> -L/usr/src/xen-staging-4.6/stubdom/cross-root-x86_64/x86_64-xen-
>> elf/lib
>>  -m elf_x86_64 -\( /usr/src/xen-staging-4.6/stubdom/grub-
>> x86_64/main.a
>> app.lds -\)  -L/usr/src/xen-staging-4.6/stubdom/libs-x86_64/toollog
>> -whole-archive -lxentoollog -no-whole-archive
>> -L/usr/src/xen-staging-4.6/stubdom/libs-x86_64/evtchn -whole-archive
>> -lxenevtchn -no-whole-archive
>> -L/usr/src/xen-staging-4.6/stubdom/libs-x86_64/gnttab -whole-archive
>> -lxengnttab -no-whole-archive
>> -L/usr/src/xen-staging-4.6/stubdom/libs-x86_64/call -whole-archive
>> -lxencall -no-whole-archive
>> -L/usr/src/xen-staging-4.6/stubdom/libs-x86_64/foreignmemory
>> -whole-archive -lxenforeignmemory -no-whole-archive
>> -L/usr/src/xen-staging-4.6/stubdom/libxc-x86_64 -whole-archive
>> -lxenguest -lxenctrl -no-whole-archive -lpci -lz -lm --undefined main
>> -o
>> /usr/src/xen-staging-4.6/stubdom/mini-os-x86_64-grub/mini-os_app.o
>> ld: warning: app.lds contains output sections; did you forget -T?
>> ld: cannot find -lxentoollog
>> ld: cannot find -lxenevtchn
>> ld: cannot find -lxengnttab
>> ld: cannot find -lxencall
>> ld: cannot find -lxenforeignmemory
>> Makefile:186: recipe for target
>> '/usr/src/xen-staging-4.6/stubdom/mini-os-x86_64-grub/mini-os_app.o'
>> failed
>> make[2]: ***
>> [/usr/src/xen-staging-4.6/stubdom/mini-os-x86_64-grub/mini-os_app.o]
>> Error 1
>> make[2]: Leaving directory '/usr/src/xen-staging-4.6/extras/mini-os-
>> remote'
>> Makefile:455: recipe for target 'pv-grub' failed
>> make[1]: *** [pv-grub] Error 2
>> make[1]: Leaving directory '/usr/src/xen-staging-4.6/stubdom'
>> Makefile:106: recipe for target 'install-stubdom' failed
>> make: *** [install-stubdom] Error 2
>>
>> Can someone advise?
>>
>> So I belive, that these important patches / fixes are missing from
>> xen
>> version of qemu (at least prevents compiling it without hacks on
>> newer
>> systems) and also the mini-os port needs some polishing. Maybe ubuntu
>> has newer build tools which ones causing some incompatibilities, I do
>> not know.
>>
>> Is it possible fixing any of these problems?
>>
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xen.org
>> http://lists.xen.org/xen-devel
>>
>>
>> _______________________________________________
>> Xen-users mailing list
>> Xen-users@lists.xen.org
>> http://lists.xen.org/xen-users

-- 


Éliás Tamás
Thomas Elias

ETIT[nwpro] KFT, Ügyvezető-Hálózatbiztonsági specialista
ETIT[nwpro] Ltd, General Manager-Network security specialist

Tel. HU: +36/30-497-1626
Tel. DE: +49/160-651-8723
OpenPGP pubkey: http://etit.hu/doc/et-pub.asc

Okleveles mérnök-informatikus (MSC)
Master of Science in Information Technology (MSC)

Kapcsolat: http://etit.hu/index.php/hu/kapcsolat
Jogi nyilatkozat: http://etit.hu/disclaimer-email-hu.txt
Contact: http://etit.hu/index.php/en/contact
Disclaimer: http://etit.hu/disclaimer-email-en.txt

[-- Attachment #1.1.1.2: compiling Xen 4.6 on Xenial.eml --]
[-- Type: message/rfc822, Size: 4712 bytes --]

[-- Attachment #1.1.1.2.1.1: Type: text/plain, Size: 813 bytes --]

http://lists.xenproject.org/archives/html/xen-users/2016-03/msg00092.html

I saw this post to xen-users. My mail client has not yet received it, so I
replied in a non-standard way.

I have had similar or same issues as you, and more, compiling this. You
will have other problems running Xen on Xenial, especially if your domU are
LVM based.

Here is my effort:
http://107.185.144.55/xen/ubuntu/xenial/46x/

I like building from the tarball, since its easier to patch (from xen root
base). Also the release tarball has qemu included. My linked build folder
also has a binary for ovmf.bin.46

If you wonder why building on Xenial is so chaotic, its because the Xen
devs/testers do not support gcc 5.x and have no interest. They only
recently started running Deb 8.x tests on their OSSTEST system.

PryMar56 on #xen

[-- Attachment #1.1.1.2.1.2: Type: text/html, Size: 1091 bytes --]

[-- Attachment #1.1.1.3: Képernyőkép erről: 2016-04-01 00-04-00.png --]
[-- Type: image/png, Size: 228255 bytes --]

[-- Attachment #1.1.1.4: Képernyőkép erről: 2016-04-01 00-04-12.png --]
[-- Type: image/png, Size: 241045 bytes --]

[-- Attachment #1.1.1.5: Képernyőkép erről: 2016-04-01 00-04-17.png --]
[-- Type: image/png, Size: 168896 bytes --]

[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

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

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

Re: compilation fail, xen staging-4.6, vnc.c, qemu-tradintional issues under ubuntu 16.04

[George Dunlap]

On Wed, Mar 30, 2016 at 3:58 PM, Dario Faggioli
<dario.faggioli@citrix.com> wrote:
> Cc-ing some tools, Qemu, and Stubdom/MiniOS people, and dropping xen-
> users (Bcc-ed)...
>
[snip]

>> vl.c:2784:5: error: ‘g_mem_set_vtable’ is deprecated
>> [-Werror=deprecated-declarations]
>>      g_mem_set_vtable(&mem_trace);
>>
>>
>> I had to apply
>>
>> https://lists.gnu.org/archive/html/qemu-devel/2015-09/msg01262.html
>>
>> which seemes that only partially been applied (has rejects), but
>> after
>> modifying the sources by hand, it seemes working.

Anthony / Stefano / Ian, this is still failing two months later:

vl.c: In function ‘main’:
vl.c:2784:5: error: ‘g_mem_set_vtable’ is deprecated
[-Werror=deprecated-declarations]
     g_mem_set_vtable(&mem_trace);
     ^
In file included from /usr/include/glib-2.0/glib/glist.h:32:0,
                 from /usr/include/glib-2.0/glib/ghash.h:33,
                 from /usr/include/glib-2.0/glib.h:50,
                 from vl.c:59:
/usr/include/glib-2.0/glib/gmem.h:357:6: note: declared here
 void  g_mem_set_vtable (GMemVTable *vtable);
      ^
cc1: all warnings being treated as errors
/root/git/xen.git/tools/qemu-xen-dir/rules.mak:57: recipe for target
'vl.o' failed

 -George

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

Re: compilation fail, xen staging-4.6, vnc.c, qemu-tradintional issues under ubuntu 16.04

[Ian Jackson]

George Dunlap writes ("Re: [Xen-devel] compilation fail, xen staging-4.6, vnc.c, qemu-tradintional issues under ubuntu 16.04"):
> Anthony / Stefano / Ian, this is still failing two months later:
> 
> vl.c: In function ‘main’:
> vl.c:2784:5: error: ‘g_mem_set_vtable’ is deprecated
> [-Werror=deprecated-declarations]
>      g_mem_set_vtable(&mem_trace);
>      ^
> In file included from /usr/include/glib-2.0/glib/glist.h:32:0,
>                  from /usr/include/glib-2.0/glib/ghash.h:33,
>                  from /usr/include/glib-2.0/glib.h:50,
>                  from vl.c:59:
> /usr/include/glib-2.0/glib/gmem.h:357:6: note: declared here
>  void  g_mem_set_vtable (GMemVTable *vtable);
>       ^
> cc1: all warnings being treated as errors
> /root/git/xen.git/tools/qemu-xen-dir/rules.mak:57: recipe for target
> 'vl.o' failed

Anthony, perhaps while you're looking at the XSA-180 backports you
could look at this too ?

(I can confirm that with qemu-xen staging-4.6, git-grep
g_mem_set_vtable produces some output, but I haven't investigated
further.  I don't know which Xen branches are affected.)

I think this should be fixed for the forthcoming 4.6 point release,
ideally.

Ian.

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

Re: compilation fail, xen staging-4.6, vnc.c, qemu-tradintional issues under ubuntu 16.04

[Anthony PERARD]

On Fri, Jun 10, 2016 at 12:26:21PM +0100, George Dunlap wrote:
> On Wed, Mar 30, 2016 at 3:58 PM, Dario Faggioli
> <dario.faggioli@citrix.com> wrote:
> > Cc-ing some tools, Qemu, and Stubdom/MiniOS people, and dropping xen-
> > users (Bcc-ed)...
> >
> [snip]
> 
> >> vl.c:2784:5: error: ‘g_mem_set_vtable’ is deprecated
> >> [-Werror=deprecated-declarations]
> >>      g_mem_set_vtable(&mem_trace);
> >>
> >>
> >> I had to apply
> >>
> >> https://lists.gnu.org/archive/html/qemu-devel/2015-09/msg01262.html
> >>
> >> which seemes that only partially been applied (has rejects), but
> >> after
> >> modifying the sources by hand, it seemes working.
> 
> Anthony / Stefano / Ian, this is still failing two months later:
> 
> vl.c: In function ‘main’:
> vl.c:2784:5: error: ‘g_mem_set_vtable’ is deprecated
> [-Werror=deprecated-declarations]
>      g_mem_set_vtable(&mem_trace);
>      ^
> In file included from /usr/include/glib-2.0/glib/glist.h:32:0,
>                  from /usr/include/glib-2.0/glib/ghash.h:33,
>                  from /usr/include/glib-2.0/glib.h:50,
>                  from vl.c:59:
> /usr/include/glib-2.0/glib/gmem.h:357:6: note: declared here
>  void  g_mem_set_vtable (GMemVTable *vtable);
>       ^
> cc1: all warnings being treated as errors
> /root/git/xen.git/tools/qemu-xen-dir/rules.mak:57: recipe for target
> 'vl.o' failed

# edit tools/Makefile to not compile xentrace
./configure --disable-qemu-traditional --with-extra-qemuu-configure-args='--disable-werror'
make

Works for me :).

Should we add --disable-werror to QEMU when doing a release? Or do we
really want to fix compilation warnings in stable branches?

-- 
Anthony PERARD

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

Re: compilation fail, xen staging-4.6, vnc.c, qemu-tradintional issues under ubuntu 16.04

[George Dunlap]

On Fri, Jun 10, 2016 at 3:00 PM, Anthony PERARD
<anthony.perard@citrix.com> wrote:
> On Fri, Jun 10, 2016 at 12:26:21PM +0100, George Dunlap wrote:
>> On Wed, Mar 30, 2016 at 3:58 PM, Dario Faggioli
>> <dario.faggioli@citrix.com> wrote:
>> > Cc-ing some tools, Qemu, and Stubdom/MiniOS people, and dropping xen-
>> > users (Bcc-ed)...
>> >
>> [snip]
>>
>> >> vl.c:2784:5: error: ‘g_mem_set_vtable’ is deprecated
>> >> [-Werror=deprecated-declarations]
>> >>      g_mem_set_vtable(&mem_trace);
>> >>
>> >>
>> >> I had to apply
>> >>
>> >> https://lists.gnu.org/archive/html/qemu-devel/2015-09/msg01262.html
>> >>
>> >> which seemes that only partially been applied (has rejects), but
>> >> after
>> >> modifying the sources by hand, it seemes working.
>>
>> Anthony / Stefano / Ian, this is still failing two months later:
>>
>> vl.c: In function ‘main’:
>> vl.c:2784:5: error: ‘g_mem_set_vtable’ is deprecated
>> [-Werror=deprecated-declarations]
>>      g_mem_set_vtable(&mem_trace);
>>      ^
>> In file included from /usr/include/glib-2.0/glib/glist.h:32:0,
>>                  from /usr/include/glib-2.0/glib/ghash.h:33,
>>                  from /usr/include/glib-2.0/glib.h:50,
>>                  from vl.c:59:
>> /usr/include/glib-2.0/glib/gmem.h:357:6: note: declared here
>>  void  g_mem_set_vtable (GMemVTable *vtable);
>>       ^
>> cc1: all warnings being treated as errors
>> /root/git/xen.git/tools/qemu-xen-dir/rules.mak:57: recipe for target
>> 'vl.o' failed
>
> # edit tools/Makefile to not compile xentrace
> ./configure --disable-qemu-traditional --with-extra-qemuu-configure-args='--disable-werror'
> make
>
> Works for me :).
>
> Should we add --disable-werror to QEMU when doing a release? Or do we
> really want to fix compilation warnings in stable branches?

I think so, yes.  Consider this case, where the new version of glibc
has this marked as deprecated -- new point releases in particular
should build without using deprecated functionality.

 -George

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

Re: compilation fail, xen staging-4.6, vnc.c, qemu-tradintional issues under ubuntu 16.04

[Anthony PERARD]

On Fri, Jun 10, 2016 at 03:08:19PM +0100, George Dunlap wrote:
> On Fri, Jun 10, 2016 at 3:00 PM, Anthony PERARD
> <anthony.perard@citrix.com> wrote:
> > On Fri, Jun 10, 2016 at 12:26:21PM +0100, George Dunlap wrote:
> >> On Wed, Mar 30, 2016 at 3:58 PM, Dario Faggioli
> >> <dario.faggioli@citrix.com> wrote:
> >> > Cc-ing some tools, Qemu, and Stubdom/MiniOS people, and dropping xen-
> >> > users (Bcc-ed)...
> >> >
> >> [snip]
> >>
> >> >> vl.c:2784:5: error: ‘g_mem_set_vtable’ is deprecated
> >> >> [-Werror=deprecated-declarations]
> >> >>      g_mem_set_vtable(&mem_trace);
> >> >>
> >> >>
> >> >> I had to apply
> >> >>
> >> >> https://lists.gnu.org/archive/html/qemu-devel/2015-09/msg01262.html
> >> >>
> >> >> which seemes that only partially been applied (has rejects), but
> >> >> after
> >> >> modifying the sources by hand, it seemes working.
> >>
> >> Anthony / Stefano / Ian, this is still failing two months later:
> >>
> >> vl.c: In function ‘main’:
> >> vl.c:2784:5: error: ‘g_mem_set_vtable’ is deprecated
> >> [-Werror=deprecated-declarations]
> >>      g_mem_set_vtable(&mem_trace);
> >>      ^
> >> In file included from /usr/include/glib-2.0/glib/glist.h:32:0,
> >>                  from /usr/include/glib-2.0/glib/ghash.h:33,
> >>                  from /usr/include/glib-2.0/glib.h:50,
> >>                  from vl.c:59:
> >> /usr/include/glib-2.0/glib/gmem.h:357:6: note: declared here
> >>  void  g_mem_set_vtable (GMemVTable *vtable);
> >>       ^
> >> cc1: all warnings being treated as errors
> >> /root/git/xen.git/tools/qemu-xen-dir/rules.mak:57: recipe for target
> >> 'vl.o' failed
> >
> > # edit tools/Makefile to not compile xentrace
> > ./configure --disable-qemu-traditional --with-extra-qemuu-configure-args='--disable-werror'
> > make
> >
> > Works for me :).
> >
> > Should we add --disable-werror to QEMU when doing a release? Or do we
> > really want to fix compilation warnings in stable branches?
> 
> I think so, yes.  Consider this case, where the new version of glibc
> has this marked as deprecated -- new point releases in particular
> should build without using deprecated functionality.

For this case, we can apply: 98cf48f (trace: remove malloc tracing),
which remove the offending line.

-- 
Anthony PERARD

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

Re: compilation fail, xen staging-4.6, vnc.c, qemu-tradintional issues under ubuntu 16.04

[Anthony PERARD]

On Fri, Jun 10, 2016 at 01:14:43PM +0100, Ian Jackson wrote:
> George Dunlap writes ("Re: [Xen-devel] compilation fail, xen staging-4.6, vnc.c, qemu-tradintional issues under ubuntu 16.04"):
> > Anthony / Stefano / Ian, this is still failing two months later:
> > 
> > vl.c: In function ‘main’:
> > vl.c:2784:5: error: ‘g_mem_set_vtable’ is deprecated
> > [-Werror=deprecated-declarations]
> >      g_mem_set_vtable(&mem_trace);
> >      ^
> > In file included from /usr/include/glib-2.0/glib/glist.h:32:0,
> >                  from /usr/include/glib-2.0/glib/ghash.h:33,
> >                  from /usr/include/glib-2.0/glib.h:50,
> >                  from vl.c:59:
> > /usr/include/glib-2.0/glib/gmem.h:357:6: note: declared here
> >  void  g_mem_set_vtable (GMemVTable *vtable);
> >       ^
> > cc1: all warnings being treated as errors
> > /root/git/xen.git/tools/qemu-xen-dir/rules.mak:57: recipe for target
> > 'vl.o' failed
> 
> Anthony, perhaps while you're looking at the XSA-180 backports you
> could look at this too ?
> 
> (I can confirm that with qemu-xen staging-4.6, git-grep
> g_mem_set_vtable produces some output, but I haven't investigated
> further.  I don't know which Xen branches are affected.)
> 
> I think this should be fixed for the forthcoming 4.6 point release,
> ideally.

I've push upstream commit 98cf48f (trace: remove malloc tracing) to
qemu-xen staging-4.6 and 4.5.

-- 
Anthony PERARD

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

Re: compilation fail, xen staging-4.6, vnc.c, qemu-tradintional issues under ubuntu 16.04

[Stefano Stabellini]

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1565 bytes --]

On Fri, 10 Jun 2016, Anthony PERARD wrote:
> On Fri, Jun 10, 2016 at 01:14:43PM +0100, Ian Jackson wrote:
> > George Dunlap writes ("Re: [Xen-devel] compilation fail, xen staging-4.6, vnc.c, qemu-tradintional issues under ubuntu 16.04"):
> > > Anthony / Stefano / Ian, this is still failing two months later:
> > > 
> > > vl.c: In function ‘main’:
> > > vl.c:2784:5: error: ‘g_mem_set_vtable’ is deprecated
> > > [-Werror=deprecated-declarations]
> > >      g_mem_set_vtable(&mem_trace);
> > >      ^
> > > In file included from /usr/include/glib-2.0/glib/glist.h:32:0,
> > >                  from /usr/include/glib-2.0/glib/ghash.h:33,
> > >                  from /usr/include/glib-2.0/glib.h:50,
> > >                  from vl.c:59:
> > > /usr/include/glib-2.0/glib/gmem.h:357:6: note: declared here
> > >  void  g_mem_set_vtable (GMemVTable *vtable);
> > >       ^
> > > cc1: all warnings being treated as errors
> > > /root/git/xen.git/tools/qemu-xen-dir/rules.mak:57: recipe for target
> > > 'vl.o' failed
> > 
> > Anthony, perhaps while you're looking at the XSA-180 backports you
> > could look at this too ?
> > 
> > (I can confirm that with qemu-xen staging-4.6, git-grep
> > g_mem_set_vtable produces some output, but I haven't investigated
> > further.  I don't know which Xen branches are affected.)
> > 
> > I think this should be fixed for the forthcoming 4.6 point release,
> > ideally.
> 
> I've push upstream commit 98cf48f (trace: remove malloc tracing) to
> qemu-xen staging-4.6 and 4.5.

In that case we'll need new tags. 4.6.3? 4.6.2.1?

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

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

Re: compilation fail, xen staging-4.6, vnc.c, qemu-tradintional issues under ubuntu 16.04

[Jan Beulich]

>>> On 10.06.16 at 17:00, <sstabellini@kernel.org> wrote:
> On Fri, 10 Jun 2016, Anthony PERARD wrote:
>> On Fri, Jun 10, 2016 at 01:14:43PM +0100, Ian Jackson wrote:
>> > George Dunlap writes ("Re: [Xen-devel] compilation fail, xen staging-4.6, 
> vnc.c, qemu-tradintional issues under ubuntu 16.04"):
>> > > Anthony / Stefano / Ian, this is still failing two months later:
>> > > 
>> > > vl.c: In function ‘main’:
>> > > vl.c:2784:5: error: ‘g_mem_set_vtable’ is deprecated
>> > > [-Werror=deprecated-declarations]
>> > >      g_mem_set_vtable(&mem_trace);
>> > >      ^
>> > > In file included from /usr/include/glib-2.0/glib/glist.h:32:0,
>> > >                  from /usr/include/glib-2.0/glib/ghash.h:33,
>> > >                  from /usr/include/glib-2.0/glib.h:50,
>> > >                  from vl.c:59:
>> > > /usr/include/glib-2.0/glib/gmem.h:357:6: note: declared here
>> > >  void  g_mem_set_vtable (GMemVTable *vtable);
>> > >       ^
>> > > cc1: all warnings being treated as errors
>> > > /root/git/xen.git/tools/qemu-xen-dir/rules.mak:57: recipe for target
>> > > 'vl.o' failed
>> > 
>> > Anthony, perhaps while you're looking at the XSA-180 backports you
>> > could look at this too ?
>> > 
>> > (I can confirm that with qemu-xen staging-4.6, git-grep
>> > g_mem_set_vtable produces some output, but I haven't investigated
>> > further.  I don't know which Xen branches are affected.)
>> > 
>> > I think this should be fixed for the forthcoming 4.6 point release,
>> > ideally.
>> 
>> I've push upstream commit 98cf48f (trace: remove malloc tracing) to
>> qemu-xen staging-4.6 and 4.5.
> 
> In that case we'll need new tags. 4.6.3? 4.6.2.1?

4.6.2a or 4.6.2b I would say, as the main release number is still
going to be 4.6.2.

Jan

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

Re: compilation fail, xen staging-4.6, vnc.c, qemu-tradintional issues under ubuntu 16.04

[Jan Beulich]

>>> On 10.06.16 at 17:24, <JBeulich@suse.com> wrote:
>>>> On 10.06.16 at 17:00, <sstabellini@kernel.org> wrote:
>> On Fri, 10 Jun 2016, Anthony PERARD wrote:
>>> On Fri, Jun 10, 2016 at 01:14:43PM +0100, Ian Jackson wrote:
>>> > George Dunlap writes ("Re: [Xen-devel] compilation fail, xen staging-4.6, 
>> vnc.c, qemu-tradintional issues under ubuntu 16.04"):
>>> > > Anthony / Stefano / Ian, this is still failing two months later:
>>> > > 
>>> > > vl.c: In function ‘main’:
>>> > > vl.c:2784:5: error: ‘g_mem_set_vtable’ is deprecated
>>> > > [-Werror=deprecated-declarations]
>>> > >      g_mem_set_vtable(&mem_trace);
>>> > >      ^
>>> > > In file included from /usr/include/glib-2.0/glib/glist.h:32:0,
>>> > >                  from /usr/include/glib-2.0/glib/ghash.h:33,
>>> > >                  from /usr/include/glib-2.0/glib.h:50,
>>> > >                  from vl.c:59:
>>> > > /usr/include/glib-2.0/glib/gmem.h:357:6: note: declared here
>>> > >  void  g_mem_set_vtable (GMemVTable *vtable);
>>> > >       ^
>>> > > cc1: all warnings being treated as errors
>>> > > /root/git/xen.git/tools/qemu-xen-dir/rules.mak:57: recipe for target
>>> > > 'vl.o' failed
>>> > 
>>> > Anthony, perhaps while you're looking at the XSA-180 backports you
>>> > could look at this too ?
>>> > 
>>> > (I can confirm that with qemu-xen staging-4.6, git-grep
>>> > g_mem_set_vtable produces some output, but I haven't investigated
>>> > further.  I don't know which Xen branches are affected.)
>>> > 
>>> > I think this should be fixed for the forthcoming 4.6 point release,
>>> > ideally.
>>> 
>>> I've push upstream commit 98cf48f (trace: remove malloc tracing) to
>>> qemu-xen staging-4.6 and 4.5.
>> 
>> In that case we'll need new tags. 4.6.3? 4.6.2.1?
> 
> 4.6.2a or 4.6.2b I would say, as the main release number is still
> going to be 4.6.2.

But wait - the subject says qemu-trad, which didn't get tagged yet.
Did these commits go into the qemu-xen tree really? I guess I'm
confused now...

Jan

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

Re: compilation fail, xen staging-4.6, vnc.c, qemu-tradintional issues under ubuntu 16.04

[George Dunlap]

On Fri, Jun 10, 2016 at 4:30 PM, Jan Beulich <JBeulich@suse.com> wrote:
>>>> On 10.06.16 at 17:24, <JBeulich@suse.com> wrote:
>>>>> On 10.06.16 at 17:00, <sstabellini@kernel.org> wrote:
>>> On Fri, 10 Jun 2016, Anthony PERARD wrote:
>>>> On Fri, Jun 10, 2016 at 01:14:43PM +0100, Ian Jackson wrote:
>>>> > George Dunlap writes ("Re: [Xen-devel] compilation fail, xen staging-4.6,
>>> vnc.c, qemu-tradintional issues under ubuntu 16.04"):
>>>> > > Anthony / Stefano / Ian, this is still failing two months later:
>>>> > >
>>>> > > vl.c: In function ‘main’:
>>>> > > vl.c:2784:5: error: ‘g_mem_set_vtable’ is deprecated
>>>> > > [-Werror=deprecated-declarations]
>>>> > >      g_mem_set_vtable(&mem_trace);
>>>> > >      ^
>>>> > > In file included from /usr/include/glib-2.0/glib/glist.h:32:0,
>>>> > >                  from /usr/include/glib-2.0/glib/ghash.h:33,
>>>> > >                  from /usr/include/glib-2.0/glib.h:50,
>>>> > >                  from vl.c:59:
>>>> > > /usr/include/glib-2.0/glib/gmem.h:357:6: note: declared here
>>>> > >  void  g_mem_set_vtable (GMemVTable *vtable);
>>>> > >       ^
>>>> > > cc1: all warnings being treated as errors
>>>> > > /root/git/xen.git/tools/qemu-xen-dir/rules.mak:57: recipe for target
>>>> > > 'vl.o' failed
>>>> >
>>>> > Anthony, perhaps while you're looking at the XSA-180 backports you
>>>> > could look at this too ?
>>>> >
>>>> > (I can confirm that with qemu-xen staging-4.6, git-grep
>>>> > g_mem_set_vtable produces some output, but I haven't investigated
>>>> > further.  I don't know which Xen branches are affected.)
>>>> >
>>>> > I think this should be fixed for the forthcoming 4.6 point release,
>>>> > ideally.
>>>>
>>>> I've push upstream commit 98cf48f (trace: remove malloc tracing) to
>>>> qemu-xen staging-4.6 and 4.5.
>>>
>>> In that case we'll need new tags. 4.6.3? 4.6.2.1?
>>
>> 4.6.2a or 4.6.2b I would say, as the main release number is still
>> going to be 4.6.2.
>
> But wait - the subject says qemu-trad, which didn't get tagged yet.
> Did these commits go into the qemu-xen tree really? I guess I'm
> confused now...

The original report actually had 3 different issues -- the one I'm
re-raising was the one I'm personally still tripping over.  (Don't
know about the other two.)

 -George

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

Re: compilation fail, xen staging-4.6, vnc.c, qemu-tradintional issues under ubuntu 16.04

[Ian Jackson]

George Dunlap writes ("Re: [Xen-devel] compilation fail, xen staging-4.6, vnc.c, qemu-tradintional issues under ubuntu 16.04"):
> The original report actually had 3 different issues -- the one I'm
> re-raising was the one I'm personally still tripping over.  (Don't
> know about the other two.)

The gnutls_kx_set_priority and g_mem_set_vtable problems don't seem
applicable to trad AFAICT.  The final problem in the bug report is a
stubdom build failure which doesn't seem to have anything to do with
qemu.  So I think qemu-trad is a red herring ?

Ian.

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