27 Apr
2020
27 Apr
'20
5:05 p.m.
On Monday 27 of April 2020 18:09:49 deloptes wrote:
Michele Calgaro via trinity-devel wrote:
I build on several different builders. All are virtual machines in KVM,
where some hosts are Intel processor, some AMD processor, one POWER9
processor. The number of cores I have set to 6, 8, 16, 24, 32, 40. So I
dare say that I am testing the parallel build quite intensely. And I do
not notice problems with building tdelibs.
Note: Now I use sbuild with schroot.
Cheers
--
Slávek
Hi Emanoil,
not sure what you are doing wrong, all we can say is that we can build
R14.0.8 for all supported debian distros (Slavek) and R14.1.0-dev for
bullseye and it works. Slavek and I use different scripts and build
method, just as extra info. That points to some sort of problem on
your side. - src code?
- building scripts?
- building environment?
- others?
Hi Michele, all,
the problem does not occur when passing -j1 to debuild.
I could not test your scripts, because of pbuilder, which I do not use.
But -j1 seems to be now mandatory for tdelibs and tdebase.
How are you running debuild with -j1 or with -j4?
For me it is interesting to understand if it is i.e. CPU specific - I
run it on AMD or similar.
I have a note regarding tqca-tls, which also required -j1. Not sure if
this still holds, but it seems from time to time it has a problem with
-j > 1
thank you and regards