Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 636038 - app-emulation/xen-tools-4.7.3 fails to build: tap-ctl-allocate.c:109:13: error: In the GNU C Library, "makedev" is defined
Summary: app-emulation/xen-tools-4.7.3 fails to build: tap-ctl-allocate.c:109:13: erro...
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: AMD64 Linux
: Normal normal (vote)
Assignee: Gentoo Xen Devs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-10-31 14:22 UTC by Richard
Modified: 2017-11-03 18:38 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Richard 2017-10-31 14:22:03 UTC
Hi after update glibc at glibc-2.25-r8 i cant compile xen-tools.4.7.3

tap-ctl-allocate.c:109:13: error: In the GNU C Library, "makedev" is defined
 by <sys/sysmacros.h>. For historical compatibility, it is
 currently defined by <sys/types.h> as well, but we plan to
 remove this soon. To use "makedev", include <sys/sysmacros.h>
 directly. If you did not intend to use a system-defined macro
 "makedev", you should undefine it after including <sys/types.h>. [-Werror]
  err = mknod(devname, perm, makedev(major, minor));


I solve the problem adding #include <sys/sysmacros.h> at files:

xen-4.7.3/tools/blktap2/control/tap-ctl-allocate.c

xen-4.7.3/tools/libxl/libxl_internal.h
Comment 1 Tomáš Mózes 2017-11-01 11:01:29 UTC
There is an ongoing stabilization of Xen 4.8.2, please put it into your accept_keywords and use that one.
Comment 2 Richard 2017-11-01 11:24:07 UTC
(In reply to Tomáš Mózes from comment #1)
> There is an ongoing stabilization of Xen 4.8.2, please put it into your
> accept_keywords and use that one.

I install Xen 4.8.2, pv works fine but HVM running few minutes then crash with this error (same with Xen-4.7.3)

Domain 27 has shut down, reason code 3 0x3
Action for shutdown reason code 3 is destroy
Domain 27 needs to be cleaned up: destroying the domain
Done. Exiting now

I trying downgrade glibc to glibc-2.23-r4
Comment 3 Tomáš Mózes 2017-11-01 12:08:19 UTC
(In reply to Richard from comment #2)
> (In reply to Tomáš Mózes from comment #1)
> > There is an ongoing stabilization of Xen 4.8.2, please put it into your
> > accept_keywords and use that one.
> 
> I install Xen 4.8.2, pv works fine but HVM running few minutes then crash
> with this error (same with Xen-4.7.3)
> 
> Domain 27 has shut down, reason code 3 0x3
> Action for shutdown reason code 3 is destroy
> Domain 27 needs to be cleaned up: destroying the domain
> Done. Exiting now
> 
> I trying downgrade glibc to glibc-2.23-r4

I'm not sure if it's still true, but you cannot downgrade glibc. By the way, I've a few xen machines with glibc 2.25 and xen 4.8.2 and it works fine (hvm).
Comment 4 Tomáš Mózes 2017-11-01 12:09:07 UTC
Did your HVM machines work with any previous glibc/xen on that machine?
Comment 5 Richard 2017-11-01 12:31:27 UTC
(In reply to Tomáš Mózes from comment #3)
> (In reply to Richard from comment #2)
> > (In reply to Tomáš Mózes from comment #1)
> > > There is an ongoing stabilization of Xen 4.8.2, please put it into your
> > > accept_keywords and use that one.
> > 
> > I install Xen 4.8.2, pv works fine but HVM running few minutes then crash
> > with this error (same with Xen-4.7.3)
> > 
> > Domain 27 has shut down, reason code 3 0x3
> > Action for shutdown reason code 3 is destroy
> > Domain 27 needs to be cleaned up: destroying the domain
> > Done. Exiting now
> > 
> > I trying downgrade glibc to glibc-2.23-r4
> 
> I'm not sure if it's still true, but you cannot downgrade glibc. By the way,
> I've a few xen machines with glibc 2.25 and xen 4.8.2 and it works fine
> (hvm).

Sorry i know cannot downgrade, i restore backup with glibc-2.23-r4
Comment 6 Richard 2017-11-01 13:05:20 UTC
(In reply to Tomáš Mózes from comment #4)
> Did your HVM machines work with any previous glibc/xen on that machine?

Yes, but i found the problem. HVM is a windows 32bits (3GB max memory) the configuration file of this vm have an error

memory = 2048
maxmem = 16384

#xl dmesg
(XEN) p2m_pod_demand_populate: Dom28 out of PoD memory! (tot=524363 ents=3670016 dom0)
(XEN) domain_crash called from p2m-pod.c:1146

I correct maxmem var, and all works fine.

Thanks.
Comment 7 Tomáš Mózes 2017-11-03 18:38:48 UTC
Now version 4.8.2 is stable.