16:15 < askhl> tototo: I understood that it uses MKL, which is the spawn of the devil itself. Try to follow the standard instructions for linking to MKL, so it will (hopefully) find both the fake FFTW impostor and the fake FFTW-MPI impostor. Once libvdwxc is compiled correctly it should not be difficult to link from GPAW. 16:16 < tototo> hope so :) I have a second account that I'm not too scared of messing around with 16:17 < tototo> I did a git clone of the libvdwxc repo 16:17 < askhl> please pastebin your GPAW customize.py. That should tell you all the necessary libraries 16:18 < askhl> Basically we need: 16:18 < tototo> http://pastebin.com/Kjs76zJz 16:18 < askhl> The include_dirs, library_dirs, and libraries. 16:23 < askhl> I would put the include_dirs as FFTW_INCLUDES, the libraries as FFTW_LIBS, and you can put the MKL library dir as LT_SYS_LIBRARY_PATH or LDFLAGS (the latter might be more appropriate if you use modules which set LD_LIBRARY_PATH as is often the case) 16:23 < askhl> These environment variables are mentioned by ./configure --help 16:24 < askhl> What I usually do is to create a file called reconfigure. which exports any variables necessary, and then calls ./configure [options] 16:26 < tototo> I'm assuming this is in the libvdwxc directory? 16:27 < tototo> hah, ./configure doesn't work for the git repo 16:27 < askhl> Yes, you got the source right? Now find the configure file. (If you got the dev version you need autoreconf -i to generate the configure file) 16:27 < tototo> but does for the wget'ed tar 16:27 < tototo> yep now I see the ./configure --help 16:29 < tototo> what's the syntax for the reconfigure file? 16:29 < askhl> it's just a shellscript which runs configure. You can use any language/syntax 16:30 < askhl> That's just what I normally do 16:30 < tototo> so just normal bash EXPORT etc? 16:30 < askhl> (since I don't want hte compile command to be lost in the bash history) 16:30 < askhl> yes 16:30 < tototo> ok 16:32 < tototo> if there are multiple libraries in the "libraries = ['a', 'b', ...] syntax, is there a handy syntax to export a "list"? 16:32 < tototo> or does it just take the same [ ] 16:33 -!- tototo [~tomasusi@imacsusi.pnm.univie.ac.at] has quit [Quit: Lost terminal] 16:34 < askhl> hmm 16:34 -!- tototo [~tomasusi@imacsusi.pnm.univie.ac.at] has joined #gpaw 16:34 < tototo> lol, terminal crashed :D 16:34 < askhl> colon-separated list 16:34 < askhl> like $PATH 16:36 < tototo> could you re-paste the message with which customize.py items should be exported as which for the reconfigure? 16:38 < askhl> http://dcwww.camd.dtu.dk/~askhl/files/snippet.txt 16:39 < tototo> thanks 16:40 -!- tototo [~tomasusi@imacsusi.pnm.univie.ac.at] has quit [Quit: Lost terminal] 16:41 -!- tototo [~tomasusi@imacsusi.pnm.univie.ac.at] has joined #gpaw 16:41 < askhl> http://dcwww.camd.dtu.dk/~askhl/files/snippet.txt