Open robertsawko opened 8 years ago
Okay, I think I located the fault to openjpeg.yaml
file. It seems that on my commit it compiles the version 2.1 but it makes a symbolic link to version 1.5. I am on commit hashdist/hashstack@0355f7b, but I can see the problem on the latest commit to in this file. See the fix_include
step.
I am trying to edit yaml file and remove openjpeg from .hashidist/bld
to force rebuild file but that doesn't seem to change anything and still 2.1 is used. I suppose there's some temporary file sitting in somewhere...
Perhaps this should have been a hashdist issue all along. I have now created a pull request hashdist/hashstack#926 back onto stable/arch
but I think the same problem is on master
and presumably some other branches. My proteus compilation has now passed the problematic step, but I won't close this until I know that you received this message.
OK, thanks a lot. Let's leave this open until I've made sure the hashstack fix is included in the .hashstack_version that we store as the default proteus stack.
Yep, it's the c0q1 tests which are crashing. More precisely it's test_c0q1()
and apparently it's becuase it has something to do with test_hexMesh_3x3=False
. Setting that to True
makes the whole file run.
This should be sorted @cekees. Or no more relevant?
I am trying to solve breaking compilation with hashdist. I think I can overcome this problem, but I would like to do it the hashdist way. Unfortuntately, it quickly outsmarted me and I cannot really figure out what's wrong about this.
My compilation breaks at grib_api:
Even though the file sits where it's supposed to:
The openjpeg.h file is a symbolic link to a file inside
openjpeg-2.1
directory. The linking is done viahashdist
viafix_include
step. Nothing else seems to be out of ordinary. The correct include directory is clearly picked up bygrib_api
. Can you let me know if you can see what's going wrong. I am working from archlinux/stable distribution. Fresh buiild.