> >the dependencies on nana, if you're willing. It would be nice to see
> >if current CVS can compile on FreeBSD.
>
> The only problem I've had with the current CVS on FreeBSD 3.4
> is in configure.in:
> ${MAKE-make} -f Makefile.config.finish)
> doesn't seem to set ${MAKE-make} to gmake. I
> Am I doing something wrong ?
>
> I just applied the latest bigpatch and the error dialog for report
> error still just says "Error executing scheme report" with no
> information about the error. Was there another patch that I missed ?
No, that patch should have the error catching code. Could
Am I doing something wrong ?
I just applied the latest bigpatch and the error dialog for report
error still just says "Error executing scheme report" with no
information about the error. Was there another patch that I missed ?
Debugging my attempts at report code is very slow without knowing w
>the dependencies on nana, if you're willing. It would be nice to see
>if current CVS can compile on FreeBSD.
The only problem I've had with the current CVS on FreeBSD 3.4
is in configure.in:
${MAKE-make} -f Makefile.config.finish)
doesn't seem to set ${MAKE-make} to gmake. I haven't had a
David Bobroff writes:
> In response to a list of troubles (.qif import failure, odd behavior of
> dialog boxes, and ominous messages when starting Gnucash) Dave Peticolas said:
>
> >Ok, that is definitely caused by the version of lesstif you are using.
> >If you don't want to recompile, unin
In response to a list of troubles (.qif import failure, odd behavior of
dialog boxes, and ominous messages when starting Gnucash) Dave Peticolas said:
>Ok, that is definitely caused by the version of lesstif you are using.
>If you don't want to recompile, uninstall the version of lesstif you
>hav