[meta-freescale] building core-image-minimalfort1042d4rdb*failsbuilding hypervisor

[Zhenhua Luo]

Hi Robert, 

The patch is submitted to fix the hypervisor build issue. https://patchwork.openembedded.org/patch/141881/. 

The hypervisor is a layer of software that enables the efficient and secure partitioning of a multicore system. A system's CPUs, memory, and I/O devices can be divided into groupings or partitions, as shown in the figure below. Each partition is capable of executing a guest operating system. For more details, you can refer to the QorIQ SDK document which is available in http://tinyurl.com/ya57eeol. 


Best Regards, 

Zhenhua

> -----Original Message-----
> From: Robert P. J. Day [mailto:rpjday at crashcourse.ca]
> Sent: Thursday, July 13, 2017 5:48 AM
> To: Zhenhua Luo <zhenhua.luo at nxp.com>
> Cc: Kursad Oney CW <koney at mmm.com>; meta-freescale at yoctoproject.org;
> C.r. Guo <chunrong.guo at nxp.com>
> Subject: RE: [meta-freescale] building core-image-
> minimalfort1042d4rdb*failsbuilding hypervisor
> 
> On Tue, 11 Jul 2017, Zhenhua Luo wrote:
> 
> > Hi all,
> >
> > We will take a look the issue and fix it ASAP.
> >
> >
> > Best Regards,
> >
> > Zhenhua
> >
> > > -----Original Message-----
> > > From: meta-freescale-bounces at yoctoproject.org
> > > [mailto:meta-freescale- bounces at yoctoproject.org] On Behalf Of
> > > Kursad Oney CW
> > > Sent: Sunday, July 09, 2017 11:24 PM
> > > To: Robert P. J. Day <rpjday at crashcourse.ca>
> > > Cc: meta-freescale at yoctoproject.org
> > > Subject: Re: [meta-freescale] building core-image-
> > > minimalfort1042d4rdb*failsbuilding hypervisor
> > >
> > > Robert,
> > >
> > > >
> > > > > Robert,
> > > > >
> > > > > >   to make a long story (hopefully) short, i was trying to
> > > > > > build both the 32- and 64-bit versions of t1042d4rdb, and both
> > > > > > failed in exactly the same place, trying to build the
> > > > > > hypervisor recipe, so i'm open to suggestions (this is on a fully-updated
> fedora system):
> > > > > >
> > > > > > [...truncated...]
> > > > > > | /home/rpjday/oe/builds/t1042d4rdb-64b/tmp/work/ppc64e5500-po
> > > > > > | ky-
> > > linux/hypervisor/git-r3/git/libos/lib/sprintf.c: In function 'sprintf':
> > > > > > | /home/rpjday/oe/builds/t1042d4rdb-64b/tmp/work/ppc64e5500-po
> > > > > > | ky-
> > > linux/hypervisor/git-r3/git/libos/lib/sprintf.c:459:6: error:
> > > specified bound
> > > 18446744073709551615 exceeds maximum object size
> 9223372036854775807
> > > [-Werror=format-truncation=]
> > > > > > |   int ret = vsnprintf(buf, ULONG_MAX, str, args);
> > > > > > |       ^~~
> > > > > > | cc1: all warnings being treated as errors
> > > > >
> > > > > I think gcc is complaining about ULONG_MAX being the size argument.
> > > > > Since vsnprintf() returns int, it can print at most LONG_MAX
> > > > > characters to the buffer. I'd probably just change that argument
> > > > > to
> > > LONG_MAX.
> > > > >
> > > > > I believe the format-truncation flag is a gcc 7 thing.
> > > >
> > > >   i suspected as much, but i'm curious as to why this error still
> > > > exists, and wasn't flagged by regular build testing. i don't just
> > > > want to hack the code without hearing from others as to why this
> > > > issue exists.
> > >
> > > To take a wild guess, I would say the yocto version you are using
> > > probably upgraded to gcc 7 where this new flag became a default for
> > > -Werror. If you try an older branch or just use the recipe for gcc 6, the
> warning might go away.
> > >
> > > That said the DNG team at NXP would be the definite authority on this.
> 
>   while fixing that hypervisor compile error, here's probably a dumb question ...
> what do i need the hypervisor for, anyway? since it's listed in
> EXTRA_IMAGEDEPENDS, i can clearly temporarily remove it to get a build. as i'm
> new to this target and processor, what's it for?
> 
> rday
> 
> --
> 
> =================================================================
> =======
> Robert P. J. Day                                 Ottawa, Ontario, CANADA
>                         http://crashcourse.ca
> 
> Twitter:                                       http://twitter.com/rpjday
> LinkedIn:                               http://ca.linkedin.com/in/rpjday
> =================================================================
> =======