If CFLAGS contains unsanitized CFLAGS which are not understood by nvcc then dev-haskell/accelerate-cuda fails to build as it tries to pass it directly. Strangely it works with -ggdb but not -Wa.
(In reply to comment #0) > If CFLAGS contains unsanitized CFLAGS which are not understood by nvcc then > dev-haskell/accelerate-cuda fails to build as it tries to pass it directly. > Strangely it works with -ggdb but not -Wa. I guess it's due to some sanitizing there is already in-place: src_configure() { # It assumes that configure is run, but does not run it (Andres has # patched upstream to fix this). So need to run configure. But its # difficult to make the configure works as it wants to use # /opt/cuda/bin/nvcc which does not understand lots # of g++ flags. strip-flags filter-flags -march* -ggdb -pipe -Wl* haskell-cabal_src_configure } What are your options?
(In reply to comment #1) > (In reply to comment #0) > > If CFLAGS contains unsanitized CFLAGS which are not understood by nvcc then > > dev-haskell/accelerate-cuda fails to build as it tries to pass it directly. > > Strangely it works with -ggdb but not -Wa. > > I guess it's due to some sanitizing there is already in-place: > > src_configure() { > # It assumes that configure is run, but does not run it (Andres has > # patched upstream to fix this). So need to run configure. But its > # difficult to make the configure works as it wants to use > # /opt/cuda/bin/nvcc which does not understand lots > # of g++ flags. > strip-flags > filter-flags -march* -ggdb -pipe -Wl* > haskell-cabal_src_configure > } > > What are your options? -Wa,--compress-debug-sections (Yes - I understend that it is technically not safe flag but it prevents webkit-gtk build from crashing during compilation when ar tries to create archive bigger then 4G).
pushed fix in the gentoo-haskell overlay in dev-haskell/accelerate-cuda-0.13.0.3-r1.
