Package build problem on trusty

Hello

In the log you've shared I can see DEB_BUILD_OPTIONS taking a 4 parallel jobs config, you could try running this with a lower level of concurrency.

How can I decrease parallel jobs? Add it with 'rules' file to env DEB_BUILD_OPTIONS variable?

One more try with changing 'rules' file. Currently it contains such lines:

--- rules ---
#!/usr/bin/make -f
#export DH_VERBOSE=1

export DEB_BUILD_MAINT_OPTIONS=hardening=+all,parallel=2

include /usr/share/dpkg/architecture.mk

export DEB_CXXFLAGS_MAINT_APPEND=-Wall -pedantic
export DEB_LDFLAGS_MAINT_APPEND=

%:
        dh $@ --parallel

override_dh_auto_install:
--- end ---

Result: https://launchpad.net/~purplei2p/+archive/ubuntu/i2pd/+build/24308472
Still no luck.

You set it in your debian/rules file.

What you're sharing here is the setting of DEB_BUILD_MAINT_OPTIONS and not DEB_BUILD_OPTIONS. And you can see in the buildlog you shared (https://launchpad.net/~purplei2p/+archive/ubuntu/i2pd/+build/24308472) that DEB_BUILD_OPTIONS is still DEB_BUILD_OPTIONS=parallel=4 and expands to: make -j4 (see "dh_auto_build: make -j4 returned exit code 2" towards the end of the log).

That's why I'm asking how to override, because DEB_BUILD_OPTIONS make same thing:

---rules---
#!/usr/bin/make -f
#export DH_VERBOSE=1

export DEB_BUILD_OPTIONS=parallel=2
export DEB_BUILD_MAINT_OPTIONS=hardening=+all

include /usr/share/dpkg/architecture.mk

export DEB_CXXFLAGS_MAINT_APPEND=-Wall -pedantic
export DEB_LDFLAGS_MAINT_APPEND=

%:
        dh $@ --parallel

override_dh_auto_install:
---end---

https://launchpad.net/~purplei2p/+archive/ubuntu/i2pd/+build/24318867

Even with parallel=1: https://launchpad.net/~purplei2p/+archive/ubuntu/i2pd/+build/24318914

We are unable to help much with debugging your specific build. So you will have to try and figure this out on your own. My colleague mentioned that their guess is that the source package contains a gigantic source file that makes the compiler use lots of memory or that maybe it's a compiler bug.

> At first time I found that trusty chroots looks like have decreased virtual memory size

It is definitely not true that trusty builds have reduced virtual memory compared to other series.

Since this issue is happening only on i386, it could be that the build is trying to use more than 4GiB of virtual memory, which isn't possible on the 32-bit i386 architecture. Parallelism may not have anything to do with this issue. So you could consider disabling i386 builds for this package, if you do not have any actual users on i386.