|
01:13
FROGGS_ joined
02:22
colomon joined
07:09
domidumont joined
07:13
domidumont joined
07:37
zakharyas joined
08:06
Ven_ joined
|
|||
| nebuchadnezzar | I don't know if someone is interested in some build warnings of MoarVM for 2016.07 (qa.debian.org/bls/packages/m/moarvm.html) ? | 08:26 | |
|
10:15
Ven_ joined
|
|||
| arnsholt | nebuchadnezzar: The dyncall ones are in budled 3rd party code, so probably won't be fixed (unless they're actually bugs) | 11:15 | |
| The last one is in Moar code though | 11:16 | ||
| jnthn wonders if that last one is the pthreads_yield thing | 11:26 | ||
| iirc the last attempt to fix that resulted in the current warning becoming a failure in various places, so tread carefully :) | |||
| nwc10 | git blame for the the relevant lines usually helps | 11:28 | |
| arnsholt | jnthn: Don't you mean... thread carefully? | 11:34 | |
|
11:42
Ven_ joined
|
|||
| jnthn | :P | 11:44 | |
|
11:50
dalek joined
13:30
brrt joined
|
|||
| brrt | hey #moarvm | 13:31 | |
| nwc10 | good *, brrt | ||
| brrt | just 2c: that warning comes from the fact that wherever _phtread_yield() is called _GNU_SOURCE must be defined and it isn't | ||
| the cheap fix is to add -D_GNU_SOURCE=1 to the Makefile flags for affected platforms, however there are a bunch of places where _GNU_SOURCE is already predefined | |||
| nwc10 | I think that bit of knowledge is worth more than 2c :-) | 13:32 | |
| brrt | i didn't fix it last time i encountered it because i wasn't 100% sure which would be best; either to add it wherever pthread_yield is called or to remove it from wherever it is defined and deifne it in a global place | 13:33 | |
| and i was lazy at the time | 13:34 | ||
|
14:19
brrt joined
15:08
Ven_ joined
15:23
Ven_ joined
16:00
zakharyas joined
16:55
FROGGS joined
17:12
domidumont joined
19:01
brrt joined
21:37
mst joined
|
|||