Due to clang problems[1] I've switched to gcc from FreeBSD ports.
That involves some minor fixes provided in this series.
Roman Bogorodskiy (2):
bhyve: fix bhyvexml2argvtest build with gcc
maint: extend PIE support check
m4/virt-compile-pie.m4| 4 ++--
tests/bhyvexml2argvtest.c | 2 --
2
GCC installed from FreeBSD ports doesn't support building PIE executables
and fails with:
/usr/local/bin/ld: /usr/lib/crt1.o: relocation R_X86_64_32 against
`_DYNAMIC' can not be used when making a shared object; recompile with
-fPIC
/usr/lib/crt1.o: error adding symbols: Bad value
collect2: error
gcc5 reports an error like this:
bhyvexml2argvtest.c: In function 'testCompareXMLToArgvFiles':
bhyvexml2argvtest.c:24:18: error: variable 'vm' set but not used
[-Werror=unused-but-set-variable]
virDomainObj vm;
^
cc1: all warnings being treated as errors
Fix by dropping thi
Roman Bogorodskiy wrote:
> Eric Blake wrote:
>
> > On 05/08/2015 12:23 AM, Roman Bogorodskiy wrote:
> > > Roman Bogorodskiy wrote:
> > >
> > >> Roman Bogorodskiy wrote:
> > >>
> > >>> Currently the stack frame size limit is set to 4096 and it started to
> > >>> cause an error like this:
Roman Bogorodskiy wrote:
> Due to clang problems[1] I've switched to gcc from FreeBSD ports.
> That involves some minor fixes provided in this series.
Oops, it misses:
1: https://www.redhat.com/archives/libvir-list/2015-May/msg00011.html
> Roman Bogorodskiy (2):
> bhyve: fix bhyvexml2argvte
On Fri, May 08, 2015 at 04:31:02PM -0600, Jim Fehlig wrote:
> For HVM domains, vfb info must be populated in the libxl_domain_build_info
> stuct. Currently this is done in the libxlMakeVfbList function, but IMO
struct
> it would be cleaner to populate the build_info vfb in a separate
> libxlMakeB
