Ok, Next failure is meson, but I already have a patch for that. (attached)
running install
Checking .pth file support in
/opt/t2-trunk/build/default-9.0-svn-generic-x86-64-linux/usr/lib/python3.7/site-packages/
/opt/t2-trunk/build/default-9.0-svn-generic-x86-64-linux/TOOLCHAIN/tools.cross/bin/python3
-E -c pass
TEST FAILED:
/opt/t2-trunk/build/default-9.0-svn-generic-x86-64-linux/usr/lib/python3.7/site-packages/
does NOT support .pth files
error: bad install directory or PYTHONPATH
^1-meson
You are attempting to install a package to a directory that is not
on PYTHONPATH and which Python does not read ".pth" files from. The
installation directory you specified (via --install-dir, --prefix, or
the distutils default setting) was:
^1-meson
/opt/t2-trunk/build/default-9.0-svn-generic-x86-64-linux/usr/lib/python3.7/site-packages/
^1-meson
and your PYTHONPATH environment variable currently contains:
^1-meson
''on
^1-meson
Here are some of your options for correcting the problem:
^1-meson
* You can choose a different installation directory, i.e., one that is
on PYTHONPATH or supports .pth files
^1-meson
* You can add the installation directory to the PYTHONPATH environment
variable. (It must then also be on PYTHONPATH whenever you run
Python and want to use the package(s) you are installing.)
^1-meson
* You can set up the installation directory to support ".pth" files by
using one of the approaches described here:
^1-meson
https://setuptools.readthedocs.io/en/latest/easy_install.html#custom-installation-locations
^1-meson
^1-meson
Please make the appropriate changes for your system and try again.
Due to previous errors, no 1-meson.log file!
(Try enabling xtrace in the config to track an error inside the build
system.)
--- BUILD ERROR ---
Creating file list and doing final adaptions ...
Searching for orphaned files ...
Found 8 files for this package.
Found 0 orphaned files for this package.
Clear (old) md5sums ...
Creating md5sum files ... done.
Creating package description ...
Making post-install adaptions.
== 02/15/20 03:57:58 =[1]=> Aborted building package meson.
On 2/14/20 10:44 PM, Jan Rovins wrote:
Looking into the mpc error, it seems that my iso file has mpfr.h from
version 3.16 in /usr/include, and it looks like the incompatibility is
between mpfr & mpc.
I tried doing an Build-PKG on my chroot system to update the mpfr to
match the new version 4.02, but that did not help, but down grading it
to v3.16 again got rid of the error, and the build is still running.
Jan
On 2/14/20 9:35 PM, Jan Rovins wrote:
mul.c:175:1: error: conflicting types for 'mpfr_fmma'
175 | mpfr_fmma (mpfr_ptr z, mpfr_srcptr a, mpfr_srcptr b,
mpfr_srcptr c,
| ^~~~~~~~~
In file included from mpc.h:25,
from mpc-impl.h:30,
from mul.c:22:
/opt/t2-trunk/build/default-9.0-svn-generic-x86-64-cross-linux/TOOLCHAIN/tools.cross//usr/include/mpfr.h:731:21:
note: previous declaration of 'mpfr_fmma' was here
731 | __MPFR_DECLSPEC int mpfr_fmma (mpfr_ptr, mpfr_srcptr,
mpfr_srcptr, mpfr_srcptr,
| ^~~~~~~~~
Index: package/develop/meson/meson.desc
===================================================================
--- package/develop/meson/meson.desc (revision 49342)
+++ package/develop/meson/meson.desc (working copy)
@@ -31,5 +31,7 @@
[O] pyscript=python3
[O] runpysetup=1
+[O] export PYVER="`python -V 2>&1 | sed 's/Python \([0-9]\.[0-9]\).*/\1/'`"
+[O] export PYTHONPATH=$root/usr/lib/python$PYVER/site-packages
[D] ee272f6b2231c3c449b5453836b236c1f9cc8b219318998e97642ba1 meson-0.52.1.tar.gz !https://github.com/mesonbuild/meson/archive/0.52.1.tar.gz
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[email protected] with a subject of: unsubscribe t2
