Bug 205547 - finance/gnucash: does not build, abort segmentation fault
Summary: finance/gnucash: does not build, abort segmentation fault
Status: Closed Feedback Timeout
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: Guido Falsi
URL:
Keywords: crash, needs-qa
Depends on:
Blocks:
 
Reported: 2015-12-23 17:27 UTC by lenzi.sergio
Modified: 2016-01-25 10:48 UTC (History)
3 users (show)

See Also:
madpilot: maintainer-feedback+


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description lenzi.sergio 2015-12-23 17:27:02 UTC

    
Comment 1 lenzi.sergio 2015-12-23 17:31:16 UTC
latest gnucash 2.6.10
does not build on FreeBSD 10.0 RELEASE



GNC_MODULE_PATH="../../src/engine/.libs:${GNC_MODULE_PATH}" GUILE_LOAD_PATH="../../src/app-utils:../../src/core-utils:../../src/engine:../../src/gnc-module:../../src/scm:${GUILE_LOAD_PATH}" GUILE_LOAD_COMPILED_PATH="../../src/app-utils:../../src/core-utils:../../src/engine:../../src/gnc-module:../../src/scm:${GUILE_LOAD_COMPILED_PATH}" LD_LIBRARY_PATH="../../src/libqof/qof/.libs:../../src/core-utils/.libs:../../src/gnc-module/.libs:../../src/engine/.libs:../../src/app-utils/.libs:${LD_LIBRARY_PATH}" DYLD_LIBRARY_PATH="../../src/libqof/qof/.libs:../../src/core-utils/.libs:../../src/gnc-module/.libs:../../src/engine/.libs:../../src/app-utils/.libs:${DYLD_LIBRARY_PATH}"  \
/usr/local/bin/guild compile -o prefs.go prefs.scm
Makefile:1304: recipe for target 'business-prefs.go' failed
gmake[6]: *** [business-prefs.go] Segmentation fault
Comment 2 Guido Falsi freebsd_committer freebsd_triage 2015-12-23 17:59:12 UTC
Hi,

Can you attach a full log for the build failure? (you can use script(1) to do that)

Can you also test the build a few times to make sure it always fails at the same point in the build?

Also, since the binary segfaulting is guile, could you try recompiling the guile port (lang/guile or lang/guile2 if you're using the guile2 option)

As a final note, FreeBSD 10.0 isn't supported anymore, you should really upgrade to 10.1 at least. While I can't say this is the cause of the problem, you could try on a 10.1 install if it works correctly.

Thanks.
Comment 3 lenzi.sergio 2015-12-26 22:01:20 UTC
(In reply to Guido Falsi from comment #2)

Sorry for the delay. I installed a CLEAN Freebsd 10.0 RELEASE and build the ports from scratch... using the command portmaster finace/gnucash... (12 hours after....)  it builds and works as expected... 
But in a system with 1872 ports compiled in, it does not build at all.


What can I say????
Comment 4 Guido Falsi freebsd_committer freebsd_triage 2015-12-27 09:40:05 UTC
This information indicates it's a local problem on your machine. I'm changing the importance of this bug accordingly.

One (or some) of the ports being used to build gnucash is corrupted on that machine. You don't need to recompile all 1800 ports installed there, but to identify the few ones that need rebuilding.

As I already said, the executable actually dieing during the build is /usr/local/bin/guild, so first of all you should try rebuilding the port installing it (lang/guile).

Another port used during the build that could be causing problems is lang/slib-guile, this port also depends on lang/slib.

So try recompiling lang/guile, lang/slib-guile and lang/slib, then recompiling gnucash, and see what happens. If it still fails There are also other ports you could try recompiling in that dependency chain (for example I'd try recompiling also math/gmp and devel/libltdl if needed).

To give you any further help I need the full build log.


I also strongly suggest you upgrade to 10.1 or 10.2 anyway.
Comment 5 Guido Falsi freebsd_committer freebsd_triage 2016-01-06 10:53:10 UTC
Hi, Have you got any further feedback?

Did you try recompiling just the ports I suggested? Did that make a difference?

Thanks.
Comment 6 Guido Falsi freebsd_committer freebsd_triage 2016-01-25 10:48:28 UTC
Closing due to missing timeout about resolution. No other user reported similar issues.