Hi all, I am trying to put together a conda [1] package for pocl, eventually to be uploaded to conda-forge [2]. For now, I'm packaging pocl 0.13. The intention is to use this as the approach to shipping all my CL-based software for users who may not have CL installed. In order to be able to deal with user-defined installation locations, conda builds in an artificially long path like
/opt/conda/conda-bld/home_1483644385670/_b_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehol/lib64 and then hacks all occurences of such strings in the binary by replacing them with the (likely shorter) actual path and NULL-terminating them. That obviously only works if the path is all there is to such strings. When trying to use the resulting pocl binary, I get errors like error: <command line>:17:10: '/home/andreask/pack/miniconda3/share/pocl I've been trying to track down the source of that string, without much success. For instance, all occurrence of PKGDATADIR in POCL (outside of the TCE driver) are such that they should be pure null-terminated paths in the binary. Any suggestions on where I might be able to look? Also, is there any way to force a -g debug build (using CMake) even if LLVM was compiled in release mode? Thanks! Andreas [1] http://conda.pydata.org/docs/ [2] https://conda-forge.github.io/ ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ pocl-devel mailing list pocl-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pocl-devel
