just plopped a self-built monerod into the xmrchain.net box.

hey guys! when next hardfork is gonna happen?

Unknown.

thanks

not this month or next, cetainly

does anyone know how much space reproducible builds take up?

whats the thing we used before to collaborate on a statement?

or announcement or whatever

including the downloaded dependencies

gingeropolous: we can set a date once we know how long the CLSAG audit takes

well i think the general shift should be discussed. we don't need a hard date. I think the idea I've seen is to maintain a 6 month release schedule, with the possibility of a fork occurring at those releases

so any given 6 month date will either be a point release, or a major release

if there was ever any agreement that major release numbers related to consensus changes

i forget if that was the case.

because we've got a lot of people trained up on "ooh, its been six month, must be something going on"

they start seeing the seasons change, smell the air, days start drastically shifting duration, and they start thinkin there must be a fork a'coming

I think my gitian tree is using about 12GB

ty

I'm not sure that that includes the space the docker containers themselves need

seems to me that docker is storing those centrally, not in my gitianuser's home directory

hyc: regarding macOS SDK, do I have to extract it?

depends says extract, the other link says don’t

ok looks like I don’t have to extract it

gitian script does it for me

indeed

ok, started the build process now :D

scoobybejesus: are you also going to build the reproducible builds? the more the better :)

oh... probably... :) (i'm busy but will try to get it going real quick.. hopefully it cooperates)

no hurry, I guess we will wait a few days before release anyway

because we also have to build GUI

Looks like gcc got upgraded today from 7.4.0 to 7.5.0 in Ubuntu 18.04.

I'll rebuild.

yep I’m currently using 7.5

> cc1plus: out of memory allocating 65536 bytes after a total of 121749504 bytes

So close...

i686 ?

`./gitian-build.py --docker -j 4 --memory 6000 --detach-sign --no-commit --build selsta v0.15.0.5`

should be ok for 8GB ram and 4 cores?

-j4 for 8GB is really pushing it.

i think some of the bigger files get upset with that

ok back to j2 lol

3 might work if you don't get wallet2 and core_rpc_server at the same time :)

Which build ? Linux i686 or Win i686 ?

I use -j6 with -m10000.

I think i686-linux-gnu

but not sure where I can see that

builder/var/build.log

the last lines

I see both i686-linux-gnu and x86_64-linux-gnu

It's probably wallet2. My build will reach i686-linux-gnu soon and we'll see.

can I simply restart?

Arrow up, enter :)

ok, I changed the -j4 to -j2

and enter :D

But since it didn't finish, it will probably start building deps again.

looks like it

> Memory usage: 274.5M out of 7.8G

seems suspiciously low, but maybe it will rise once it builds monero

I don't think it's memory.

that’s what my VM says

No, I mean it's a typical error for i686 builds of wallet2. Always on the edge of passing or failing.

ah ok

guess turning down the jobs can’t hurt

Hmm, looks like it's x86_64-linux-gnu after all.

My build completed that one.

my host has 16GB ram and 4 cores, my VM has 8GB and 4 cores, should be ok?

You give 6000 MB to docker.

-j6 with -m10000 works here.

so far so good? paste.debian.net/1134370

We'll see when my Linux build completes. Buids built with gcc 7.4.0 don't match.

TheCharlatan hashes matched with yours iDunk, I asked him about GCC version

My Linux gcc 7.5.0 build match scoobybejesus'.

Bummer that a part of the toolchain got upgraded right after release.

mine was still on 7.4 ... annoying. So lets all rebuild and bump to 7.5?

Any new build will be with 7.5.0, so might as well rebuild.

fingers crossed we're good to go. here's the whole thing: paste.debian.net/1134389

ok I’m close to the point where it failed previously

no crash :)