The ebuild is missing an "inherit" line below the "EAPI" one that specifies
"toolchain-funcs" (which is the eclass that provides the "tc-*" functions. Try
EAPI=7
inherit toolchain-funcs
Fantastic! Thank you very much! This fixed the problem!
Thank you, Michael and James.
Yes, I plan to submit a nice patch to the Makefile to upstream.
However, I think something is not right on my computer.
I have earlier tried to specify
emake CC="$(tc-getCXX)" prefix="${EPREFIX}/usr" DESTDIR="${D}"
Somehow, emerge does not know what
Dear all,
I got a newbie question.
I need to patch a Makefile, for a package I am working on my own layman
repo. The package is sci-geosciences/sosicon. It converts spatial data
that is in sosi format, which is the national standard format in Norway,
to a shape file or to PostGIS.
In the
Honestly, I find it counter productive to remove a package from the main
repository, when there are active efforts to fix the package's problems.
Xianwen
Chen (陈贤文) wrote:
This ebuild enables Python 3 as one of the Python targets. Otherwise
there is no difference between this ebuild and the latest ebuild in
Portage, which only had Python 2 as the Python target.
Then it probably doesn't work. Did you try running tests on python3
implementations
Dear all,
Attached is an ebuild of dev-python/numba-0.40.1, which was masked for
only having Python 2 as the Python target.
This ebuild enables Python 3 as one of the Python targets. Otherwise
there is no difference between this ebuild and the latest ebuild in
Portage, which only had Python
Dear all,
There is a typo in
https://gitweb.gentoo.org/repo/gentoo.git/tree/dev-lang/julia/julia-1.4.0-r2.ebuild.
On line 82, instead of *llvm_pkg_setp*, it should be *llvm_pkg_setup*.
Yours sincerely,
Xianwen
