<
hkaiser>
looks better now, much easier to grasp
<
zao>
How amazing, I managed to compile an example snippet from the quickstart guide.
K-ballo has quit [Quit: K-ballo]
<
zao>
This might be of interest to you people.
<
zao>
Tool that takes Clang 9 -ftime-trace info from each TU and computes some stats across the codebase.
<
hkaiser>
zao: cool!
hkaiser has quit [Ping timeout: 240 seconds]
weilewei84 has joined #ste||ar
nikunj has quit [Read error: Connection reset by peer]
nikunj has joined #ste||ar
jbjnr has joined #ste||ar
weilewei84 has quit [Remote host closed the connection]
weilewei has quit [Remote host closed the connection]
nikunj has quit [Ping timeout: 240 seconds]
jbjnr has quit [Quit: WeeChat 2.5]
K-ballo has joined #ste||ar
Coldblackice has joined #ste||ar
Coldblackice has quit [Client Quit]
nikunj has joined #ste||ar
Coldblackice has joined #ste||ar
Coldblackice has quit [Client Quit]
Coldblackice has joined #ste||ar
nikunj has quit [Ping timeout: 265 seconds]
Coldblackice has quit []
Coldblackice has joined #ste||ar
hkaiser has joined #ste||ar
weilewei has joined #ste||ar
<
K-ballo>
I was aware of it, but did not know it had already made it!
<
weilewei>
Any idea what causes in __static_initialization_and_destruction_0, undefined reference to `hpx::util::agas_logger()' ?
<
hkaiser>
weilewei: logging disabled/enabled mismatch?
<
hkaiser>
weilewei: looks very strnage to me - some kind of configuration mismatch perhaps - different c++ abis, stale binaries somehwere, etc.
<
weilewei>
hmm, maybe, so I need to find out all the places that he enabled/disabled logging?
<
weilewei>
for the term stale binaries, how should I understand this?
<
weilewei>
But I already comment out all the #includes that lead hpx logging
<
weilewei>
I built a binary with hpx logging before, but I cleaned up hpx install and the application build folder...
<
weilewei>
Also, I make sure that -std=c++14 is set
K-ballo has quit [Quit: K-ballo]
K-ballo has joined #ste||ar