Dear Kenneth,

Kenneth Hoste <[email protected]> writes:

> Dear Loris,
>
> On 28/09/2021 15:03, Loris Bennett wrote:
>> Hi,
>>
>> With EB 4.4.2, My attempt to build
>>
>>    Keras-2.3.1-fosscuda-2019b-Python-3.7.4.eb
>>
>> is failing on the dependency
>>
>>    TensorFlow-2.1.0-fosscuda-2019b-Python-3.7.4
>>
>> with
>>
>>    ERROR:
>> /trinity/shared/easybuild/build/TensorFlow/2.1.0/fosscuda-2019b-Python-3.7.4/TensorFlow/tensorflow-2.1.0/tensorflow/core/platform/BUILD:313:1:
>> C++ compilation of rule '//tensorflow/core/platform:numbers' failed (Exit 1)
>>    tensorflow/core/platform/numbers.cc:28:10: fatal error: 
>> double-conversion/double-conversion.h: No such file or directory
>>
>> but earlier in the log I have
>>
>>    == 2021-09-28 14:19:59,377 modules.py:617 INFO Checking whether 
>> double-conversion/3.1.4-GCCcore-8.3.0 exists...
>>    == 2021-09-28 14:19:59,377 modules.py:622 INFO Module 
>> double-conversion/3.1.4-GCCcore-8.3.0 exists (found in list of available 
>> modules)
>>    == 2021-09-28 14:19:59,377 modules.py:645 INFO Result for existence check 
>> of double-conversion/3.1.4-GCCcore-8.3.0 module: True
>>
>> Does this ring any bells for anyone?
>
> You may need to reinstall your double-conversion module, to ensure it's 
> installed correctly.
>
> See the fixes made in 
> https://github.com/easybuilders/easybuild-easyconfigs/pull/9659, for 
> example.
>
> That was merged quite a while ago though, but perhaps your 
> double-conversion installation is older than that...

Thanks for the information.  In fact our module was installed two days
after that merge into develop, but the EB release with the fix must
obviously have appeared somewhat later.

Is there an easy way of seeing which modules depend on a given module?
I guess this would be more Lmod's job than EB's.  Tweaking the include
path like the fix does seems like it might affect modules which include
double-conversion, although you obviously looked into this.

Cheers,

Loris
 
-- 
Dr. Loris Bennett (Hr./Mr.)
ZEDAT, Freie Universität Berlin         Email [email protected]

Reply via email to