> I checked it out and both clBLAS and clFFT actually suffer from the same > problem. It seems upstream is rolling its own > "multiarch" detection / selection mechanism. The detection is based on the > result of CMAKE_SIZEOF_VOID_P, and the > selection can be overriden via a cmake option.
obviously it does not work properly because it end up with a -m64 on my 32 bit system. Maybe this is the real problem. > One option would be to just patch the build system and comment out the part > where the offending build flag is set. I > doubt however that upstream would be happy with this solution, since they > must have setup their CI infrastructure > around this option I presume. > I am wondering what would be a good solution to suggest upstream about. I > guess it is just more convenient for them to > let the build system handle mutliarch builds, including setting the > appropriate build flags and arch-dependent install paths > instead of setting a proper build environment up like dh does. I do not know what is the recommended way in cmake for this kind of "multi-arch" things. maybe someone with more cmake experience can tell how to deal with this kind of problem. Cheers Fred -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
