IRC Logs for #crux-devel Monday, 2016-11-21

Romsteryou may want to fix your clang port teK__01:50
Romstersince you changed llvm you broke clang. revdep -vvv clang01:51
Romsterthe dynlib options need to be the same for clang01:51
*** onodera has quit IRC02:17
*** marius has joined #crux-devel03:36
*** mavrick61 has quit IRC03:49
*** mavrick61 has joined #crux-devel03:50
*** marius has quit IRC04:19
*** frieda has joined #crux-devel04:25
*** frieda has quit IRC04:28
teK__fired the rebuild yesterday before going to bed09:51
teK__I expect a rebuild is required for clang to work again09:52
teK__more: soon09:52
Romsterjust making sure you seen the problem09:54
teK__I did, thanks09:55
*** onodera has joined #crux-devel11:16
*** onodera has quit IRC11:27
*** onodera has joined #crux-devel12:19
*** heroux has quit IRC12:31
*** heroux has joined #crux-devel12:32
teK__Romster: is in llvm's footprint and also in the newly package from just now12:49
*** onodera has quit IRC13:25
*** onodera has joined #crux-devel14:06
*** onodera has quit IRC16:32
*** onodera has joined #crux-devel16:32
jaegerWhat's the process for updating compat-32.git in 3.3? merge 3.2 into 3.3 then update signatures recursively?18:33
jaeger(specifically for pulling 3.2 updates, I don't mean for individual ports)18:49
Romsteri was gonna wait for the last day of release as getting compat-32 up wont take much effort21:15
Romsterdid you even push them commits teK__ i don't see them in ports -u21:20
teK__none required?21:46
teK__hm, now its also broken on my test system21:48
teK__well well. Not today.21:48

Generated by 2.14.0 by Marius Gedminas - find it at!