Dear Alan, Thank you very much indeed for your detailed answers.
> On 19 Oct 2018, at 10:25, Alan O'Cais <[email protected]> wrote: > > Hi Jakob, > > It is always possible to shadow the LiBTIFF at GCCcore with another LibTIFF > in the intel toolchain (so that you only use the intel toolchain version when > you need to). I will try doing just that. > That this is not an issue for other people though makes me wonder if > something else is not the source of the problem. I am not sure if this is an issue for other people. I am not using a public easyconfig, but am making a new one, perhaps nobody are building Python extensions with the intel toolchain that links LibTIFF. With all toolchains prior to 2018b there were separate LibTIFF libraries for intel and foss toolchains. I could try to upload my stuff as a WIP pull-request so others can test if this is a general problem. In that case we may need to go back to two different LibTIFF builds. > A bit of googling tells me that this may actually be a bug in the gold linker > https://bugzilla.redhat.com/show_bug.cgi?id=1458003 . Does your site config > ignore binutils as a dep? If you add a build dep on binutils 2.31.1 maybe the > bug goes away...try adding > builddependencies = [('binutils', '2.31.1', '', True)] > to your LibTIFF easyconfig. When I load intel/2018b then binutils/2.30-GCCcore-7.3.0 is loaded. I tried adding the line to the Pillow easyconfig, but I still get the same linkage error. > Sorry to keep spamming you but maybe this also signals the solution: > https://github.com/easybuilders/easybuild-easyblocks/pull/1455 > https://github.com/easybuilders/easybuild-easyblocks/issues/1136 > and I even had to use this myself > https://github.com/easybuilders/easybuild-easyblocks/issues/1359 > > Since you're not using a bundle, it should be enough to add it as > prebuildopts: > prebuildopts = 'LDHSARED="$CC -shared" ' All of these relate to building Python extensions with the intel toolchain, when the main Python is build with GCC. I am using an Intel python, and I can see that linkage happens with icc not with gcc. So I do not think this is the problem. Best regards Jakob -- Jakob Schiøtz, professor, Ph.D. Department of Physics Technical University of Denmark DK-2800 Kongens Lyngby, Denmark http://www.fysik.dtu.dk/~schiotz/
