When building mono from source with Synth I get the following build error:

 

Making all in mini

gmake[4]: Entering directory
'/construction/xports/lang/mono/work/mono-5.10.1.47/mono/mini'

if test -d ../../.git; then \

                    (cd ../..; \

                                         LANG=C; export LANG; \

                                         if test -z "$ghprbPullId"; then \

                                                             branch=`git
branch | grep '^\*' | sed 's/(detached from .*/explicit/' | cut -d ' ' -f
2`; \

                                         else \

 
branch="pull-request-$ghprbPullId"; \

                                         fi; \

                                         version=`git log --no-color
--first-parent -n1 --pretty=format:%h`; \

                                         echo "#define FULL_VERSION
\"$branch/$version\""; \

                    ); \

else \

                    echo "#define FULL_VERSION \"5.10.1.47\""; \

fi > version.h

python2.7 ./genmdesc.py TARGET_AMD64 . cpu-amd64.h amd64_desc ./cpu-amd64.md

gmake[4]: python2.7: Command not found

gmake[4]: *** [Makefile:3996: cpu-amd64.h] Error 127

gmake[4]: *** Waiting for unfinished jobs....

gmake[4]: Leaving directory
'/construction/xports/lang/mono/work/mono-5.10.1.47/mono/mini'

gmake[3]: *** [Makefile:477: all-recursive] Error 1

gmake[3]: Leaving directory
'/construction/xports/lang/mono/work/mono-5.10.1.47/mono'

gmake[2]: *** [Makefile:549: all-recursive] Error 1

gmake[2]: Leaving directory
'/construction/xports/lang/mono/work/mono-5.10.1.47'

gmake[1]: *** [Makefile:479: all] Error 2

gmake[1]: Leaving directory
'/construction/xports/lang/mono/work/mono-5.10.1.47'

===> Compilation failed unexpectedly.

Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to

the maintainer.

*** Error code 1

 

Stop.

make: stopped in /xports/lang/mono

 

 

Any idea's? I have DEFAULT_VERSIONS += python=3.6 in make.conf, as I see
from the log, the build process can't seem to locate python2.7.

Is this the root cause? I'm just speculating. If this is the case, should we
define a hard dependency for mono on py2.7, if it can't deal with py3.6?

 

Thanks,

Dries

 

_______________________________________________
freebsd-mono@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-mono
To unsubscribe, send any mail to "freebsd-mono-unsubscr...@freebsd.org"

Reply via email to