[08:23] <david3> hi i have a question about a mistake i made on bugs.launchpad.net, can anybody help me?
[09:12] <cjwatson> hggdh: done
[09:23] <jochensp> Hi, I get "virtual memory exhausted: Cannot allocate memory" when trying to compile on PPA, any way to increase the limit?
[09:32] <cjwatson> jochensp: Only for the pool as a whole.  Which build is this?
[09:33] <cjwatson> PPA builders have 4 GiB of RAM per guest, which generally seems enough for any sensible build ...
[09:34] <cjwatson> david3: helps to say what the mistake was :-)
[09:53] <jochensp> cjwatson: https://launchpad.net/~v-launchpad-jochen-sprickerhof-de/+archive/ubuntu/pcl/+build/6366005/+files/buildlog_ubuntu-trusty-amd64.pcl-1.7_1.7.2-1%2Btrusty4_FAILEDTOBUILD.txt.gz
[09:58] <cjwatson> jochensp: the compiler rather than the linker; that's novel, though I suppose that's also C++ ... can you find out roughly how much memory that process takes, e.g. by compiling on a different system and watching it in top?
[09:58] <cjwatson> I don't know if we'll be able to do anything about the limit, but we should at least find out how far short we are
[09:58] <cjwatson> also it would be worth experimenting to see if different optimisation levels and such bring it within 4GiB
[10:06] <jochensp> cjwatson: will do after lunch
[10:46] <wgrant> cjwatson, jochensp: There's also the issue that something needing more than 4GiB of VM will never be able to build on 32-bit architectures.
[11:19] <jochensp> wgrant: only zhe amd64 build fails
[11:20] <wgrant> Ah
[11:32] <david3> well, i wanted to subscribe to a bug, but i clicked on the wrong button (set information type to: Public -> Public Security), i immediately undid my changes, but the log of the change is still in the     │ pgraner
[11:32] <david3>                   | description. Can i somehow remove my changes from the log?
[11:33] <wgrant> david3: It's not possible to remove items from the activity log. They're not doing any damage.
[11:37] <david3> thank you, ok, i just didn't want to appear in a public log as a total noob ;)
[13:10] <sergio-br2> hey
[13:11] <sergio-br2> i'm trying to compile a package with gcc 4.8 in utopic, and it has a -fstack-protector-strong parameter
[13:11] <sergio-br2> but this parameter was added only in gcc 4.9, right?
[13:11] <sergio-br2> x86_64-linux-gnu-g++-4.8: error: unrecognized command line option '-fstack-protector-strong'
[13:13] <sergio-br2> https://launchpadlibrarian.net/184914518/buildlog_ubuntu-utopic-amd64.dinothawr_1.0%2Br379~6~ubuntu14.10.1_FAILEDTOBUILD.txt.gz
[13:29] <dobey> sergio-br2: well, you can't use options only availabile in >= 4.9, with 4.8
[13:29] <sergio-br2> ok
[13:30] <sergio-br2> but that option is automatically
[13:30] <dobey> automatically from where?
[13:30] <sergio-br2> do i have to force with -fstack-protector --param=ssp-buffer-size=4 ?
[13:31] <sergio-br2> i didn't override the dh_auto_build in the rules
[13:31] <dobey> sergio-br2: you should probably ask in #ubuntu-devel about the default compiler options in ubuntu. launchpad doesn't pick them
[13:31] <sergio-br2> hum, ok
[13:32] <dobey> so if those are the default options for 4.9 and are being applied when using 4.8, then either you need to do something extra, or there's a bug in debhelper maybe