[GNC-dev] Warnings while building master
Today I rebuilt master from scratch and my eye was caught by the following warning: [22/513] Generating swig-engine.cpp /home/janssege/Development/gnucash/master/src/libgnucash/engine/engine-helpers.h:31: Warning 313: Unrecognized extern type "C++". /home/janssege/Development/gnucash/master/src/libgnucash/engine/gnc-date.h:83: Warning 313: Unrecognized extern type "C++". /home/janssege/Development/gnucash/master/src/libgnucash/engine/qofquery.h:90: Warning 302: Identifier 'QofQuery' redefined (ignored), /home/janssege/Development/gnucash/master/src/libgnucash/engine/gnc-option.hpp:55: Warning 302: previous definition of 'QofQuery'. /home/janssege/Development/gnucash/master/src/libgnucash/engine/gnc-commodity.h:56: Warning 313: Unrecognized extern type "C++". /home/janssege/Development/gnucash/master/src/libgnucash/engine/gncBusiness.h:40: Warning 313: Unrecognized extern type "C++". /home/janssege/Development/gnucash/master/src/libgnucash/engine/gncEntry.h:37: Warning 313: Unrecognized extern type "C++". Would this be a potential issue ? The warnings are generated by swig while parsing our headers. Normal compilation of objects that include these files works fine. I don't see anything misbehaving in the built executable either so perhaps it's a non-issue. Regards, Geert ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: [GNC-dev] Problem building master branch
Hi John, I did do a fresh pull and fast forward. I also delete the contents of the build directory whenever I checkout a different branch before building and then rerun cmake and did for this one. I was getting the same problem when I tried to build my branch off the master so I went back to see if the master would build. Both had the same errors. I checked out the maint branch and built it with no problems. I noticed that Christopher Lam had modified a few of the Cmake files when I accidentally rebased on the maint branch yesterday so it may be a hangover from that that the git reflog somehow didn't fix. I'll try and track down exactly where the problem is occurring in the cmake files David - David Cousens -- Sent from: http://gnucash.1415818.n4.nabble.com/GnuCash-Dev-f1435356.html ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
[GNC-dev] Problem building master branch
Hi, I'm getting an error running make while building the master branch. It seems to be a problem loading gnucash/engine/gnc-numeric, which doesn't exist, but libgnucash/engine/gnc-numeric does exist in the sources. maybe primitive-load-path is not set correctly ? Make output where the error occurs is given below. Any suggestions? [ 32%] Built target scm-engine-0 Scanning dependencies of target scm-engine-1 [ 32%] Generating ../../lib/x86_64-linux-gnu/guile/2.0/site-ccache/gnucash/engine/commodity-table.go wrote `/home/david/GnucashDevelopment/Repository/build-make/lib/x86_64-linux-gnu/guile/2.0/site-ccache/gnucash/engine/commodity-table.go' [ 32%] Generating ../../lib/x86_64-linux-gnu/guile/2.0/site-ccache/gnucash/engine/engine-interface.go wrote `/home/david/GnucashDevelopment/Repository/build-make/lib/x86_64-linux-gnu/guile/2.0/site-ccache/gnucash/engine/engine-interface.go' [ 32%] Generating ../../lib/x86_64-linux-gnu/guile/2.0/site-ccache/gnucash/engine/engine-utilities.go Backtrace: In ice-9/eval-string.scm: 44: 19 [read-and-eval # #:lang ...] 37: 18 [lp (use-modules (gnucash engine))] In ice-9/eval.scm: 505: 17 [# (use-modules #)] In ice-9/psyntax.scm: 1106: 16 [expand-top-sequence ((use-modules (gnucash engine))) () ...] 989: 15 [scan ((use-modules (gnucash engine))) () ...] 279: 14 [scan ((# #) #(syntax-object *unspecified* # #)) () (()) ...] In ice-9/boot-9.scm: 3589: 13 [process-use-modules (((gnucash engine)))] 705: 12 [map # ((#))] 3590: 11 [# (#)] 2867: 10 [resolve-interface (gnucash engine) #:select ...] 2792: 9 [# # ...] 3068: 8 [try-module-autoload (gnucash engine) #f] 2404: 7 [save-module-excursion #] 3088: 6 [#] In unknown file: ?: 5 [primitive-load-path "gnucash/engine" ...] In engine.scm: 118: 4 [#] In ice-9/boot-9.scm: 1727: 3 [%start-stack load-stack ...] 1732: 2 [#] In unknown file: ?: 1 [primitive-load-path "gnucash/engine/gnc-numeric"] In ice-9/boot-9.scm: 109: 0 [# misc-error ...] ice-9/boot-9.scm:109:20: In procedure #: ice-9/boot-9.scm:109:20: In procedure primitive-load-path: Unable to find file "gnucash/engine/gnc-numeric" in load path libgnucash/engine/CMakeFiles/scm-engine-1.dir/build.make:80: recipe for target 'lib/x86_64-linux-gnu/guile/2.0/site-ccache/gnucash/engine/engine-utilities.go' failed make[2]: *** [lib/x86_64-linux-gnu/guile/2.0/site-ccache/gnucash/engine/engine-utilities.go] Error 1 CMakeFiles/Makefile2:5301: recipe for target 'libgnucash/engine/CMakeFiles/scm-engine-1.dir/all' failed make[1]: *** [libgnucash/engine/CMakeFiles/scm-engine-1.dir/all] Error 2 Makefile:162: recipe for target 'all' failed make: *** [all] Error 2 David Cousens - David Cousens -- Sent from: http://gnucash.1415818.n4.nabble.com/GnuCash-Dev-f1435356.html ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Problem building master with autotools
On zaterdag 26 augustus 2017 02:41:17 CEST Alex Aycinena wrote: > I can confirm that Geert's commit 64f36323b23d6dc9eb2eab9eb2630f1efc0a64ef > fixes this problem and the --enable-debug switch with autotools no longer > causes this problem on my system. > > Thanks, > > Alex Lovely :) Thanks for your confirmation. Geert ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Problem building master with autotools
Geert, On Fri, Jul 21, 2017 at 1:52 AM, Geert Janssenswrote: > Op woensdag 19 juli 2017 22:09:40 CEST schreef Alex Aycinena: > > On Tue, Jul 11, 2017 at 3:29 PM, Eric Theise > wrote: > > > Hi everyone, > > > > > > I seem to be having the same problem as Alex. It's my first time > trying to > > > do a local build. I'm using an up-to-date Ubuntu 16.04 virtual machine. > > > > > > Eric > > > > > > ... > > > make[4]: Leaving directory '/home/erictheise/Repos/ > > > erictheise/gnucash/build/src/import-export/log-replay' > > > Making all in test > > > ../../../src/engine/test-core/.libs/libgncmod-test-engine.a( > test-engine-s > > > tuff.o): undefined reference to symbol '__gxx_personality_v0@@CXXABI_ > 1.3' > > > //usr/lib/x86_64-linux-gnu/libstdc++.so.6: error adding symbols: DSO > > > missing from command line > > > collect2: error: ld returned 1 exit status > > > Makefile:838: recipe for target 'test-import-pending-matches' failed > > > > > As an update on this issue, I have been able to build with autotools and, > > through a process of elimination, have discovered that the problem occurs > > when I use the --enable-debug configure switch, but not otherwise. In > other > > words: > > > > ../gnucash/configure --srcdir=/home/gnucash-dev/gitcheckouts/gnucash > > --prefix=/opt/gnucash-git/gnucash --enable-debug --enable-doxygen > > --enable-error-on-warning --enable-compile-warnings=yes > > --with-dbi-dbd-dir=/usr/lib64/dbd --enable-ofx --enable-aqbanking > > --enable-locale-specific-tax --enable-python > > > > fails make with the indicated error while: > > > > ../gnucash/configure --srcdir=/home/gnucash-dev/gitcheckouts/gnucash > > --prefix=/opt/gnucash-git/gnucash --enable-doxygen > > --enable-error-on-warning --enable-compile-warnings=yes > > --with-dbi-dbd-dir=/usr/lib64/dbd --enable-ofx --enable-aqbanking > > --enable-locale-specific-tax --enable-python > > > > succeeds through make, make check and, as root, make install. > > > > I don't know why though. > > > > Alex > > I have noticed the same behavior on my laptop. I'm away from home so I > can't > test if I can also reproduce it on the workstation I usually develop on. > Will > do that when I get back home unless someone figures out a fix before that > time. > > Regards, > > Geert > I can confirm that Geert's commit 64f36323b23d6dc9eb2eab9eb2630f1efc0a64ef fixes this problem and the --enable-debug switch with autotools no longer causes this problem on my system. Thanks, Alex ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Problem building master with autotools
Op woensdag 19 juli 2017 22:09:40 CEST schreef Alex Aycinena: > On Tue, Jul 11, 2017 at 3:29 PM, Eric Theisewrote: > > Hi everyone, > > > > I seem to be having the same problem as Alex. It's my first time trying to > > do a local build. I'm using an up-to-date Ubuntu 16.04 virtual machine. > > > > Eric > > > > ... > > make[4]: Leaving directory '/home/erictheise/Repos/ > > erictheise/gnucash/build/src/import-export/log-replay' > > Making all in test > > make[4]: Entering directory '/home/erictheise/Repos/ > > erictheise/gnucash/build/src/import-export/test' > > /bin/bash ../../../libtool --tag=CC --mode=link gcc -I../../../../src > > -I../../../../src/gnc-module -I../../../../src/test-core > > -I../../../../src/engine -I../../../../src/app-utils > > -I../../../../src/import-export -I../../../../src/libqof/qof > > -I../../../../src/engine/test-core -pthread -I/usr/include/gtk-3.0 > > -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 > > -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include > > -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/ > > -I/usr/include/mirclient -I/usr/include/mircore -I/usr/include/mircookie > > -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/harfbuzz > > -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo > > -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 > > -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 > > -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include > > -pthread -I/usr/include/guile/2.0 -pthread -I/usr/include/glib-2.0 > > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -g -std=gnu11 -g -g -o > > test-import-pending-matches > > test_import_pending_matches-test-import-pending-matches.o > > ../../../src/libqof/qof/libgnc-qof.la ../../../src/engine/libgncmod- > > engine.la ../libgncmod-generic-import.la ../../../src/engine/test-core/ > > libgncmod-test-engine.la ../../../src/test-core/libtest-core.la -lgio-2.0 > > -lgthread-2.0 -pthread -lgobject-2.0 -Wl,--export-dynamic -lgmodule-2.0 > > -pthread -lglib-2.0 -lm > > libtool: link: gcc -I../../../../src -I../../../../src/gnc-module > > -I../../../../src/test-core -I../../../../src/engine > > -I../../../../src/app-utils -I../../../../src/import-export > > -I../../../../src/libqof/qof -I../../../../src/engine/test-core -pthread > > -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 > > -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 > > -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gtk-3.0 > > -I/usr/include/gio-unix-2.0/ -I/usr/include/mirclient > > -I/usr/include/mircore -I/usr/include/mircookie -I/usr/include/cairo > > -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 > > -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 > > -I/usr/include/freetype2 -I/usr/include/libpng12 > > -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 > > -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include > > -pthread -I/usr/include/guile/2.0 -pthread -I/usr/include/glib-2.0 > > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -g -std=gnu11 -g -g -o > > .libs/test-import-pending-matches > > test_import_pending_matches-test-import-pending-matches.o -pthread > > -Wl,--export-dynamic -pthread > > ../../../src/libqof/qof/.libs/libgnc-qof.so > > ../../../src/engine/.libs/libgncmod-engine.so > > ../.libs/libgncmod-generic-import.so > > ../../../src/engine/test-core/.libs/libgncmod-test-engine.a > > /home/erictheise/Repos/erictheise/gnucash/build/src/ > > engine/.libs/libgncmod-engine.so /home/erictheise/Repos/ > > erictheise/gnucash/build/src/gnc-module/.libs/libgnc-module.so > > /home/erictheise/Repos/erictheise/gnucash/build/src/ > > core-utils/.libs/libgnc-core-utils.so -lpthread -lguile-2.0 -lgc > > /home/erictheise/Repos/erictheise/gnucash/build/src/libqof/qof/.libs/libgn > > c-qof.so -lboost_regex ../../../src/test-core/.libs/libtest-core.so > > -lgio-2.0 -lgthread-2.0 -lgobject-2.0 -lgmodule-2.0 -lglib-2.0 -lm > > -pthread > > -Wl,-rpath -Wl,/home/erictheise/Repos/erictheise/gnucash/build/lib > > -Wl,-rpath -Wl,/home/erictheise/Repos/erictheise/gnucash/build/lib/gnucash > > /usr/bin/ld: > > ../../../src/engine/test-core/.libs/libgncmod-test-engine.a(test-engine-s > > tuff.o): undefined reference to symbol '__gxx_personality_v0@@CXXABI_1.3' > > //usr/lib/x86_64-linux-gnu/libstdc++.so.6: error adding symbols: DSO > > missing from command line > > collect2: error: ld returned 1 exit status > > Makefile:838: recipe for target 'test-import-pending-matches' failed > > make[4]: *** [test-import-pending-matches] Error 1 > > make[4]: Leaving directory '/home/erictheise/Repos/ > > erictheise/gnucash/build/src/import-export/test' > > Makefile:777: recipe for target 'all-recursive' failed > > make[3]: *** [all-recursive] Error 1 > > make[3]: Leaving directory '/home/erictheise/Repos/ > > erictheise/gnucash/build/src/import-export' > >
Re: Problem building master with autotools
On Tue, Jul 11, 2017 at 3:29 PM, Eric Theisewrote: > Hi everyone, > > I seem to be having the same problem as Alex. It's my first time trying to > do a local build. I'm using an up-to-date Ubuntu 16.04 virtual machine. > > Eric > > ... > make[4]: Leaving directory '/home/erictheise/Repos/ > erictheise/gnucash/build/src/import-export/log-replay' > Making all in test > make[4]: Entering directory '/home/erictheise/Repos/ > erictheise/gnucash/build/src/import-export/test' > /bin/bash ../../../libtool --tag=CC --mode=link gcc -I../../../../src > -I../../../../src/gnc-module -I../../../../src/test-core > -I../../../../src/engine -I../../../../src/app-utils > -I../../../../src/import-export -I../../../../src/libqof/qof > -I../../../../src/engine/test-core -pthread -I/usr/include/gtk-3.0 > -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 > -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include > -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/ > -I/usr/include/mirclient -I/usr/include/mircore -I/usr/include/mircookie > -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/harfbuzz > -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo > -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 > -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 > -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include > -pthread -I/usr/include/guile/2.0 -pthread -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -g -std=gnu11 -g -g -o > test-import-pending-matches > test_import_pending_matches-test-import-pending-matches.o > ../../../src/libqof/qof/libgnc-qof.la ../../../src/engine/libgncmod- > engine.la ../libgncmod-generic-import.la ../../../src/engine/test-core/ > libgncmod-test-engine.la ../../../src/test-core/libtest-core.la -lgio-2.0 > -lgthread-2.0 -pthread -lgobject-2.0 -Wl,--export-dynamic -lgmodule-2.0 > -pthread -lglib-2.0 -lm > libtool: link: gcc -I../../../../src -I../../../../src/gnc-module > -I../../../../src/test-core -I../../../../src/engine > -I../../../../src/app-utils -I../../../../src/import-export > -I../../../../src/libqof/qof -I../../../../src/engine/test-core -pthread > -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 > -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 > -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gtk-3.0 > -I/usr/include/gio-unix-2.0/ -I/usr/include/mirclient > -I/usr/include/mircore -I/usr/include/mircookie -I/usr/include/cairo > -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 > -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 > -I/usr/include/freetype2 -I/usr/include/libpng12 > -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 > -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include > -pthread -I/usr/include/guile/2.0 -pthread -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -g -std=gnu11 -g -g -o > .libs/test-import-pending-matches > test_import_pending_matches-test-import-pending-matches.o > -pthread -Wl,--export-dynamic -pthread > ../../../src/libqof/qof/.libs/libgnc-qof.so > ../../../src/engine/.libs/libgncmod-engine.so > ../.libs/libgncmod-generic-import.so > ../../../src/engine/test-core/.libs/libgncmod-test-engine.a > /home/erictheise/Repos/erictheise/gnucash/build/src/ > engine/.libs/libgncmod-engine.so /home/erictheise/Repos/ > erictheise/gnucash/build/src/gnc-module/.libs/libgnc-module.so > /home/erictheise/Repos/erictheise/gnucash/build/src/ > core-utils/.libs/libgnc-core-utils.so -lpthread -lguile-2.0 -lgc > /home/erictheise/Repos/erictheise/gnucash/build/src/libqof/qof/.libs/libgnc-qof.so > -lboost_regex ../../../src/test-core/.libs/libtest-core.so -lgio-2.0 > -lgthread-2.0 -lgobject-2.0 -lgmodule-2.0 -lglib-2.0 -lm -pthread > -Wl,-rpath -Wl,/home/erictheise/Repos/erictheise/gnucash/build/lib > -Wl,-rpath -Wl,/home/erictheise/Repos/erictheise/gnucash/build/lib/gnucash > /usr/bin/ld: > ../../../src/engine/test-core/.libs/libgncmod-test-engine.a(test-engine-stuff.o): > undefined reference to symbol '__gxx_personality_v0@@CXXABI_1.3' > //usr/lib/x86_64-linux-gnu/libstdc++.so.6: error adding symbols: DSO > missing from command line > collect2: error: ld returned 1 exit status > Makefile:838: recipe for target 'test-import-pending-matches' failed > make[4]: *** [test-import-pending-matches] Error 1 > make[4]: Leaving directory '/home/erictheise/Repos/ > erictheise/gnucash/build/src/import-export/test' > Makefile:777: recipe for target 'all-recursive' failed > make[3]: *** [all-recursive] Error 1 > make[3]: Leaving directory '/home/erictheise/Repos/ > erictheise/gnucash/build/src/import-export' > Makefile:597: recipe for target 'all-recursive' failed > make[2]: *** [all-recursive] Error 1 > make[2]: Leaving directory '/home/erictheise/Repos/ > erictheise/gnucash/build/src' > Makefile:826: recipe for target 'all-recursive' failed >
Re: Problem building master with autotools
> On Jul 11, 2017, at 10:13 AM, Alex Aycinena <alex.aycin...@gmail.com> wrote: > > John, > > -- Forwarded message -- > From: John Ralls <jra...@ceridwen.us <mailto:jra...@ceridwen.us>> > To: Geert Janssens <geert.gnuc...@kobaltwit.be > <mailto:geert.gnuc...@kobaltwit.be>> > Cc: gnucash-devel@gnucash.org <mailto:gnucash-devel@gnucash.org>, Alex > Aycinena <alex.aycin...@gmail.com <mailto:alex.aycin...@gmail.com>> > Bcc: > Date: Tue, 11 Jul 2017 06:57:52 -0700 > Subject: Re: Problem building master with autotools > > > > On Jul 11, 2017, at 5:33 AM, Geert Janssens <geert.gnuc...@kobaltwit.be > > <mailto:geert.gnuc...@kobaltwit.be>> wrote: > > > > On dinsdag 11 juli 2017 03:38:16 CEST Alex Aycinena wrote: > >> With a fresh checkout of master, I try to build with the autotools but I > >> get an error in linking test-import-pending-matches with test-engine-stuff > >> during make as follows: > >> > >> /usr/bin/ld: > >> ../../../src/engine/test-core/.libs/libgncmod-test-engine.a(test-engine-stuf > >> f.o): undefined reference to symbol '__gxx_personality_v0@@CXXABI_1.3' > >> /usr/lib64/libstdc++.so.6: error adding symbols: DSO missing from command > >> line > >> collect2: error: ld returned 1 exit status > >> Makefile:837: recipe for target 'test-import-pending-matches' failed > >> > >> I can build with cmake but I would like to run make check after an > >> autotools make because I think it runs different checks. > >> > >> Can anyone give me an idea of how to get this to work? This is Fedora 25. > >> > > > > Odd I don't get this on my system (Fedora 25 as well). > > > > The linker is having issues resolving "__gxx_personality_v0". The internet > > cites two common issues for this: > > - either a library is missing > > - or the sequence of libraries on the command line is wrong (a symbol to > > resolve should appear after the source in which it's being imported). > > I hit that the other day and the problem was that I had installed libraries > from master while trying to build maint. Since the latter doesn’t link to > libstdc++, picking up one of the installed libraries that needed it caused > the error and clearing out the installed libgnc* fixed the problem. > > Regards, > John Ralls > > Ah, so it is not just me. This might help me solve it but I'm not quite > following. If I do a new checkout and then build in an empty separate build > directory, wouldn't that avoid the problem? Where would the installed libgnc* > be that causes the problem that I would have to clear out? In > /usr/lib64/gnucash? If I change anything there, wouldn't that mess up the > Fedora installed gnucash package? > > By the way, I'm getting the same problem on three separate systems: a Fedora > 24, a Fedora 25 and a Fedora 25 VM, so if it is some strange system > configuration I have, then I have it on three systems, not just one. I think > I'll try a new VM of Fedora 26 that just came out and see if it works there. Alex, You don’t necessarily have the same problem just because you have the same symptom, but no, just having a separate build directory isn’t enough. If you have libgnc* anywhere the linker looks for libraries you run the risk of it linking one of those instead of the ones in your build-dir. The most likely suspect would be the components of the GnuCash in /usr/lib that you use for keeping your books, but if you set —prefix=/opt/foo and run make install, then later have another build for which you also set —prefix=/opt/foo then the installed libraries from the first build can screw up the second. Short of switching to a Mac, where the application bundles and separate jhbuild prefixes keep everything perfectly isolated, the best solution is to develop in a VM and if you have multiple builds ensure that they each have their own prefix directory so that none can see the product of another. Regards, John Ralls ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Problem building master with autotools
Hi everyone, I seem to be having the same problem as Alex. It's my first time trying to do a local build. I'm using an up-to-date Ubuntu 16.04 virtual machine. Eric ... make[4]: Leaving directory '/home/erictheise/Repos/erictheise/gnucash/build/src/import-export/log-replay' Making all in test make[4]: Entering directory '/home/erictheise/Repos/erictheise/gnucash/build/src/import-export/test' /bin/bash ../../../libtool --tag=CC --mode=link gcc -I../../../../src -I../../../../src/gnc-module -I../../../../src/test-core -I../../../../src/engine -I../../../../src/app-utils -I../../../../src/import-export -I../../../../src/libqof/qof -I../../../../src/engine/test-core -pthread -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/mirclient -I/usr/include/mircore -I/usr/include/mircookie -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread -I/usr/include/guile/2.0 -pthread -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -g -std=gnu11 -g -g -o test-import-pending-matches test_import_pending_matches-test-import-pending-matches.o ../../../src/libqof/qof/libgnc-qof.la ../../../src/engine/ libgncmod-engine.la ../libgncmod-generic-import.la ../../../src/engine/test-core/libgncmod-test-engine.la ../../../src/test-core/libtest-core.la -lgio-2.0 -lgthread-2.0 -pthread -lgobject-2.0 -Wl,--export-dynamic -lgmodule-2.0 -pthread -lglib-2.0 -lm libtool: link: gcc -I../../../../src -I../../../../src/gnc-module -I../../../../src/test-core -I../../../../src/engine -I../../../../src/app-utils -I../../../../src/import-export -I../../../../src/libqof/qof -I../../../../src/engine/test-core -pthread -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/mirclient -I/usr/include/mircore -I/usr/include/mircookie -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread -I/usr/include/guile/2.0 -pthread -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -g -std=gnu11 -g -g -o .libs/test-import-pending-matches test_import_pending_matches-test-import-pending-matches.o -pthread -Wl,--export-dynamic -pthread ../../../src/libqof/qof/.libs/libgnc-qof.so ../../../src/engine/.libs/libgncmod-engine.so ../.libs/libgncmod-generic-import.so ../../../src/engine/test-core/.libs/libgncmod-test-engine.a /home/erictheise/Repos/erictheise/gnucash/build/src/engine/.libs/libgncmod-engine.so /home/erictheise/Repos/erictheise/gnucash/build/src/gnc-module/.libs/libgnc-module.so /home/erictheise/Repos/erictheise/gnucash/build/src/core-utils/.libs/libgnc-core-utils.so -lpthread -lguile-2.0 -lgc /home/erictheise/Repos/erictheise/gnucash/build/src/libqof/qof/.libs/libgnc-qof.so -lboost_regex ../../../src/test-core/.libs/libtest-core.so -lgio-2.0 -lgthread-2.0 -lgobject-2.0 -lgmodule-2.0 -lglib-2.0 -lm -pthread -Wl,-rpath -Wl,/home/erictheise/Repos/erictheise/gnucash/build/lib -Wl,-rpath -Wl,/home/erictheise/Repos/erictheise/gnucash/build/lib/gnucash /usr/bin/ld: ../../../src/engine/test-core/.libs/libgncmod-test-engine.a(test-engine-stuff.o): undefined reference to symbol '__gxx_personality_v0@@CXXABI_1.3' //usr/lib/x86_64-linux-gnu/libstdc++.so.6: error adding symbols: DSO missing from command line collect2: error: ld returned 1 exit status Makefile:838: recipe for target 'test-import-pending-matches' failed make[4]: *** [test-import-pending-matches] Error 1 make[4]: Leaving directory '/home/erictheise/Repos/erictheise/gnucash/build/src/import-export/test' Makefile:777: recipe for target 'all-recursive' failed make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory '/home/erictheise/Repos/erictheise/gnucash/build/src/import-export' Makefile:597: recipe for target 'all-recursive' failed make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory '/home/erictheise/Repos/erictheise/gnucash/build/src' Makefile:826: recipe for target 'all-recursive' failed make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory '/home/erictheise/Repos/erictheise/gnucash/build' Makefile:680: recipe for target 'all' failed make: *** [all] Error 2 erictheise@erictheise-VirtualBox:~/Repos/erictheise/gnucash/build$ On Tue, Jul 11,
Re: Problem building master with autotools
Geert, > Odd I don't get this on my system (Fedora 25 as well). > > The linker is having issues resolving "__gxx_personality_v0". The internet > cites two common issues for this: > - either a library is missing > - or the sequence of libraries on the command line is wrong (a symbol to > resolve should appear after the source in which it's being imported). > > For the first I option I don't have many clues. The symbol is defined in > libstdc++. You could check whether it's installed on your system, including > the devel package. > > Both libstdc++ and libstdc++-devel are installed > If it's a case of out of order mentioning of link libraries, we could use > my > system as a reference as I don't have the issue. > > Below is the full command issued to build test-import-pending-matches: > > The two differences I found are > -g -O2 -std=gnu11 > mine says: -g -std=gnull -g -g Mine doesn't have: > -lsecret-1 > > > > Do you see any differences with yours ? > I don't know if the two items above have any bearing or why they would be different. > > Others may be able to give you more direct help. I'm not very fluent in > linker > stuff I'm afraid... > > Geert > > Neither am I but thanks for your help. Alex ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Problem building master with autotools
John, > > -- Forwarded message -- > From: John Ralls <jra...@ceridwen.us> > To: Geert Janssens <geert.gnuc...@kobaltwit.be> > Cc: gnucash-devel@gnucash.org, Alex Aycinena <alex.aycin...@gmail.com> > Bcc: > Date: Tue, 11 Jul 2017 06:57:52 -0700 > Subject: Re: Problem building master with autotools > > > > On Jul 11, 2017, at 5:33 AM, Geert Janssens <geert.gnuc...@kobaltwit.be> > wrote: > > > > On dinsdag 11 juli 2017 03:38:16 CEST Alex Aycinena wrote: > >> With a fresh checkout of master, I try to build with the autotools but I > >> get an error in linking test-import-pending-matches with > test-engine-stuff > >> during make as follows: > >> > >> /usr/bin/ld: > >> ../../../src/engine/test-core/.libs/libgncmod-test-engine.a( > test-engine-stuf > >> f.o): undefined reference to symbol '__gxx_personality_v0@@CXXABI_1.3' > >> /usr/lib64/libstdc++.so.6: error adding symbols: DSO missing from > command > >> line > >> collect2: error: ld returned 1 exit status > >> Makefile:837: recipe for target 'test-import-pending-matches' failed > >> > >> I can build with cmake but I would like to run make check after an > >> autotools make because I think it runs different checks. > >> > >> Can anyone give me an idea of how to get this to work? This is Fedora > 25. > >> > > > > Odd I don't get this on my system (Fedora 25 as well). > > > > The linker is having issues resolving "__gxx_personality_v0". The > internet > > cites two common issues for this: > > - either a library is missing > > - or the sequence of libraries on the command line is wrong (a symbol to > > resolve should appear after the source in which it's being imported). > > I hit that the other day and the problem was that I had installed > libraries from master while trying to build maint. Since the latter doesn’t > link to libstdc++, picking up one of the installed libraries that needed it > caused the error and clearing out the installed libgnc* fixed the problem. > > Regards, > John Ralls > > Ah, so it is not just me. This might help me solve it but I'm not quite following. If I do a new checkout and then build in an empty separate build directory, wouldn't that avoid the problem? Where would the installed libgnc* be that causes the problem that I would have to clear out? In /usr/lib64/gnucash? If I change anything there, wouldn't that mess up the Fedora installed gnucash package? By the way, I'm getting the same problem on three separate systems: a Fedora 24, a Fedora 25 and a Fedora 25 VM, so if it is some strange system configuration I have, then I have it on three systems, not just one. I think I'll try a new VM of Fedora 26 that just came out and see if it works there. Alex ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Problem building master with autotools
Sumit, > > -- Forwarded message -- > From: Sumit Bhardwaj <bhardw...@gmail.com> > To: Alex Aycinena <alex.aycin...@gmail.com> > Cc: gnucash-devel <gnucash-devel@gnucash.org> > Bcc: > Date: Mon, 10 Jul 2017 20:04:00 -0700 > Subject: Re: Problem building master with autotools > Just did a fresh pull from gnucash/master (not a rebase). > > Using autotools (./autogen.sh && ./configure --enable-compile-warnings && > make) succeeded. > > Make check failed. Fail message is below. I will try to look at it if I > have some time tonight. > > -Sumit > > ./../../test-driver: line 107: 8259 Trace/breakpoint trap (core dumped) > "$@" > $log_file 2>&1 > FAIL: test-app-utils > > > Testsuite summary for GnuCash 2.6.99 > > > # TOTAL: 7 > # PASS: 6 > # SKIP: 0 > # XFAIL: 0 > # FAIL: 1 > # XPASS: 0 > # ERROR: 0 > > > See src/app-utils/test/test-suite.log > Please report to gnucash-devel@gnucash.org > > > Makefile:1051: recipe for target 'test-suite.log' failed > make[5]: *** [test-suite.log] Error 1 > make[5]: Leaving directory > '/home/bhardwajs/ac/devel/gnucash/src/app-utils/test' > Makefile:1157: recipe for target 'check-TESTS' failed > make[4]: *** [check-TESTS] Error 2 > make[4]: Leaving directory > '/home/bhardwajs/ac/devel/gnucash/src/app-utils/test' > Makefile:1272: recipe for target 'check-am' failed > make[3]: *** [check-am] Error 2 > make[3]: Leaving directory > '/home/bhardwajs/ac/devel/gnucash/src/app-utils/test' > Makefile:1026: recipe for target 'check-recursive' failed > make[2]: *** [check-recursive] Error 1 > make[2]: Leaving directory '/home/bhardwajs/ac/devel/ > gnucash/src/app-utils' > Makefile:596: recipe for target 'check-recursive' failed > make[1]: *** [check-recursive] Error 1 > make[1]: Leaving directory '/home/bhardwajs/ac/devel/gnucash/src' > Makefile:825: recipe for target 'check-recursive' failed > make: *** [check-recursive] Error 1 > > This the test that I pushed that I can't test since I can't build with autotools. This test apparently isn't run when you test with cmake, which I didn't realize. I have backed it out until I can test it and hopefully didn't introduce any other problems in doing so. Alex ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Problem building master with autotools
> On Jul 11, 2017, at 5:33 AM, Geert Janssens> wrote: > > On dinsdag 11 juli 2017 03:38:16 CEST Alex Aycinena wrote: >> With a fresh checkout of master, I try to build with the autotools but I >> get an error in linking test-import-pending-matches with test-engine-stuff >> during make as follows: >> >> /usr/bin/ld: >> ../../../src/engine/test-core/.libs/libgncmod-test-engine.a(test-engine-stuf >> f.o): undefined reference to symbol '__gxx_personality_v0@@CXXABI_1.3' >> /usr/lib64/libstdc++.so.6: error adding symbols: DSO missing from command >> line >> collect2: error: ld returned 1 exit status >> Makefile:837: recipe for target 'test-import-pending-matches' failed >> >> I can build with cmake but I would like to run make check after an >> autotools make because I think it runs different checks. >> >> Can anyone give me an idea of how to get this to work? This is Fedora 25. >> > > Odd I don't get this on my system (Fedora 25 as well). > > The linker is having issues resolving "__gxx_personality_v0". The internet > cites two common issues for this: > - either a library is missing > - or the sequence of libraries on the command line is wrong (a symbol to > resolve should appear after the source in which it's being imported). I hit that the other day and the problem was that I had installed libraries from master while trying to build maint. Since the latter doesn’t link to libstdc++, picking up one of the installed libraries that needed it caused the error and clearing out the installed libgnc* fixed the problem. Regards, John Ralls ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Problem building master with autotools
On dinsdag 11 juli 2017 03:38:16 CEST Alex Aycinena wrote: > With a fresh checkout of master, I try to build with the autotools but I > get an error in linking test-import-pending-matches with test-engine-stuff > during make as follows: > > /usr/bin/ld: > ../../../src/engine/test-core/.libs/libgncmod-test-engine.a(test-engine-stuf > f.o): undefined reference to symbol '__gxx_personality_v0@@CXXABI_1.3' > /usr/lib64/libstdc++.so.6: error adding symbols: DSO missing from command > line > collect2: error: ld returned 1 exit status > Makefile:837: recipe for target 'test-import-pending-matches' failed > > I can build with cmake but I would like to run make check after an > autotools make because I think it runs different checks. > > Can anyone give me an idea of how to get this to work? This is Fedora 25. > Odd I don't get this on my system (Fedora 25 as well). The linker is having issues resolving "__gxx_personality_v0". The internet cites two common issues for this: - either a library is missing - or the sequence of libraries on the command line is wrong (a symbol to resolve should appear after the source in which it's being imported). For the first I option I don't have many clues. The symbol is defined in libstdc++. You could check whether it's installed on your system, including the devel package. If it's a case of out of order mentioning of link libraries, we could use my system as a reference as I don't have the issue. Below is the full command issued to build test-import-pending-matches: libtool: link: gcc -I/gitsrc-dir/src -I/gitsrc-dir/src/gnc-module -I/gitsrc-dir/src/test-core -I/gitsrc-dir/src/engine -I/gitsrc-dir/src/app-utils -I/gitsrc-dir/src/import-export -I/gitsrc-dir/src/libqof/qof -I/gitsrc-dir/src/engine/test-core -pthread -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib64/dbus-1.0/include -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/freetype2 -I/usr/include/libdrm -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -pthread -I/usr/include/guile/2.0 -pthread -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -g -O2 -std=gnu11 -o .libs/test-import-pending-matches test_import_pending_matches-test-import-pending-matches.o -pthread -Wl,--export-dynamic -pthread ../../../src/libqof/qof/.libs/libgnc-qof.so -L/usr/lib64 ../../../src/engine/.libs/libgncmod-engine.so ../.libs/libgncmod-generic-import.so /build-dir/src/gnome-utils/.libs/libgncmod-gnome-utils.so /build-dir/src/backend/xml/.libs/libgnc-backend-xml-utils.so -lgnome-keyring -lsecret-1 -lX11 /build-dir/src/app-utils/.libs/libgncmod-app-utils.so -lgtk-3 -lgdk-3 -lpangocairo-1.0 -lpango-1.0 -latk-1.0 -lcairo-gobject -lcairo -lgdk_pixbuf-2.0 -lxslt -lz -ldl -lxml2 ../../../src/engine/test-core/.libs/libgncmod-test-engine.a /build-dir/src/engine/.libs/libgncmod-engine.so /build-dir/src/gnc-module/.libs/libgnc-module.so /build-dir/src/core-utils/.libs/libgnc-core-utils.so -lpthread -lguile-2.0 -lgc ../../../src/test-core/.libs/libtest-core.so /build-dir/src/libqof/qof/.libs/libgnc-qof.so -lboost_regex -lgio-2.0 -lgthread-2.0 -lgobject-2.0 -lgmodule-2.0 -lglib-2.0 -lm -pthread -Wl,-rpath -Wl,/install-dir/lib -Wl,-rpath -Wl,/install-dir/lib/gnucash Do you see any differences with yours ? Others may be able to give you more direct help. I'm not very fluent in linker stuff I'm afraid... Geert ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Problem building master with autotools
Just did a fresh pull from gnucash/master (not a rebase). Using autotools (./autogen.sh && ./configure --enable-compile-warnings && make) succeeded. Make check failed. Fail message is below. I will try to look at it if I have some time tonight. -Sumit ./../../test-driver: line 107: 8259 Trace/breakpoint trap (core dumped) "$@" > $log_file 2>&1 FAIL: test-app-utils Testsuite summary for GnuCash 2.6.99 # TOTAL: 7 # PASS: 6 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 See src/app-utils/test/test-suite.log Please report to gnucash-devel@gnucash.org Makefile:1051: recipe for target 'test-suite.log' failed make[5]: *** [test-suite.log] Error 1 make[5]: Leaving directory '/home/bhardwajs/ac/devel/gnucash/src/app-utils/test' Makefile:1157: recipe for target 'check-TESTS' failed make[4]: *** [check-TESTS] Error 2 make[4]: Leaving directory '/home/bhardwajs/ac/devel/gnucash/src/app-utils/test' Makefile:1272: recipe for target 'check-am' failed make[3]: *** [check-am] Error 2 make[3]: Leaving directory '/home/bhardwajs/ac/devel/gnucash/src/app-utils/test' Makefile:1026: recipe for target 'check-recursive' failed make[2]: *** [check-recursive] Error 1 make[2]: Leaving directory '/home/bhardwajs/ac/devel/gnucash/src/app-utils' Makefile:596: recipe for target 'check-recursive' failed make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory '/home/bhardwajs/ac/devel/gnucash/src' Makefile:825: recipe for target 'check-recursive' failed make: *** [check-recursive] Error 1 On Mon, Jul 10, 2017 at 7:15 PM, Alex Aycinenawrote: > > > On Jul 10, 2017 6:58 PM, "Sumit Bhardwaj" wrote: > > I checked out master in the AM today and had a clean build (make and make > install) on Fedora 25 using autotools. I can try again once I get to my > personal machine. > > Are you doing make test here? I can try and report. > > Thanks, > Sumit > > On Mon, Jul 10, 2017 at 6:38 PM, Alex Aycinena > wrote: > >> With a fresh checkout of master, I try to build with the autotools but I >> get an error in linking test-import-pending-matches with test-engine-stuff >> during make as follows: >> >> /usr/bin/ld: >> ../../../src/engine/test-core/.libs/libgncmod-test-engine.a( >> test-engine-stuff.o): >> undefined reference to symbol '__gxx_personality_v0@@CXXABI_1.3' >> /usr/lib64/libstdc++.so.6: error adding symbols: DSO missing from command >> line >> collect2: error: ld returned 1 exit status >> Makefile:837: recipe for target 'test-import-pending-matches' failed >> >> I can build with cmake but I would like to run make check after an >> autotools make because I think it runs different checks. >> >> Can anyone give me an idea of how to get this to work? This is Fedora 25. >> >> Thanks, >> >> Alex >> ___ >> gnucash-devel mailing list >> gnucash-devel@gnucash.org >> https://lists.gnucash.org/mailman/listinfo/gnucash-devel >> > > No - I have a new check out and an empty build directory. I run autogen.sh > then change to the build directory. I run config with a bunch of switches > referring back to the main directory for source. Then I run make and get > the error. > > Can't figure out why it stopped working suddenly a few weeks ago. > > Thanks. > > Alex > ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Problem building master with autotools
On Jul 10, 2017 6:58 PM, "Sumit Bhardwaj"wrote: I checked out master in the AM today and had a clean build (make and make install) on Fedora 25 using autotools. I can try again once I get to my personal machine. Are you doing make test here? I can try and report. Thanks, Sumit On Mon, Jul 10, 2017 at 6:38 PM, Alex Aycinena wrote: > With a fresh checkout of master, I try to build with the autotools but I > get an error in linking test-import-pending-matches with test-engine-stuff > during make as follows: > > /usr/bin/ld: > ../../../src/engine/test-core/.libs/libgncmod-test-engine.a( > test-engine-stuff.o): > undefined reference to symbol '__gxx_personality_v0@@CXXABI_1.3' > /usr/lib64/libstdc++.so.6: error adding symbols: DSO missing from command > line > collect2: error: ld returned 1 exit status > Makefile:837: recipe for target 'test-import-pending-matches' failed > > I can build with cmake but I would like to run make check after an > autotools make because I think it runs different checks. > > Can anyone give me an idea of how to get this to work? This is Fedora 25. > > Thanks, > > Alex > ___ > gnucash-devel mailing list > gnucash-devel@gnucash.org > https://lists.gnucash.org/mailman/listinfo/gnucash-devel > No - I have a new check out and an empty build directory. I run autogen.sh then change to the build directory. I run config with a bunch of switches referring back to the main directory for source. Then I run make and get the error. Can't figure out why it stopped working suddenly a few weeks ago. Thanks. Alex ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Problem building master with autotools
I checked out master in the AM today and had a clean build (make and make install) on Fedora 25 using autotools. I can try again once I get to my personal machine. Are you doing make test here? I can try and report. Thanks, Sumit On Mon, Jul 10, 2017 at 6:38 PM, Alex Aycinenawrote: > With a fresh checkout of master, I try to build with the autotools but I > get an error in linking test-import-pending-matches with test-engine-stuff > during make as follows: > > /usr/bin/ld: > ../../../src/engine/test-core/.libs/libgncmod-test-engine.a( > test-engine-stuff.o): > undefined reference to symbol '__gxx_personality_v0@@CXXABI_1.3' > /usr/lib64/libstdc++.so.6: error adding symbols: DSO missing from command > line > collect2: error: ld returned 1 exit status > Makefile:837: recipe for target 'test-import-pending-matches' failed > > I can build with cmake but I would like to run make check after an > autotools make because I think it runs different checks. > > Can anyone give me an idea of how to get this to work? This is Fedora 25. > > Thanks, > > Alex > ___ > gnucash-devel mailing list > gnucash-devel@gnucash.org > https://lists.gnucash.org/mailman/listinfo/gnucash-devel > ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Problem building master with autotools
With a fresh checkout of master, I try to build with the autotools but I get an error in linking test-import-pending-matches with test-engine-stuff during make as follows: /usr/bin/ld: ../../../src/engine/test-core/.libs/libgncmod-test-engine.a(test-engine-stuff.o): undefined reference to symbol '__gxx_personality_v0@@CXXABI_1.3' /usr/lib64/libstdc++.so.6: error adding symbols: DSO missing from command line collect2: error: ld returned 1 exit status Makefile:837: recipe for target 'test-import-pending-matches' failed I can build with cmake but I would like to run make check after an autotools make because I think it runs different checks. Can anyone give me an idea of how to get this to work? This is Fedora 25. Thanks, Alex ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: building master
> -- Forwarded message -- > From: John Ralls <jra...@ceridwen.us> > To: Alex Aycinena <alex.aycin...@gmail.com> > Cc: gnucash-devel <gnucash-devel@gnucash.org> > Bcc: > Date: Sat, 22 Apr 2017 16:48:05 -0700 > Subject: Re: building master > > > On Apr 22, 2017, at 3:47 PM, Alex Aycinena <alex.aycin...@gmail.com> > wrote: > > > >> > > > So to switch to using cmake with ninja, I installed cmake (which installed > > cmake-data and jsoncpp, as well) and ninja-build (on Fedora). But from > your > > note, it was still unclear to me how to use them. Up to now, I have had > two > > parallel directories, for example, gnucash-clean, where the source is > > checked out to, and gnucash-clean-build, where I build. Then I would: > > > > $ cd /home/gnucash-dev/gitcheckouts/gnucash-clean > > $ git pull > > $ ./autogen.sh > > $ cd /home/gnucash-dev/gitcheckouts/gnucash-clean-build > > $ rm -rf * > > $ ../gnucash-clean/configure > > --srcdir=/home/gnucash-dev/gitcheckouts/gnucash-clean > > --prefix=/opt/gnucash-git/gnucash-clean --enable-debug --enable-doxygen > > --enable-error-on-warning --enable-compile-warnings=yes > > --with-dbi-dbd-dir=/usr/lib64/dbd --enable-ofx --enable-aqbanking > > --enable-locale-specific-tax --enable-python > > $ make > > $ make check > > > > Then after switching to root: > > > > $ cd /home/gnucash-dev/gitcheckouts/gnucash-clean-build > > $ make install > > > > So now I tried instead: > > > > $ cd /home/gnucash-dev/gitcheckouts/gnucash-clean > > $ git pull > > $ ./autogen.sh <-- still needed I assumed? > > $ cd /home/gnucash-dev/gitcheckouts/gnucash-clean-build > > $ rm -rf * > > cmake -D WITH_PYTHON=ON \ > > -D CMAKE_INSTALL_PREFIX=/opt/gnucash-git/gnucash-clean \ > > -D CMAKE_BUILD_TYPE=Debug \ > > -D WITH_AQBANKING=ON -G Ninja \ > > /home/gnucash-dev/gitcheckouts/gnucash-clean > > $ ninja-build > > > > It was working away until it stopped with: > > > > [166/962] cd > > /home/gnucash-dev/gitchec...ean/src/doc/design/gnucash-design.texi > > FAILED: src/doc/design/CMakeFiles/gnucash-design.texi > > cd /home/gnucash-dev/gitcheckouts/gnucash-clean-build/src/doc/design && > > makeinfo -I > > /home/gnucash-dev/gitcheckouts/gnucash-clean-build/src/doc/design > > /home/gnucash-dev/gitcheckouts/gnucash-clean/ > src/doc/design/gnucash-design.texi > > /bin/sh: makeinfo: command not found > > [168/962] Building CXX object > > src/libq...Files/gnc-qof.dir/qof/qofsession.cpp.o > > ninja: build stopped: subcommand failed. > > > > Feedback would be welcome. > > > > I assume once I get a clean build, then I would: > > > > $ ninja-build check > > > > Then after switching to root: > > > > $ cd /home/gnucash-dev/gitcheckouts/gnucash-clean-build > > $ ninja-build install > > > > Also, what happens to these other configure options I would previously > set: > > > > --enable-doxygen > > --enable-error-on-warning > > --enable-compile-warnings=yes > > --with-dbi-dbd-dir=/usr/lib64/dbd > > --enable-ofx (I see in CMakeCache.txt that WITH_OFX:BOOL=ON even though I > > didn't specify it) > > --enable-locale-specific-tax > > Alex, > > See https://github.com/Gnucash/gnucash/blob/master/cmake/README_CMAKE.txt. > > You don't need or want to autogen. That's autotools and CMake doesn't use > any of that stuff. > Pretty much everything is on by default so generally no build options need > to be set. > > The failure suggests that you might not have texinfo installed. We should > probably just turn off building the obsolete texi files anyway and think > about removing them. > > Regards, > John Ralls > > > > > -- Forwarded message -- > From: Geert Janssens <geert.gnuc...@kobaltwit.be> > To: gnucash-devel@gnucash.org > Cc: John Ralls <jra...@ceridwen.us>, Alex Aycinena < > alex.aycin...@gmail.com> > Bcc: > Date: Sun, 23 Apr 2017 12:25:56 +0200 > Subject: Re: building master > On zondag 23 april 2017 01:48:05 CEST John Ralls wrote: > > See https://github.com/Gnucash/gnucash/blob/master/cmake/ > README_CMAKE.txt. > > > > Ah, that was the link I should have passed to Wm as well... Thanks for > referring to it. > > Geert > John and Geert, Thanks for the help. I installed texinfo and followed your other suggestions and got a clean build and check with cmake and ninja so now I'm back in business. Alex ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: building master
On zondag 23 april 2017 01:48:05 CEST John Ralls wrote: > See https://github.com/Gnucash/gnucash/blob/master/cmake/README_CMAKE.txt. > Ah, that was the link I should have passed to Wm as well... Thanks for referring to it. Geert ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: building master
> On Apr 22, 2017, at 3:47 PM, Alex Aycinena <alex.aycin...@gmail.com> wrote: > >> >> -- Forwarded message -- >> From: Geert Janssens <geert.gnuc...@kobaltwit.be> >> To: gnucash-devel@gnucash.org, Wm <wm_o_...@yahoo.co.uk> >> Cc: >> Bcc: >> Date: Sat, 22 Apr 2017 14:40:56 +0200 >> Subject: Re: building master >> On vrijdag 21 april 2017 23:17:31 CEST Wm via gnucash-devel wrote: >>> On 21/04/2017 19:21, John Ralls wrote: >>>> Alex, >>>> >>>> >>>> Looks like autotools picked the wrong compiler for a C++ object. See >>>> http://stackoverflow.com/questions/6045809/link-error- >> undefined-reference >>>> -to-gxx-personality-v0-and-g. Geert and I have both switched to cmake & >>>> ninja-build; there's no issue there so it might be a typo in that >>>> directory's Makefile.am. >>>> >>>> On the other hand Geert just merged his C++ rewrite of >>>> src/import-export/imp-csv, so if you have installed libs that are >> getting >>>> linked in that could cause the error too. >>> I've had intermittent difficulty with builds too recently but haven't >>> said anything because I'm not building gnc for any particular purpose. >>> >> What errors do you see Wm ? >> >>> I have noticed the cmake / ninja combo has been mentioned more than one >>> recently here. >>> >>> Should others that build-because-we-do-it-anyway be switching and is >>> there a suggested "start reading here" ref you could suggest? >>> >> We have a wiki page on CMake [1]. It's been written quite some time ago, >> but it still looks like a >> good starting point. At that time ninja wasn't written yet so that >> information is currently missing. >> >> In short cmake replaces automake/autoconf and the configuration script >> that's generated by >> those. It will produce build recipes for different build systems. The wiki >> page explains how to >> make these recipes for the gnu-make build system (which is the only build >> system supported by >> automake/autoconf by the way). So using cmake like this will generate >> Makefile files which can >> be used just like before by running make, make install, make check,... >> >> Ninja on the other hand is an alternative for gnu-make with a strong focus >> on parallellizing the >> build as much as possible, and as such utilizing your typical multi-core >> cpu much more >> efficiently. The commands to use it are similar to gnu-make: >> make -> ninja (or ninja-build) >> make install -> ninja (or ninja-build) install >> make check -> ninja (or ninja-build) check >> >> I'm writing "ninja (or ninja-build)" because the name of the command >> depends on your OS. On >> Windows it's "ninja", on Fedora it's "ninja-build". Oh, well... >> >> To instruct cmake to set up for ninja instead of gnu-make, you invoke >> cmake with "-G Ninja" >> added to the options. As an example my current cmake command looks like >> this: >> cmake -D WITH_PYTHON=ON \ >> -D CMAKE_INSTALL_PREFIX= \ >> -DCMAKE_BUILD_TYPE=Debug -DWITH_AQBANKING=ON -G Ninja \ >> >> >> >> >> After that short intro, a few words on where to go next: because of the >> better performance and >> greater flexibility in build system support (even Ms Visual Studio is >> supported by cmake), we are >> seriously considering to switch to cmake in favor of autotools at some >> point. >> >> We won't do so for the stable 2.6 series (although even that builds fine >> with cmake/ninja >> already; the combo is in active use for our Windows nightly builds). For >> the upcoming 2.8 >> though it's very likely we will formally switch to cmake. There are a few >> release related details >> which still need to be ported to cmake before that switch can be complete >> though. >> >> So for now we're formally supporting autotools/gnu-make and informally >> cmake/ in >> which John and I currently prefer to be ninja for its >> performance. >> >>> I'm building on Ubuntu LTS if it matters ... and it shouldn't really >>> matter as I'm just building to keep in touch. >> >> You didn't mention which LTS edition. However on my 14.04LTS ninja is >> already available, so I >> expect it to be in 16.04 as well. >> >> Regards, >> >> Geert >> >> [1] http:/
Re: building master
> > -- Forwarded message -- > From: Geert Janssens <geert.gnuc...@kobaltwit.be> > To: gnucash-devel@gnucash.org, Wm <wm_o_...@yahoo.co.uk> > Cc: > Bcc: > Date: Sat, 22 Apr 2017 14:40:56 +0200 > Subject: Re: building master > On vrijdag 21 april 2017 23:17:31 CEST Wm via gnucash-devel wrote: > > On 21/04/2017 19:21, John Ralls wrote: > > > Alex, > > > > > > > > > Looks like autotools picked the wrong compiler for a C++ object. See > > > http://stackoverflow.com/questions/6045809/link-error- > undefined-reference > > > -to-gxx-personality-v0-and-g. Geert and I have both switched to cmake & > > > ninja-build; there's no issue there so it might be a typo in that > > > directory's Makefile.am. > > > > > > On the other hand Geert just merged his C++ rewrite of > > > src/import-export/imp-csv, so if you have installed libs that are > getting > > > linked in that could cause the error too. > > I've had intermittent difficulty with builds too recently but haven't > > said anything because I'm not building gnc for any particular purpose. > > > What errors do you see Wm ? > > > I have noticed the cmake / ninja combo has been mentioned more than one > > recently here. > > > > Should others that build-because-we-do-it-anyway be switching and is > > there a suggested "start reading here" ref you could suggest? > > > We have a wiki page on CMake [1]. It's been written quite some time ago, > but it still looks like a > good starting point. At that time ninja wasn't written yet so that > information is currently missing. > > In short cmake replaces automake/autoconf and the configuration script > that's generated by > those. It will produce build recipes for different build systems. The wiki > page explains how to > make these recipes for the gnu-make build system (which is the only build > system supported by > automake/autoconf by the way). So using cmake like this will generate > Makefile files which can > be used just like before by running make, make install, make check,... > > Ninja on the other hand is an alternative for gnu-make with a strong focus > on parallellizing the > build as much as possible, and as such utilizing your typical multi-core > cpu much more > efficiently. The commands to use it are similar to gnu-make: > make -> ninja (or ninja-build) > make install -> ninja (or ninja-build) install > make check -> ninja (or ninja-build) check > > I'm writing "ninja (or ninja-build)" because the name of the command > depends on your OS. On > Windows it's "ninja", on Fedora it's "ninja-build". Oh, well... > > To instruct cmake to set up for ninja instead of gnu-make, you invoke > cmake with "-G Ninja" > added to the options. As an example my current cmake command looks like > this: > cmake -D WITH_PYTHON=ON \ > -D CMAKE_INSTALL_PREFIX= \ > -DCMAKE_BUILD_TYPE=Debug -DWITH_AQBANKING=ON -G Ninja \ > > > > > After that short intro, a few words on where to go next: because of the > better performance and > greater flexibility in build system support (even Ms Visual Studio is > supported by cmake), we are > seriously considering to switch to cmake in favor of autotools at some > point. > > We won't do so for the stable 2.6 series (although even that builds fine > with cmake/ninja > already; the combo is in active use for our Windows nightly builds). For > the upcoming 2.8 > though it's very likely we will formally switch to cmake. There are a few > release related details > which still need to be ported to cmake before that switch can be complete > though. > > So for now we're formally supporting autotools/gnu-make and informally > cmake/ in > which John and I currently prefer to be ninja for its > performance. > > > I'm building on Ubuntu LTS if it matters ... and it shouldn't really > > matter as I'm just building to keep in touch. > > You didn't mention which LTS edition. However on my 14.04LTS ninja is > already available, so I > expect it to be in 16.04 as well. > > Regards, > > Geert > > [1] http://wiki.gnucash.org/wiki/CMake > > So to switch to using cmake with ninja, I installed cmake (which installed cmake-data and jsoncpp, as well) and ninja-build (on Fedora). But from your note, it was still unclear to me how to use them. Up to now, I have had two parallel directories, for example, gnucash-clean, where the source is checked out to, and gnucash-clean-build, where I build. Then I would: $ cd /home/gnucash-dev/gitcheckouts/gnucash-clean $ git pull $ ./autogen.sh $ cd /home/gnucash-dev/gi
Re: building master
On vrijdag 21 april 2017 23:17:31 CEST Wm via gnucash-devel wrote: > On 21/04/2017 19:21, John Ralls wrote: > > Alex, > > > > > > Looks like autotools picked the wrong compiler for a C++ object. See > > http://stackoverflow.com/questions/6045809/link-error-undefined-reference > > -to-gxx-personality-v0-and-g. Geert and I have both switched to cmake & > > ninja-build; there's no issue there so it might be a typo in that > > directory's Makefile.am. > > > > On the other hand Geert just merged his C++ rewrite of > > src/import-export/imp-csv, so if you have installed libs that are getting > > linked in that could cause the error too. > I've had intermittent difficulty with builds too recently but haven't > said anything because I'm not building gnc for any particular purpose. > What errors do you see Wm ? > I have noticed the cmake / ninja combo has been mentioned more than one > recently here. > > Should others that build-because-we-do-it-anyway be switching and is > there a suggested "start reading here" ref you could suggest? > We have a wiki page on CMake [1]. It's been written quite some time ago, but it still looks like a good starting point. At that time ninja wasn't written yet so that information is currently missing. In short cmake replaces automake/autoconf and the configuration script that's generated by those. It will produce build recipes for different build systems. The wiki page explains how to make these recipes for the gnu-make build system (which is the only build system supported by automake/autoconf by the way). So using cmake like this will generate Makefile files which can be used just like before by running make, make install, make check,... Ninja on the other hand is an alternative for gnu-make with a strong focus on parallellizing the build as much as possible, and as such utilizing your typical multi-core cpu much more efficiently. The commands to use it are similar to gnu-make: make -> ninja (or ninja-build) make install -> ninja (or ninja-build) install make check -> ninja (or ninja-build) check I'm writing "ninja (or ninja-build)" because the name of the command depends on your OS. On Windows it's "ninja", on Fedora it's "ninja-build". Oh, well... To instruct cmake to set up for ninja instead of gnu-make, you invoke cmake with "-G Ninja" added to the options. As an example my current cmake command looks like this: cmake -D WITH_PYTHON=ON \ -D CMAKE_INSTALL_PREFIX= \ -DCMAKE_BUILD_TYPE=Debug -DWITH_AQBANKING=ON -G Ninja \ After that short intro, a few words on where to go next: because of the better performance and greater flexibility in build system support (even Ms Visual Studio is supported by cmake), we are seriously considering to switch to cmake in favor of autotools at some point. We won't do so for the stable 2.6 series (although even that builds fine with cmake/ninja already; the combo is in active use for our Windows nightly builds). For the upcoming 2.8 though it's very likely we will formally switch to cmake. There are a few release related details which still need to be ported to cmake before that switch can be complete though. So for now we're formally supporting autotools/gnu-make and informally cmake/ in which John and I currently prefer to be ninja for its performance. > I'm building on Ubuntu LTS if it matters ... and it shouldn't really > matter as I'm just building to keep in touch. You didn't mention which LTS edition. However on my 14.04LTS ninja is already available, so I expect it to be in 16.04 as well. Regards, Geert [1] http://wiki.gnucash.org/wiki/CMake ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: building master
On vrijdag 21 april 2017 20:21:39 CEST John Ralls wrote: > > On Apr 21, 2017, at 10:00 AM, Alex Aycinena> > wrote: > > > > Hi, > > > > I have been unable to spend any time on gnucash for several weeks but am > > about to get started again. I checked out master anew but when I tried to > > build it, I get: > > > > /usr/bin/ld: > > ../../../src/engine/test-core/.libs/libgncmod-test-engine.a(test-engine-st > > uff.o): undefined reference to symbol '__gxx_personality_v0@@CXXABI_1.3' > > /usr/lib64/libstdc++.so.6: error adding symbols: DSO missing from command > > line > > collect2: error: ld returned 1 exit status > > Makefile:839: recipe for target 'test-import-pending-matches' failed > > make[4]: *** [test-import-pending-matches] Error 1 > > make[4]: Leaving directory > > '/home/gnucash-dev/gitcheckouts/gnucash-clean-new-build/src/import-export/ > > test' > > > > This is on Fedora 25 and I know Geert does his development on Fedora. Is > > anybody else seeing this? Is there a new dependency that has been added > > that I missed? > > Alex, > > > Looks like autotools picked the wrong compiler for a C++ object. See > http://stackoverflow.com/questions/6045809/link-error-undefined-reference-t > o-gxx-personality-v0-and-g. Geert and I have both switched to cmake & > ninja-build; there's no issue there so it might be a typo in that > directory's Makefile.am. > It doesn't look like a cmake vs autotools issue. I have rebuilt a clean checkout with autotools this morning and didn't run into the above. I had to set an environment variable TZ to "America/Los_Angeles" to get test-gnc- datetime to pass, but with current master I have to do this as well with cmake/ninja. > On the other hand Geert just merged his C++ rewrite of > src/import-export/imp-csv, so if you have installed libs that are getting > linked in that could cause the error too. I didn't test this. I have no system install of gnucash right now. Geert ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: building master
On 21/04/2017 19:21, John Ralls wrote: > Alex, > > > Looks like autotools picked the wrong compiler for a C++ object. See > http://stackoverflow.com/questions/6045809/link-error-undefined-reference-to-gxx-personality-v0-and-g. > Geert and I have both switched to cmake & ninja-build; there's no issue > there so it might be a typo in that directory's Makefile.am. > > On the other hand Geert just merged his C++ rewrite of > src/import-export/imp-csv, so if you have installed libs that are getting > linked in that could cause the error too. I've had intermittent difficulty with builds too recently but haven't said anything because I'm not building gnc for any particular purpose. I have noticed the cmake / ninja combo has been mentioned more than one recently here. Should others that build-because-we-do-it-anyway be switching and is there a suggested "start reading here" ref you could suggest? I'm building on Ubuntu LTS if it matters ... and it shouldn't really matter as I'm just building to keep in touch. -- Wm ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: building master
> On Apr 21, 2017, at 10:00 AM, Alex Aycinenawrote: > > Hi, > > I have been unable to spend any time on gnucash for several weeks but am > about to get started again. I checked out master anew but when I tried to > build it, I get: > > /usr/bin/ld: > ../../../src/engine/test-core/.libs/libgncmod-test-engine.a(test-engine-stuff.o): > undefined reference to symbol '__gxx_personality_v0@@CXXABI_1.3' > /usr/lib64/libstdc++.so.6: error adding symbols: DSO missing from command > line > collect2: error: ld returned 1 exit status > Makefile:839: recipe for target 'test-import-pending-matches' failed > make[4]: *** [test-import-pending-matches] Error 1 > make[4]: Leaving directory > '/home/gnucash-dev/gitcheckouts/gnucash-clean-new-build/src/import-export/test' > > This is on Fedora 25 and I know Geert does his development on Fedora. Is > anybody else seeing this? Is there a new dependency that has been added > that I missed? Alex, Looks like autotools picked the wrong compiler for a C++ object. See http://stackoverflow.com/questions/6045809/link-error-undefined-reference-to-gxx-personality-v0-and-g. Geert and I have both switched to cmake & ninja-build; there's no issue there so it might be a typo in that directory's Makefile.am. On the other hand Geert just merged his C++ rewrite of src/import-export/imp-csv, so if you have installed libs that are getting linked in that could cause the error too. Regards, John Ralls ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
building master
Hi, I have been unable to spend any time on gnucash for several weeks but am about to get started again. I checked out master anew but when I tried to build it, I get: /usr/bin/ld: ../../../src/engine/test-core/.libs/libgncmod-test-engine.a(test-engine-stuff.o): undefined reference to symbol '__gxx_personality_v0@@CXXABI_1.3' /usr/lib64/libstdc++.so.6: error adding symbols: DSO missing from command line collect2: error: ld returned 1 exit status Makefile:839: recipe for target 'test-import-pending-matches' failed make[4]: *** [test-import-pending-matches] Error 1 make[4]: Leaving directory '/home/gnucash-dev/gitcheckouts/gnucash-clean-new-build/src/import-export/test' This is on Fedora 25 and I know Geert does his development on Fedora. Is anybody else seeing this? Is there a new dependency that has been added that I missed? Thanks for any feedback. Alex ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: building master with boost
On Sat, Nov 1, 2014 at 2:42 PM, Carsten Rinke carsten.ri...@gmx.de wrote: Hi, to check if some front-porting is working, I tried to compile on the master branch - for the first time. It told me that boost is missing: checking for boostlib = 1.48.0... configure: We could not detect the boost libraries (version 1.48 or higher). If you have a staged boost library (still not installed) please specify $BOOST_ROOT in your environment and do not give a PATH to --with-boost option. If you are sure you have boost installed, then check your version number looking in boost/version.hpp. See http://randspringer.de/boost for more documentation. configure: error: Boost 1.48.0 or later was not found and is required to build GnuCash So I downloaded Boost 1.56.0 into /opt/lib/boost/boost_1_56_0. Running configure with an environment variable echo $BOOST_ROOT - /opt/lib/boost/boost_1_56_0 does not change anything. Running configure with --with-boost /opt/lib/boost/boost_1_56_0 results in: checking build system type... Invalid configuration `/opt/lib/boost/boost_1_56_0': machine `/opt/lib/boost/boost_1_56_0' not recognized configure: error: /bin/bash ../config.sub /opt/lib/boost/boost_1_56_0 failed What can I do? Kind regards, Carsten ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel I do a similar thing, and here is what I pass to configure: ./configure --with-boost=/home/lmat/builds/development (I trimmed out a dozen lines, but this should get to the gist of the matter.) I built boost with #!/bin/bash cd boostsvn ./bootstrap.sh --prefix=/home/lmat/builds/development ./b2 install I don't set BOOST_ROOT. Hopefully this helps? In Christ, Aaron Laws ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: building master with boost
Thanks for all feedback. Finally I managed: - I installed the library with the help from John and Aaron - and I also used the = as indicated by Geert. - Works all fine now :-) Carsten On 03.11.2014 16:50, Aaron Laws wrote: On Sat, Nov 1, 2014 at 2:42 PM, Carsten Rinke carsten.ri...@gmx.de mailto:carsten.ri...@gmx.de wrote: Hi, to check if some front-porting is working, I tried to compile on the master branch - for the first time. It told me that boost is missing: checking for boostlib = 1.48.0... configure: We could not detect the boost libraries (version 1.48 or higher). If you have a staged boost library (still not installed) please specify $BOOST_ROOT in your environment and do not give a PATH to --with-boost option. If you are sure you have boost installed, then check your version number looking in boost/version.hpp. See http://randspringer.de/boost for more documentation. configure: error: Boost 1.48.0 or later was not found and is required to build GnuCash So I downloaded Boost 1.56.0 into /opt/lib/boost/boost_1_56_0. Running configure with an environment variable echo $BOOST_ROOT - /opt/lib/boost/boost_1_56_0 does not change anything. Running configure with --with-boost /opt/lib/boost/boost_1_56_0 results in: checking build system type... Invalid configuration `/opt/lib/boost/boost_1_56_0': machine `/opt/lib/boost/boost_1_56_0' not recognized configure: error: /bin/bash ../config.sub /opt/lib/boost/boost_1_56_0 failed What can I do? Kind regards, Carsten ___ gnucash-devel mailing list gnucash-devel@gnucash.org mailto:gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel I do a similar thing, and here is what I pass to configure: ./configure --with-boost=/home/lmat/builds/development (I trimmed out a dozen lines, but this should get to the gist of the matter.) I built boost with #!/bin/bash cd boostsvn ./bootstrap.sh --prefix=/home/lmat/builds/development ./b2 install I don't set BOOST_ROOT. Hopefully this helps? In Christ, Aaron Laws ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
building master with boost
Hi, to check if some front-porting is working, I tried to compile on the master branch - for the first time. It told me that boost is missing: checking for boostlib = 1.48.0... configure: We could not detect the boost libraries (version 1.48 or higher). If you have a staged boost library (still not installed) please specify $BOOST_ROOT in your environment and do not give a PATH to --with-boost option. If you are sure you have boost installed, then check your version number looking in boost/version.hpp. See http://randspringer.de/boost for more documentation. configure: error: Boost 1.48.0 or later was not found and is required to build GnuCash So I downloaded Boost 1.56.0 into /opt/lib/boost/boost_1_56_0. Running configure with an environment variable echo $BOOST_ROOT - /opt/lib/boost/boost_1_56_0 does not change anything. Running configure with --with-boost /opt/lib/boost/boost_1_56_0 results in: checking build system type... Invalid configuration `/opt/lib/boost/boost_1_56_0': machine `/opt/lib/boost/boost_1_56_0' not recognized configure: error: /bin/bash ../config.sub /opt/lib/boost/boost_1_56_0 failed What can I do? Kind regards, Carsten ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: building master with boost
On Nov 1, 2014, at 11:42 AM, Carsten Rinke carsten.ri...@gmx.de wrote: Hi, to check if some front-porting is working, I tried to compile on the master branch - for the first time. It told me that boost is missing: checking for boostlib = 1.48.0... configure: We could not detect the boost libraries (version 1.48 or higher). If you have a staged boost library (still not installed) please specify $BOOST_ROOT in your environment and do not give a PATH to --with-boost option. If you are sure you have boost installed, then check your version number looking in boost/version.hpp. See http://randspringer.de/boost for more documentation. configure: error: Boost 1.48.0 or later was not found and is required to build GnuCash So I downloaded Boost 1.56.0 into /opt/lib/boost/boost_1_56_0. Running configure with an environment variable echo $BOOST_ROOT - /opt/lib/boost/boost_1_56_0 does not change anything. Running configure with --with-boost /opt/lib/boost/boost_1_56_0 results in: checking build system type... Invalid configuration `/opt/lib/boost/boost_1_56_0': machine `/opt/lib/boost/boost_1_56_0' not recognized configure: error: /bin/bash ../config.sub /opt/lib/boost/boost_1_56_0 failed What can I do? Read http://www.boost.org/doc/libs/release/more/getting_started/index.html. Study macros/m4_ax_boost_base.m4 to see what causes that error message and what configure is looking for, then make sure that you installed boost in a way that it finds it. Did you build boost or just untar it in that directory? Regards, John Ralls ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: building master with boost
On Saturday 01 November 2014 19:42:59 Carsten Rinke wrote: Hi, to check if some front-porting is working, I tried to compile on the master branch - for the first time. It told me that boost is missing: checking for boostlib = 1.48.0... configure: We could not detect the boost libraries (version 1.48 or higher). If you have a staged boost library (still not installed) please specify $BOOST_ROOT in your environment and do not give a PATH to --with-boost option. If you are sure you have boost installed, then check your version number looking in boost/version.hpp. See http://randspringer.de/boost for more documentation. configure: error: Boost 1.48.0 or later was not found and is required to build GnuCash So I downloaded Boost 1.56.0 into /opt/lib/boost/boost_1_56_0. Running configure with an environment variable echo $BOOST_ROOT - /opt/lib/boost/boost_1_56_0 does not change anything. Running configure with --with-boost /opt/lib/boost/boost_1_56_0 results in: checking build system type... Invalid configuration `/opt/lib/boost/boost_1_56_0': machine `/opt/lib/boost/boost_1_56_0' not recognized configure: error: /bin/bash ../config.sub /opt/lib/boost/boost_1_56_0 failed What can I do? Would --with-boost=/opt/lib/boost/boost_1_56_0 work ? It seems to me there should be an = sign after the option. Geert ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel