aserio changed the topic of #ste||ar to: STE||AR: Systems Technology, Emergent Parallelism, and Algorithm Research | stellar.cct.lsu.edu | HPX: A cure for performance impaired parallel applications | github.com/STEllAR-GROUP/hpx | Buildbot: http://rostam.cct.lsu.edu/ | Log: http://irclog.cct.lsu.edu/
parsa has quit [Quit: Zzzzzzzzzzzz]
parsa has joined #ste||ar
EverYoung has quit [Ping timeout: 246 seconds]
<github>
[hpx] hkaiser opened pull request #2849: Unify serialization of non-default-constructable types (master...fixing_2846) https://git.io/v5erw
patg has quit [Quit: This computer has gone to sleep]
bikineev has quit [Remote host closed the connection]
pree has joined #ste||ar
parsa has quit [Quit: Zzzzzzzzzzzz]
mcopik has joined #ste||ar
bikineev has joined #ste||ar
bikineev has quit [Remote host closed the connection]
bikineev has joined #ste||ar
hkaiser has joined #ste||ar
bikineev has quit [Read error: Connection reset by peer]
bikineev has joined #ste||ar
<pree>
Hi all. what minimum c++ version should hpx support ? Because I'm using some c++17 things like std::conjuction's etc. what if the user has compiler which supports upto c++11
<pree>
the build gets failed ?/
<hkaiser>
pree: in unguarded code, please stick to c++11
<pree>
Okay. Thanks
<pree>
unguared code ??
<pree>
hkaiser ^^
<hkaiser>
if you want to use features of c++14 or 17 place those code snippets inside #ifdef/#endif
<hkaiser>
best is to stick with c++11, though
<pree>
Okay I will try to stick with c++11.
<pree>
and some ifdef's if want to
<hkaiser>
pree: using #ifdef means you need two alternatives of the code, c++11 and a newer version - I think you shouldn't even think of this at this point
<pree>
okay
<hkaiser>
pree: I doubt you have a use case where you can't get away with c++11
<pree>
nothing special just for some code readabilty though
<hkaiser>
pree: having two versions does not increase readability, usually
<pree>
Okay I will stick to c++11,
<pree>
thanks
<pree>
I thought it will give readability without alternatives, now I'm okay
K-ballo has joined #ste||ar
bikineev has quit [Remote host closed the connection]
bikineev has joined #ste||ar
bikineev has quit [Remote host closed the connection]
pree has quit [Ping timeout: 246 seconds]
Rodario has joined #ste||ar
<Rodario>
Hi, smone here i could annoy with a question regarding the build process of hpx relly fast?
pree has joined #ste||ar
<zao>
I'm going to conjure up breakfast, but you can always try :)
<hkaiser>
zao: breakfast?
<jbjnr>
14:39 here. start the BBQ soon!
<hkaiser>
Rodario: ust ask, somebody will answer
<zao>
hkaiser: Sat up a bit too long last night to try to tease out my CPU bugs with HPX :)
<zao>
Didn't learn much, except that if you build it under the Windows Subsystem for Linux, compiler processes apparently do not want to touch swap.
<hkaiser>
zao: almost like in the US, something wrong - the russians!
<hkaiser>
zao: for you - something wrong - HPX!
<hkaiser>
;)
<Rodario>
allrighty, currently my build dies with error msg referring to undefined refrences. I realized then that while using cmake i get a msg saying: "failed to create symbolic link <root_path>/hpx_main/hpx/build/share/hpx': No such file or directory"
<zao>
It's a good load on a system :)
<hkaiser>
Rodario: that one is benign, you can safely ignore it
<hkaiser>
note to self - find a way to avoid this warning
<Rodario>
huh ... bummer. I hoped this was the problem crashing the build :D
<zao>
Do you have some background on what kind of environment you're building in, and what are the missing symbols and for what binary?
<Rodario>
the first one is: numa_domains.cpp:(.text+0x9c): undefined reference to `hpx::get_runtime()
<hkaiser>
rodario can you give me the output of cmake as well, please?
<hkaiser>
including command line, pls
<hkaiser>
also, you did not give me the full build logs, nor the errors generated
<zao>
(did you know that machines don't boot without RAM?)
<Rodario>
command line for cmake would be: cmake -DHPX_WITH_CXX14=ON VERBOSE=1 ..
<Rodario>
or do I miss something here
<hkaiser>
VERBOSE=1 is needed for make only, the HPX_WITH_CXX14=On goes onto the cmake command line
<hkaiser>
zao: they tend to squirm without RAM, yah
<Rodario>
allright, i posted the verbose output, the error msg. that comes after it is bigger than my terminal can scroll. How to post all of that? I am rather novice concerning terminal usage ...
vamatya has joined #ste||ar
<zao>
Typically, you can glue on 2>&1
<zao>
Typically, you can glue on 2>&1 | tee -a some-log-file
<zao>
(silly enter key)
<zao>
Merges stderr into stdout, and pipes it into tee, which shows the output to screen and also appends it into the file mentioned.
<zao>
You can then drag the file into a gist, or otherwise share it.
<Rodario>
Cool stuff. Now to get through those 16 764 lines of error...
<K-ballo>
Rodario: could you find out which flags you are using?
<Rodario>
flags for cmake?
<Rodario>
like: -DHPX_WITH_CXX14=ON
<Rodario>
?
<zao>
For a /usr/bin/c++ invocation.
<zao>
Like the one I linked above, with make VERBOSE=1
<K-ballo>
you may need to force a rebuild, you may pass -B to make
<zao>
or delete some object file, like src/CMakeFiles/hpx.dir/util/batch_environment.cpp.o
<K-ballo>
much easier to do that, yes
<Rodario>
an then use make with VERBOSE=1 again?
<zao>
Right.
<Rodario>
make VERBOSE=1 -j3
<Rodario>
but wasnt this the way I created the last gist?
<K-ballo>
for the last gist when make was run all translation units had already been compiled, so it only shows the attempt to link all those object files into a library
<K-ballo>
deleting one of those object files will result in make running the corresponding compilation step for that translation unit, and revealing the flags used for compilation