OK, the problem did turn out was my sloppy git tree. Always clean up before you think you hit a bug :)
But I've got another question: when you specify a patch in a eb file and run the file, it doesn't look for the patch file in the directory of the eb file. It looks in the python tree. Is this intended behaviour? I think it would make sense to also look in the directory of the eb file. Should a write a patch for that? Or is this working as it is intended? Ward On Fri, Jul 12, 2013 at 5:41 PM, Ward Poelmans <[email protected]> wrote: > Hello all, > > I want to make a new eb for gcc that builds with the latest cloog and > ppl. The problem is that I need to apply a patch to ppl before > building in stage 2. And that's a problem (I think). Currently, the > sources of gcc, cloog, ppl, ... are all extracted in the same > directory and just before building in stage 2, the sources of cloog > and ppl are moved to in-tree. > > My question is, what is the best way to apply a patch to ppl? I think > there are 2 ways: > - I can add a patch_step to the gcc easyblock that reads that patches > and applies them according to prefix: ppl-* is applied to the ppl > tree, cloog-* is applied to the cloog tree. > - Currently, you can specify either a patch level or a prefix to a > patch in an easyconfig. This could be extended to allow both? This > would also solve my problem. A prefix alone is not enough for the > patch I want to apply. > > Does anyone have an opinion on which way to proceed? > > > Futher I have a small suggestion for the FAQ on github: if you have > cuda in your CPATH, C_INCLUDE_PATH or LIBRARY_PATH, you can get weird > gcc building errors. So, I think it's a good idea to unset those > variables prior to building gcc if you get any strange error. > > Ward -- ir. Ward Poelmans Center for Molecular Modeling Ghent University Technologiepark 903, B-9052 Zwijnaarde Belgium Tel: +32 9 264 65 76 Fax: +32 9 264 66 97 E-mail: [email protected] http://molmod.UGent.be/
