Check the compiler version used when USE=cuda is enabled. CUDA-10
so far only supports gcc < 9, which get's installed by the ebuild,
but there was no check whether this compiler is active when emerging
the package.
This patch checks and bails out early, instead of breaking with an
error during the compile phase.
The current ebuild installs a gcc < 9, but doesn't check for the version in use when emerging the package. Add an early check in pkg_pretend to avoid build time errors during compilation.
Note The doc patch you removed from 3.4.0 ebuild is needed whenever USE=doc is enabled, so I re-added it. On my tests, building documentation didn't succeed with python-3, due to old-style print statements for the doc building code.
Check the compiler version used when USE=cuda is enabled. CUDA-10 so far only supports gcc < 9, which get's installed by the ebuild, but there was no check whether this compiler is active when emerging the package. This patch checks and bails out early, instead of breaking with an error during the compile phase.
Package-Manager: Portage-2.3.99, Repoman-2.3.22 Manifest-Sign-Key: 0x2E246A4E715AA683 Signed-off-by: Bernd Waibel waebbl@gmail.com
The current ebuild installs a gcc < 9, but doesn't check for the version in use when emerging the package. Add an early check in pkg_pretend to avoid build time errors during compilation.
Note The doc patch you removed from 3.4.0 ebuild is needed whenever USE=doc is enabled, so I re-added it. On my tests, building documentation didn't succeed with python-3, due to old-style
printstatements for the doc building code.