2.0.4 crash
Donald Allen
donaldcallen at gmail.com
Mon Feb 12 11:32:12 EST 2007
On 2/12/07, Josh Sled <jsled at asynchronous.org> wrote:
>
> On Mon, 2007-02-12 at 11:14 -0500, Donald Allen wrote:
> >
> >
> > On 2/12/07, Derek Atkins <warlord at mit.edu> wrote:
> > "Donald Allen" <donaldcallen at gmail.com> writes:
> >
> > > With g-wrap-1.9.6-r1 in place, I tried to emerge gnucash
> > 2.0.4-r1 and got
> > >
> > > cannot find g-wrap-wct.h where g-wrap claims it should
> > be.
> > > are you on Debian or Ubuntu and still using g-wrap
> > 1.9.6-2?
> > > See: http://bugzilla.gnome.org/show_bug.cgi?id=330539
> >
> > What did config.log say?
> >
> > A lot. But the interesting part would seem to be:
> >
> > configure:25945: i686-pc-linux-gnu-gcc -c -O2 -march=pentium4
> > -std=gnu99 conftest.c >&5
> > In file included from /usr/include/g-wrap/ffi-support.h:24,
> [...]
>
> See <http://bugs.gentoo.org/show_bug.cgi?id=125468#c22>.
>
> g-wrap has a (really) bad interaction with libffi on the system. The
> workaround is to emerge g-wrap an odd number of times. :(
Oh, of course, the obvious. Why didn't *I* think of that?-)
The comment
> there mentions 1.9.7, but it applies to 1.9.6 as well.
As I said before, I think I'll wait for stable 2.0.4 unless you think some
really important bug got fixed since 2.0.1 (I did a quick scan of the
release notes and didn't see anything that looked like it would matter a lot
to me). Also 2.0.1 read the file written by 2.0.4 and seems to be happy (I
assume there's a fair amount of sanity-checking that happens when the file
is read and if the file were corrupted, I'd probably have heard about it).
/Don
--
> ...jsled
> http://asynchronous.org/ - a=jsled;b=asynchronous.org;echo ${a}@${b}
>
>
More information about the gnucash-user
mailing list