Re: [Xen-devel] Unable to build staging-4.9 on RHEL6
>>> On 27.08.18 at 13:30, wrote:
> On Monday, 27 August 2018 8:36:50 PM AEST Jan Beulich wrote:
>> >>> On 27.08.18 at 12:03, wrote:
>> > On Monday, 27 August 2018 6:32:17 PM AEST Jan Beulich wrote:
>> >> >>> On 24.08.18 at 04:56, wrote:
>> >> > When trying to build both xen and qemu-xen from the staging-4.9
>> >> > branches, I'm running into issues compiling.
>> >> >
>> >> > Errors start with:
>> >> >
>> >> > BUILDSTDERR: sse.c: In function 'simd_test':
>> >> > BUILDSTDERR: sse.c:319: error: subscripted value is neither array nor
>> >> > pointer
>> >>
>> >> That's the x86 insn emulator test harness afaict, which doesn't get
>> >> built unless you explicitly ask for it. Why are you building it? It's
>> >> well known that it requires a new enough compiler (and the bar will
>> >> raise with AVX512 support, which is in the works).
>> >
>> > Hi Jan,
>> >
>> > I don't specifically enable any testing (that I'm aware of).
>> >
>> > The current SPEC file that I'm using is at:
>> > https://git.crc.id.au/netwiz/xen49/src/devel/SPECS/xen49.spec
>> >
>> > Essentially it boils down to:
>> > ./configure --enable-systemd --prefix=/usr --enable-xsmpolicy
>> > %{?enable_ocaml}
>> > \
>> >
>> > --libdir=%{_libdir} --enable-efi --disable-qemu-traditional \
>> > --with-extra-qemuU-configure-args="--enable-spice --enable-usb-redir"
>> >
>> > (cd xen; make defconfig; sed -i 's/# CONFIG_LIVEPATCH is not set/
>> > CONFIG_LIVEPATCH=y/g' .config; make oldconfig)
>> >
>> > export XEN_DOMAIN=xen.crc.id.au
>> > make %{?_smp_mflags} %{?efi_flags} dist
>>
>> It's this last step which is of interest afaict; how you configure
>> things does not seem to matter. The dist target implies building
>> dist-tools, which in turn has install-tools as a dependency. Most
>> of the sub-directories under tools/tests/ have an empty
>> install target in their makefiles though, which means nothing is
>> going to be done when entering the respective directories.
>
> This is actually interesting.
>
> I tried originally doing a 'make build', then 'make DESTDIR=%{buildroot}
> install' - however I found that this didn't produce any EFI binaries in /boot/
> efi/efi/$EFI_VENDOR/ like the 'make dist' option does.
>
> This seemed to persist across all versions (4.6 - 4.10) hence the path that I
> had taken.
>
> Should this then be a part of fixing why no EFI binaries exist in the make
> build / make install method, and not trying to fix a test as a side effect of
> having to use 'make dist'?
Hmm - "make build" surely doesn't put anything anywhere outside the
build tree. At least I very much hope it doesn't. "make dist" and
"make install", otoh, ought to match in this respect though: Both
should install files into their dedicated places. After all
install: $(TARGS_INSTALL)
and
dist: $(TARGS_DIST) dist-misc
dist-%: install-%
But for me all of this is pure theory only anyway, as I never use any
of these targets.
Considering that xen.gz and xen.efi installation are don by the same
rule, quite a bit depends on whether you observe the two variants of
make invocation to differ in more that what lands in
/boot/efi/efi/$EFI_VENDOR/, in particular whether within the build
tree xen/xen.efi consistently appears. If both produce it, the
difference must be contained in xen/Makefile's _install rule. And don't
forget that putting _anything_ in /boot/efi/efi/$EFI_VENDOR/ is meant
as a courtesy to developers only anyway. Distributions should not
depend on this part; their boot loader setup should instead copy
whatever is necessary into /boot/efi/... (from, in the xen.efi case,
whatever EFI_DIR resolves to).
Jan
___
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
Re: [Xen-devel] Unable to build staging-4.9 on RHEL6
On Monday, 27 August 2018 8:36:50 PM AEST Jan Beulich wrote:
> >>> On 27.08.18 at 12:03, wrote:
> > On Monday, 27 August 2018 6:32:17 PM AEST Jan Beulich wrote:
> >> >>> On 24.08.18 at 04:56, wrote:
> >> > When trying to build both xen and qemu-xen from the staging-4.9
> >> > branches, I'm running into issues compiling.
> >> >
> >> > Errors start with:
> >> >
> >> > BUILDSTDERR: sse.c: In function 'simd_test':
> >> > BUILDSTDERR: sse.c:319: error: subscripted value is neither array nor
> >> > pointer
> >>
> >> That's the x86 insn emulator test harness afaict, which doesn't get
> >> built unless you explicitly ask for it. Why are you building it? It's
> >> well known that it requires a new enough compiler (and the bar will
> >> raise with AVX512 support, which is in the works).
> >
> > Hi Jan,
> >
> > I don't specifically enable any testing (that I'm aware of).
> >
> > The current SPEC file that I'm using is at:
> > https://git.crc.id.au/netwiz/xen49/src/devel/SPECS/xen49.spec
> >
> > Essentially it boils down to:
> > ./configure --enable-systemd --prefix=/usr --enable-xsmpolicy
> > %{?enable_ocaml}
> > \
> >
> > --libdir=%{_libdir} --enable-efi --disable-qemu-traditional \
> > --with-extra-qemuU-configure-args="--enable-spice --enable-usb-redir"
> >
> > (cd xen; make defconfig; sed -i 's/# CONFIG_LIVEPATCH is not set/
> > CONFIG_LIVEPATCH=y/g' .config; make oldconfig)
> >
> > export XEN_DOMAIN=xen.crc.id.au
> > make %{?_smp_mflags} %{?efi_flags} dist
>
> It's this last step which is of interest afaict; how you configure
> things does not seem to matter. The dist target implies building
> dist-tools, which in turn has install-tools as a dependency. Most
> of the sub-directories under tools/tests/ have an empty
> install target in their makefiles though, which means nothing is
> going to be done when entering the respective directories.
This is actually interesting.
I tried originally doing a 'make build', then 'make DESTDIR=%{buildroot}
install' - however I found that this didn't produce any EFI binaries in /boot/
efi/efi/$EFI_VENDOR/ like the 'make dist' option does.
This seemed to persist across all versions (4.6 - 4.10) hence the path that I
had taken.
Should this then be a part of fixing why no EFI binaries exist in the make
build / make install method, and not trying to fix a test as a side effect of
having to use 'make dist'?
> > I'll note that 4.6, 4.7, and 4.10 do not fail in this fashion using almost
> > the same command set to build.
>
> I can't spot any relevant difference between the versions you
> mention (or master). I'm afraid you'll need to dig a little deeper
> yourself (unless someone else has an idea).
>
> Jan
--
Steven Haigh
net...@crc.id.au https://www.crc.id.au
+61 (3) 9001 6090 0412 935 897
signature.asc
Description: This is a digitally signed message part.
___
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
Re: [Xen-devel] Unable to build staging-4.9 on RHEL6
>>> On 27.08.18 at 12:03, wrote:
> On Monday, 27 August 2018 6:32:17 PM AEST Jan Beulich wrote:
>> >>> On 24.08.18 at 04:56, wrote:
>> > When trying to build both xen and qemu-xen from the staging-4.9
>> > branches, I'm running into issues compiling.
>> >
>> > Errors start with:
>> >
>> > BUILDSTDERR: sse.c: In function 'simd_test':
>> > BUILDSTDERR: sse.c:319: error: subscripted value is neither array nor
>> > pointer
>>
>> That's the x86 insn emulator test harness afaict, which doesn't get
>> built unless you explicitly ask for it. Why are you building it? It's
>> well known that it requires a new enough compiler (and the bar will
>> raise with AVX512 support, which is in the works).
>
> Hi Jan,
>
> I don't specifically enable any testing (that I'm aware of).
>
> The current SPEC file that I'm using is at:
> https://git.crc.id.au/netwiz/xen49/src/devel/SPECS/xen49.spec
>
> Essentially it boils down to:
> ./configure --enable-systemd --prefix=/usr --enable-xsmpolicy
> %{?enable_ocaml}
> \
> --libdir=%{_libdir} --enable-efi --disable-qemu-traditional \
> --with-extra-qemuU-configure-args="--enable-spice --enable-usb-redir"
>
> (cd xen; make defconfig; sed -i 's/# CONFIG_LIVEPATCH is not set/
> CONFIG_LIVEPATCH=y/g' .config; make oldconfig)
>
> export XEN_DOMAIN=xen.crc.id.au
> make %{?_smp_mflags} %{?efi_flags} dist
It's this last step which is of interest afaict; how you configure
things does not seem to matter. The dist target implies building
dist-tools, which in turn has install-tools as a dependency. Most
of the sub-directories under tools/tests/ have an empty
install target in their makefiles though, which means nothing is
going to be done when entering the respective directories.
> I'll note that 4.6, 4.7, and 4.10 do not fail in this fashion using almost
> the
> same command set to build.
I can't spot any relevant difference between the versions you
mention (or master). I'm afraid you'll need to dig a little deeper
yourself (unless someone else has an idea).
Jan
___
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
Re: [Xen-devel] Unable to build staging-4.9 on RHEL6
On Monday, 27 August 2018 6:32:17 PM AEST Jan Beulich wrote:
> >>> On 24.08.18 at 04:56, wrote:
> > When trying to build both xen and qemu-xen from the staging-4.9
> > branches, I'm running into issues compiling.
> >
> > Errors start with:
> >
> > BUILDSTDERR: sse.c: In function 'simd_test':
> > BUILDSTDERR: sse.c:319: error: subscripted value is neither array nor
> > pointer
>
> That's the x86 insn emulator test harness afaict, which doesn't get
> built unless you explicitly ask for it. Why are you building it? It's
> well known that it requires a new enough compiler (and the bar will
> raise with AVX512 support, which is in the works).
Hi Jan,
I don't specifically enable any testing (that I'm aware of).
The current SPEC file that I'm using is at:
https://git.crc.id.au/netwiz/xen49/src/devel/SPECS/xen49.spec
Essentially it boils down to:
./configure --enable-systemd --prefix=/usr --enable-xsmpolicy %{?enable_ocaml}
\
--libdir=%{_libdir} --enable-efi --disable-qemu-traditional \
--with-extra-qemuU-configure-args="--enable-spice --enable-usb-redir"
(cd xen; make defconfig; sed -i 's/# CONFIG_LIVEPATCH is not set/
CONFIG_LIVEPATCH=y/g' .config; make oldconfig)
export XEN_DOMAIN=xen.crc.id.au
make %{?_smp_mflags} %{?efi_flags} dist
I'll note that 4.6, 4.7, and 4.10 do not fail in this fashion using almost the
same command set to build.
--
Steven Haigh
net...@crc.id.au https://www.crc.id.au
+61 (3) 9001 6090 0412 935 897
signature.asc
Description: This is a digitally signed message part.
___
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
Re: [Xen-devel] Unable to build staging-4.9 on RHEL6
>>> On 24.08.18 at 04:56, wrote: > When trying to build both xen and qemu-xen from the staging-4.9 > branches, I'm running into issues compiling. > > Errors start with: > > BUILDSTDERR: sse.c: In function 'simd_test': > BUILDSTDERR: sse.c:319: error: subscripted value is neither array nor > pointer That's the x86 insn emulator test harness afaict, which doesn't get built unless you explicitly ask for it. Why are you building it? It's well known that it requires a new enough compiler (and the bar will raise with AVX512 support, which is in the works). Jan ___ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
Re: [Xen-devel] Unable to build staging-4.9 on RHEL6
Cc Anthony
On Fri, Aug 24, 2018 at 12:56:49PM +1000, Steven Haigh wrote:
> Hi all,
>
> When trying to build both xen and qemu-xen from the staging-4.9 branches,
> I'm running into issues compiling.
>
> Errors start with:
>
> BUILDSTDERR: sse.c: In function 'simd_test':
> BUILDSTDERR: sse.c:319: error: subscripted value is neither array nor
> pointer
> BUILDSTDERR: sse.c:320: error: subscripted value is neither array nor
> pointer
> BUILDSTDERR: sse.c:324: error: subscripted value is neither array nor
> pointer
> BUILDSTDERR: sse.c:328: error: subscripted value is neither array nor
> pointer
> BUILDSTDERR: sse.c:334: error: invalid operands to binary == (have 'vec_t'
> and 'vec_t')
> BUILDSTDERR: sse.c:340: error: can't convert between vector values of
> different size
> BUILDSTDERR: sse.c:345: error: invalid operands to binary == (have 'vec_t'
> and 'vec_t')
> BUILDSTDERR: sse.c:368: error: invalid operands to binary == (have 'vec_t'
> and 'vec_t')
> BUILDSTDERR: sse.c:377: error: invalid operands to binary == (have 'vec_t'
> and 'vec_t')
> BUILDSTDERR: sse.c:380: error: invalid operands to binary == (have 'vec_t'
> and 'vec_t')
> BUILDSTDERR: sse.c:405: error: invalid operands to binary == (have 'float
> __vector__' and 'vec_t')
> BUILDSTDERR: sse.c:538: error: invalid operands to binary == (have 'vec_t'
> and 'vec_t')
> BUILDSTDERR: sse.c:555: error: invalid operands to binary == (have 'float
> __vector__' and 'vec_t')
> BUILDSTDERR: sse.c:569: error: invalid operands to binary == (have 'vec_t'
> and 'int')
> BUILDSTDERR: sse.c:645: error: subscripted value is neither array nor
> pointer
> BUILDSTDERR: sse.c:645: error: subscripted value is neither array nor
> pointer
> BUILDSTDERR: make[6]: *** [sse.bin] Error 1
> BUILDSTDERR: sse2.c: In function 'simd_test':
> BUILDSTDERR: sse2.c:319: error: subscripted value is neither array nor
> pointer
> BUILDSTDERR: sse2.c:320: error: subscripted value is neither array nor
> pointer
> BUILDSTDERR: sse2.c:324: error: subscripted value is neither array nor
> pointer
> BUILDSTDERR: sse2.c:328: error: subscripted value is neither array nor
> pointer
> BUILDSTDERR: sse2.c:334: error: invalid operands to binary == (have 'vec_t'
> and 'vec_t')
> BUILDSTDERR: sse2.c:340: error: can't convert between vector values of
> different size
> BUILDSTDERR: sse2.c:345: error: invalid operands to binary == (have 'vec_t'
> and 'vec_t')
> BUILDSTDERR: sse2.c:569: error: invalid operands to binary == (have 'vec_t'
> and 'int')
> BUILDSTDERR: sse2.c:645: error: subscripted value is neither array nor
> pointer
> BUILDSTDERR: sse2.c:645: error: subscripted value is neither array nor
> pointer
> BUILDSTDERR: sse2.c:651: error: invalid operands to binary > (have 'vec_t'
> and 'int')
> BUILDSTDERR: sse2.c:653: error: invalid operands to binary == (have 'vec_t'
> and 'vec_t')
> BUILDSTDERR: make[6]: *** [sse2.bin] Error 1
>
> This continues for sse4, sse-avx, sse2-avx, and sse4-avx.
>
> Right now, the code I'm using for this build is:
>
> git clone -n -b staging-4.9 git://xenbits.xen.org/xen.git .
> git checkout %{gitid}
> pushd tools
> git clone -b staging-4.9 git://xenbits.xen.org/qemu-xen.git
> popd
>
> gitid is currently set to: 6c9d139cdd0289f2b35b5deea4b41b8e3e1b39b7
>
> --
> Steven Haigh
>
> ? net...@crc.id.au ? http://www.crc.id.au
> ? +61 (3) 9001 6090? 0412 935 897
>
> ___
> Xen-devel mailing list
> Xen-devel@lists.xenproject.org
> https://lists.xenproject.org/mailman/listinfo/xen-devel
___
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
