<zao>
Does this failure ring any bells? `multiple definition of 'hpx::force_linking()`
<zao>
Let's pave the build dir and see.
<zao>
Clean build did the trick. Got to love CMake.
<zao>
(cleaned dir, that is, just a clean did nada)
<zao>
I'm looking briefly at the problem the person mailed hpx-users about with PAPI. If I haven't built "components", it will give the kind of error they showed.
<zao>
`runtime_support::load_components: command line processing: unrecognised option '--hpx:papi-event-info=all'`
<zao>
If I build "components" first, I get a nice fat segfault out of `bin/hello_world_2 --hpx:papi-event-info=all`
<nikunj>
should you need any help from my side, please let me know
<hkaiser>
well, I think Rod will be in contact wrt FLeCSI
<nikunj>
yes I'm doing FlecSi work these days, just learnt a thing or two about dockers and now trying building and FlecSi
<nikunj>
also, I've booked flight tickets. 24th Nov - 11th Jan
<nikunj>
hkaiser: could you send a letter of invitation for the above mentioned dates just like you did for summers? I will need it to apply for a NOC
<hkaiser>
nikunj: do you still hav ethat letter we sent last time?
<nikunj>
yes I do
<nikunj>
should I email that back to you?
<hkaiser>
yes, pls
<nikunj>
email sent
<hkaiser>
nikunj: ok, we'll send another one
weilewei has joined #ste||ar
hkaiser has quit [Ping timeout: 250 seconds]
weilewei has quit [Remote host closed the connection]
<diehlpk_work>
nikunj, CCgrid deadline is December 12th
<diehlpk_work>
tianyi93, Prepares a paper for this event
akheir has quit [Remote host closed the connection]
rori has quit [Quit: WeeChat 1.9.1]
maxwellr96 has joined #ste||ar
<heller>
jbjnr: simbergm: any news?
<simbergm>
heller I think we'll know only on Monday...
jaafar has quit [Ping timeout: 240 seconds]
<heller>
simbergm: alright
jbjnr_ has joined #ste||ar
<jbjnr_>
heller:we will hear a final decision on monday about the course, but today nobody registered after the final reminder about the course, so it's very probable the course is cancelled.
<zao>
It's weird. --hpx:help doesn't list the PAPI options, then when I run in a debugger the options processing runs twice, once earlier and once in a late HPX thread.
<zao>
The second time it kind of considers --hpx:papi-event-info an unrecognized option, but also not one.
aserio has joined #ste||ar
<zao>
Gah, I have no idea how this is supposed to work and GDB isn't helping much :D
aserio has quit [Ping timeout: 250 seconds]
aserio has joined #ste||ar
<hkaiser>
zao: yah, command line processing runs twice
<hkaiser>
once right away and once after all plugins were loaded
<zao>
Not sure how many times it has run now, but it takes its fair time getting there.
<zao>
In any way, at the point it blows up towards the end, there's a whole "unrecognized command line", but none of the options are considered unrecognized.
<hkaiser>
zao: ok, I'm planning to have a look
<zao>
So for sanity's sake... what do I need to actually use PAPI? Is there some specific build step for a target to use it, or can I use --hpx:papi-* with any target?
<zao>
I'm using hello_world_2 for now, as-is.
<zao>
Shouldn't blow up regardless, of course, just wondering.
<hkaiser>
true
<hkaiser>
you should be able to use it with --hpx:print-counter=<some papi counter name>