Add libelf + libdwarf #1283
Add libelf + libdwarf #1283
Conversation
|
Test PASSed. |
|
Test report by @wpoely86 |
|
Test PASSed. |
|
Test PASSed. |
|
Ready, I think. It uses the dummy toolchain because I needed this for PerfExpert (#839). |
|
Test PASSed. |
1 similar comment
|
Test PASSed. |
|
@wpoely86: not a big fan of merging in easyconfigs that use the That's also one of the reasons why #839 hasn't made it in yet. The real solution here would be to i) build with a non-dummy toolchain (e.g. GCC), ii) assure the resulting build is toolchain-neutral (see easybuilders/easybuild-framework#570) and avoid using the toolchain label in the resulting module name. So, please revamp these to use a GCC-only toolchain? |
* develop: add easyconfigs for IMB with different toolchains remove faulty 'easyblock = ConfigureMake' line from HPL easyconfig add easyconfig file for EasyBuild v1.16.1 fix deprecated fallback to ConfigureMake easyblock in HPL easyconfig add easyconfig file for EasyBuild v1.16.0 add easyconfig for HPL 2.1 with intel/2015a add easyconfig file for intel/2015a
|
Test report by @wpoely86 |
|
Test FAILed. |
|
Test FAILed. |
|
Test PASSed. |
|
@boegel done |
|
Test report by @wpoely86 |
| configopts = "--enable-shared " | ||
|
|
||
| # This is dirty but libdwarf cannot find it's own library in the build process... | ||
| prebuildopts = ' LD_LIBRARY_PATH="../libdwarf:$LD_LIBRARY_PATH" ' |
There was a problem hiding this comment.
The build process is also a bit non standard 😉
It's just a weird library. It correctly finds it's own library for the linking, but it also tries to run a binary to generate other stuff to compile, and there it fails.
There was a problem hiding this comment.
Yeah, well, at least you're making clear why it's needed, and I've been worse. ;-)
|
Test report by @boegel |
|
Test PASSed. |
|
Test report by @boegel |
|
Looking great now, thanks @wpoely86, going in. |
Should clean this up when I find the time...