<div dir="ltr"><div>Well, I already created the schroot environment following your kind instructions.</div><div><br></div><div>However... 'make' failed again!!! cppunittest again...<br></div><div><br></div><div>My
hope is that maybe I didn't interpret correctly the changes that you
made on the sal/Module_sal.mk file (for this test I'm not using git, but
the xz sources downloaded). Could you please paste here the actual
contents of that file?</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">El mié., 14 ago. 2019 a las 14:44, Michael Weghorn (<<a href="mailto:m.weghorn@posteo.de">m.weghorn@posteo.de</a>>) escribió:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 14/08/2019 19.21, <a href="mailto:dreamnext@gmail.com" target="_blank">dreamnext@gmail.com</a> wrote:<br>
> Would be possible to download your generated deb files from some<br>
> file-sharing service?<br>
<br>
If necessary, I'll probably find a way to upload them somewhere next<br>
week. (I'll be away for the next days.) However, that won't help in the<br>
long run, so I'll think it'd be better if you can get your build setup<br>
working.<br>
<br>
> <br>
> I'm still struggling with compilation issues.<br>
> 1) After the bad experience with Debian 10, I downloaded Debian 9.9 in<br>
> the hope that would make a better compilation choice, but, alas, Debian<br>
> 9 includes a version of gcc already unsupported by LibreOffice, it<br>
> requires at least gcc 7. As far as I could found, upgrading gcc on<br>
> Debian 9 is an ugly chore, so I went back to installing Debian 10...<br>
> 2) But, this time, instead of choosing LXQT, I chose LXDE and used<br>
> LXTerminal. Now it compiled until the make error without a single hang.<br>
> I don't know if LXQT of tis default terminal were the culprits of the<br>
> frequent crashes, or something else, but at least I reached the make<br>
> error on Debian 10.<br>
> <br>
> I paste the error produced in Debian 10. It seems to be still cpunittest<br>
> related.<br>
> <br>
> Would be wise to apply your diff here, or it is not related since I'm<br>
> not running a chroot environment but a VM?<br>
<br>
The diff wouldn't help, since the tests that fail for you are unrelated<br>
to the ones I temporarily disabled.<br>
<br>
Maybe you want to try setting up an i386 chroot on an amd64 host as<br>
well? That might work better than using a i386 virtual machine (e.g.<br>
with regard to memory limitations) and I guess this should also work<br>
just fine on a host running Escuelas Linux.<br>
<br>
The steps I took to set up the chroot for use with schroot were roughly:<br>
<br>
Create chroot:<br>
<br>
sudo debootstrap --arch=i386 buster /some/path/to/chroot/buster-i386<br>
<br>
Create entry in /etc/schroot/schroot.conf:<br>
<br>
[buster-i386]<br>
description=Debian buster (stable) 32-bit<br>
directory=/some/path/to/chroot/buster-i386<br>
users=<your_username><br>
root-users=<your_username><br>
personality=linux32<br>
<br>
After that, you can change into the chroot using<br>
<br>
schroot -c buster-i386<br>
<br>
or (to work as root):<br>
<br>
schroot -c buster-i386 -u root<br>
<br>
and then set up the build dependencies, clone LibreOffice and build from<br>
there as usual.<br>
<br>
</blockquote></div>