Opened 10 days ago
Last modified 7 days ago
#69835 assigned defect
gnucash: Build error on El Capitan
| Reported by: | gpz500 (Alessandro Morgantini) | Owned by: | drkp (Dan Ports) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | |
| Keywords: | Cc: | ||
| Port: | gnucash |
Description
Versions 5.5 and 5.6 of gnucash fail to build on El Capitan, with the command 'sudo port install gnucash'. It seems a common problem because there isn't any binary packages compiled for El Capitan.
After some try, enabling the trace mode 'sudo port -t install gnucash' builds correctly. Could this be the default on El Capitan?
Attachments (2)
Change History (6)
comment:1 Changed 10 days ago by ryandesign (Ryan Carsten Schmidt)
| Owner: | set to drkp |
|---|---|
| Status: | new → assigned |
| Summary: | Build error on El Capitan → gnucash: Build error on El Capitan |
Changed 8 days ago by gpz500 (Alessandro Morgantini)
comment:2 follow-up: 3 Changed 8 days ago by gpz500 (Alessandro Morgantini)
Thank you so much for your prompt response: I attached the main.log file from my failed build. Anyway, it seems that neither your buildbot workers are able to build for El Capitan (I can't see https://build.macports.org/builders/ports-10.11_x86_64-builder/builds/259212/steps/install-port/logs/main.log to compare with mine...).
comment:3 Changed 7 days ago by ryandesign (Ryan Carsten Schmidt)
Replying to gpz500:
Thank you so much for your prompt response: I attached the main.log file from my failed build. Anyway, it seems that neither your buildbot workers are able to build for El Capitan (I can't see https://build.macports.org/builders/ports-10.11_x86_64-builder/builds/259212/steps/install-port/logs/main.log to compare with mine...).
The error in both your log and that buildbot log was:
libc++abi: terminating with uncaught exception of type boost::wrapexcept<std::invalid_argument>
So it doesn't make sense to me that using trace mode would have worked around the problem for you. The purpose of trace mode is to hide files that are not from dependencies of the port. On the buildbot, ports that are not dependencies are not active so problems that would be solved by trace mode should not be possible in the first place.
Changed 7 days ago by gpz500 (Alessandro Morgantini)
| Attachment: | main_trace.log added |
|---|
main.log for trace mode, successful build
comment:4 Changed 7 days ago by gpz500 (Alessandro Morgantini)
I added main_trace.log (obtained with command 'sudo port -k -t install gnucash') from my successful build. At lines 9526-9529 there is a list of excluded files:
[...] :warn:configure The following existing files were hidden from the build system by trace mode: :msg:configure /opt :msg:configure /opt/local/lib/perl5/vendor_perl/5.34/darwin-thread-multi-2level/Time/HiRes.pm :msg:configure /usr/X11R6 [...]
Could the problem be in one of these items?
No, there is no feature for enabling trace mode from a Portfile. It can only be enabled from the command line.
If the build succeeded in trace mode, that suggests some other port you had installed, that is not a dependency of gnucash, is causing it to fail to build. Please attach the main.log file from the failed build so that we can investigate.
The same problem should not affect our buildbot workers because they ensure that all ports that are not dependencies are deactivated before performing a build.