Hi,

I'm trying to rebuild gnucash 3.1-1, downloaded from Sourcefourge,
following the boost update in Arch, but fails with the error below.

I had 3.1 build with no problems previously. Trying to rebuild 3.1 fails
with the same error.

I've managed to temporarily build without the python integration.

The build is in a clean chroot.

Can anyone offer any tips on where to look for a solution? It seems the
offending file is automatically generated by swig.

Many thanks.

Richard.

[ 30%] Built target scm-test-core
Scanning dependencies of target unittest_support
[ 30%] Building C object
common/test-core/CMakeFiles/unittest_support.dir/swig-unittest-support-python.c.o
/build/gnucash/src/gnucash-3.1/common/test-core/swig-unittest-support-python.c:
In function ‘SWIG_Python_FixMethods’:
/build/gnucash/src/gnucash-3.1/common/test-core/swig-unittest-support-python.c:4490:15:
error: ‘strncpy’ output truncated before terminating nul copying 10
bytes from a string of the same length [-Werror=stringop-truncation]
               strncpy(buff, "swig_ptr: ", 10);
               ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
make[2]: ***
[common/test-core/CMakeFiles/unittest_support.dir/build.make:63:
common/test-core/CMakeFiles/unittest_support.dir/swig-unittest-support-python.c.o]
Error 1
make[1]: *** [CMakeFiles/Makefile2:1738:
common/test-core/CMakeFiles/unittest_support.dir/all] Error 2
make: *** [Makefile:163: all] Error 2
==> ERROR: A failure occurred in build().
    Aborting...
==> ERROR: Build failed, check /home/richard/chroot/richard/build


Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Reply via email to