Trouble with new lo-build

[Christian Lohmaier]

Hi Jürgen, *,

On Thu, Jul 3, 2025 at 12:08 PM Juergen Funk <j-funk at outlook.de> wrote:
>
> > you could use both wsl1 and wsl2, no nested acceleration features
> > necessary to build LO (but are nice if you need ipv6 networking from
> > the wsl host or similar) - the vast majority of the build is run
> > completely on the windows side. you only need the wsl container to run
> > configure (LO's own and of some externals) and run flex, bison, nasm
> > gperf, zip (and if building with translations msgfmt & msguniq) –
> > stuff that's only used a handful of times..
>
> When i try to install with wsl --install
> i get the error (sorry is in german)
> Herunterladen: Ubuntu
> Wird installiert: Ubuntu
> WSL2 wird von Ihrer aktuellen Computerkonfiguration nicht unterstützt.

Sorry if I wasn't clear - the no nested acceleration was tied to using
wsl1 to build, so wsl2 indeed needs nested virtualization, so using
wsl2 only works if it is enabled in the Host (or in the case of
bare-metal os: if it is enabled in Bios) -
https://learn.microsoft.com/en-us/windows/wsl/faq#can-i-run-wsl-2-in-a-virtual-machine-
explains how to enable nested virtualization in a suitable host.

> Aktivieren Sie die optionale Komponente "Plattform für virtuelle Computer", und stellen Sie sicher, dass die Virtualisierung im BIOS aktiviert ist.
> Aktivieren Sie "Plattform für virtuelle Computer", indem Sie ": wsl.exe --install --no-distribution
> " ausführen. Weitere Informationen finden Sie unter https://aka.ms/enablevirtualization
> Fehlercode: Wsl/InstallDistro/Service/RegisterDistro/CreateVm/HCS/HCS_E_HYPERV_NOT_INSTALLED
> Aktivieren Sie "Plattform für virtuelle Computer", indem Sie ": wsl.exe --install --no-distribution <- not slove the problem

Yeah, the Plattform für virtualle Computer is the "Virtual Machine
Platform", a subcomponent of hyper-V
https://learn.microsoft.com/en-us/windows/wsl/faq#does-wsl-2-use-hyper-v-

> The main problem is, it need the Hypervisor but it run in Hyper-V and in this case need the nested virtualisation.

wsl2 does, but wsl1 does not.

you can change the wsl version with "wsl --set-default-version 1" And
not sure whether it is needed since it has been so long since I
installed a container: wsl's --install command also has a
--enable-wsl1 command (that switch should install the "Windows
Subsystem for Linux" windows feature

> Maybe try again and set a new environment under Windows 11 as host, after Microsoft the nested virtualization should then be activatable

Again shouldn't really be necessary.
A method that should work is the following:
wsl --install --enable-wsl1 --no-distribution
→ that should install wsl itself and also make sure that the wsl1
stuff is enabled/available but skip attempts to install the default
distro
wsl --set-default-version 1
→ set the type of new distro-installations to be wsl1
wsl --install distributionname
→ install the desired distro, omit to install the default

> > lode/instructions use junit 4.10 for simplicity, since that contains
> > both files, and the vulnerabilities it has are of no interest for CI
> > or when building (only) LibreOffice.
> > Since you already specify separate jars, you could use a more current
> > junit that doesn't have the related vulnerabilities.
> Is it sufficient if i only use junit 4.12?

Only: no. Junit 4.12 doesn't contain hamcrest anymore, so if using
anything newer than junit 4.10 you need to use both, if using 4.10 you
don't need the extra hamcrest.

> > So what do you mean with "the confuse output it is the same without
> > color" - so even in a "confused" = mixed result you don't get actual
> > color but the color control characters are printed to the screen
> > instead?
>
> When you look to the starting Email here, you can see the mixed output,
> the call was /opt/lo/bin/make gb_COLOR=1

It didn't say that this was the case, but that explains - apparently
cygwin is buggy and that is why it is not enabled by default.

> but when call /opt/lo/bin/make
> then is not with color but the output the same (without the color control characters)

Not sure what you mean the same - if it is without the color control
characters, then it should just be default text color on default
background, and no garbled output should happen.

>
> I think maybe the problem is that this build system runs in Hyper-V

I doubt the garbled color output has anything to do with hyper-v/the
machine being a VM

ciao
Christian