2.0.4 crash

classic Classic list List threaded Threaded
10 messages Options
Reply | Threaded
Open this post in threaded view
|

2.0.4 crash

Donald Allen
I am running gnucash 2.0.4 on an up-to-date Gentoo system. Today, I was
updating my financial records, which included the purchase of a municipal
bond in an investment account. First, I created the bond and associated
commodity under the brokerage asset account and then the income subaccount
for the interest from the bond. I then went back to the brokerage account,
which is where the cash lives, and attempted to enter a transaction paying
the accrued interest to the interest income account. I have had accrued
interest transactions before in this account, so I typed some part of
'accrued' and hit 'tab'. It completed the description and promptly crashed.
I then repeated the foregoing, saving after each step, and the crash
occurred again. I brought up gnucash yet again, and this time the steps
preliminary to entering the accrued interest transaction weren't necessary.
So I entered the accrued interest transaction exactly the same way and this
time I was able to proceed without any problem. So something about those
preliminary steps would seem to have planted a time-bomb in the internal
data-structures, seemingly without corrupting the saved data file (I did run
a check-and-repair and as near as I can tell by comparing the gunzipped
before-and-after files, it did a little fiddling with a transaction from
several years ago and that's all).

This warrants a bug report, though I'm not really sure how useful that would
be, since I can't help the developers reproduce it without providing  the
file with my complete financial history, which I'm obviously not willing to
do. I could try to reproduce this with a new set of fictitious accounts. But
I thought I'd post this here first, in case Derek or one of the other
developers has an idea what the problem might be, in which case I wouldn't
need to bother trying to reproduce it.

/Don Allen
_______________________________________________
gnucash-user mailing list
[hidden email]
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.
Reply | Threaded
Open this post in threaded view
|

Re: 2.0.4 crash

Derek Atkins
Hi,

Unless you were to acquire a stacktrace (or be able to reproduce the
crash) I don't know how useful this report would be, I'm afraid.

-derek

"Donald Allen" <[hidden email]> writes:

> I am running gnucash 2.0.4 on an up-to-date Gentoo system. Today, I was
> updating my financial records, which included the purchase of a municipal
> bond in an investment account. First, I created the bond and associated
> commodity under the brokerage asset account and then the income subaccount
> for the interest from the bond. I then went back to the brokerage account,
> which is where the cash lives, and attempted to enter a transaction paying
> the accrued interest to the interest income account. I have had accrued
> interest transactions before in this account, so I typed some part of
> 'accrued' and hit 'tab'. It completed the description and promptly crashed.
> I then repeated the foregoing, saving after each step, and the crash
> occurred again. I brought up gnucash yet again, and this time the steps
> preliminary to entering the accrued interest transaction weren't necessary.
> So I entered the accrued interest transaction exactly the same way and this
> time I was able to proceed without any problem. So something about those
> preliminary steps would seem to have planted a time-bomb in the internal
> data-structures, seemingly without corrupting the saved data file (I did run
> a check-and-repair and as near as I can tell by comparing the gunzipped
> before-and-after files, it did a little fiddling with a transaction from
> several years ago and that's all).
>
> This warrants a bug report, though I'm not really sure how useful that would
> be, since I can't help the developers reproduce it without providing  the
> file with my complete financial history, which I'm obviously not willing to
> do. I could try to reproduce this with a new set of fictitious accounts. But
> I thought I'd post this here first, in case Derek or one of the other
> developers has an idea what the problem might be, in which case I wouldn't
> need to bother trying to reproduce it.
>
> /Don Allen
> _______________________________________________
> gnucash-user mailing list
> [hidden email]
> https://lists.gnucash.org/mailman/listinfo/gnucash-user
> -----
> Please remember to CC this list on all your replies.
> You can do this by using Reply-To-List or Reply-All.
>
>

--
       Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
       Member, MIT Student Information Processing Board  (SIPB)
       URL: http://web.mit.edu/warlord/    PP-ASEL-IA     N1NWH
       [hidden email]                        PGP key available
_______________________________________________
gnucash-user mailing list
[hidden email]
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.
Reply | Threaded
Open this post in threaded view
|

Re: 2.0.4 crash

Donald Allen
Derek --

When I said my system was up-to-date, I should have qualified that with "as
of last weekend". I'm updating again now and I think there was a version
mis-match between gnucash and the guile library, which, if I'm understanding
what the gentoo folks are saying, was the result of a dependency bug that
they've fixed. Once I get things rebuilt, I will attempt the same operations
on my personal data that caused the problem yesterday. It's possible that
what I ran into was a result of this issue. I will let you know what
happens.

/Don

On 2/11/07, Derek Atkins <[hidden email]> wrote:

>
> Hi,
>
> Unless you were to acquire a stacktrace (or be able to reproduce the
> crash) I don't know how useful this report would be, I'm afraid.
>
> -derek
>
> "Donald Allen" <[hidden email]> writes:
>
> > I am running gnucash 2.0.4 on an up-to-date Gentoo system. Today, I was
> > updating my financial records, which included the purchase of a
> municipal
> > bond in an investment account. First, I created the bond and associated
> > commodity under the brokerage asset account and then the income
> subaccount
> > for the interest from the bond. I then went back to the brokerage
> account,
> > which is where the cash lives, and attempted to enter a transaction
> paying
> > the accrued interest to the interest income account. I have had accrued
> > interest transactions before in this account, so I typed some part of
> > 'accrued' and hit 'tab'. It completed the description and promptly
> crashed.
> > I then repeated the foregoing, saving after each step, and the crash
> > occurred again. I brought up gnucash yet again, and this time the steps
> > preliminary to entering the accrued interest transaction weren't
> necessary.
> > So I entered the accrued interest transaction exactly the same way and
> this
> > time I was able to proceed without any problem. So something about those
> > preliminary steps would seem to have planted a time-bomb in the internal
> > data-structures, seemingly without corrupting the saved data file (I did
> run
> > a check-and-repair and as near as I can tell by comparing the gunzipped
> > before-and-after files, it did a little fiddling with a transaction from
> > several years ago and that's all).
> >
> > This warrants a bug report, though I'm not really sure how useful that
> would
> > be, since I can't help the developers reproduce it without
> providing  the
> > file with my complete financial history, which I'm obviously not willing
> to
> > do. I could try to reproduce this with a new set of fictitious accounts.
> But
> > I thought I'd post this here first, in case Derek or one of the other
> > developers has an idea what the problem might be, in which case I
> wouldn't
> > need to bother trying to reproduce it.
> >
> > /Don Allen
> > _______________________________________________
> > gnucash-user mailing list
> > [hidden email]
> > https://lists.gnucash.org/mailman/listinfo/gnucash-user
> > -----
> > Please remember to CC this list on all your replies.
> > You can do this by using Reply-To-List or Reply-All.
> >
> >
>
> --
>        Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
>        Member, MIT Student Information Processing Board  (SIPB)
>        URL: http://web.mit.edu/warlord/    PP-ASEL-IA     N1NWH
>        [hidden email]                        PGP key available
>
_______________________________________________
gnucash-user mailing list
[hidden email]
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.
Reply | Threaded
Open this post in threaded view
|

Re: 2.0.4 crash

Donald Allen
I spent some time trying to get gnucash 2.0.4, guile, and g-wrap built,
failed,  and finally reached the conclusion that when the gentoo folks mark
packages "testing" and mask them for that reason, there probably is a good
reason. I've been aggressive for some time about gnucash versions, unmasking
versions still marked "testing", and have gotten away with it. I think it
finally bit me. So, I undid all that, rebuilt the "stable" gnucash,
2.0.1and associated libraries and, of course, that built without
incident. I then
retried the sequence of operations that crashed gnucash on Saturday, and
that also worked without incident. So, either

a. I didn't reproduce the problem sequence perfectly this morning
b. The crash was due to a bug introduced since 2.0.1
c. The crash was due to version mis-match issues between 2.0.4 and the
libraries that the gentoo folks are still trying to untangle and which is
why 2.0.4 is still marked "testing". I'm guessing this is the answer, in
which case my apologies for polluting this forum with a non-problem.

/Don

On 2/11/07, Donald Allen <[hidden email]> wrote:

>
> Derek --
>
> When I said my system was up-to-date, I should have qualified that with
> "as of last weekend". I'm updating again now and I think there was a version
> mis-match between gnucash and the guile library, which, if I'm understanding
> what the gentoo folks are saying, was the result of a dependency bug that
> they've fixed. Once I get things rebuilt, I will attempt the same operations
> on my personal data that caused the problem yesterday. It's possible that
> what I ran into was a result of this issue. I will let you know what
> happens.
>
> /Don
>
> On 2/11/07, Derek Atkins <[hidden email]> wrote:
> >
> > Hi,
> >
> > Unless you were to acquire a stacktrace (or be able to reproduce the
> > crash) I don't know how useful this report would be, I'm afraid.
> >
> > -derek
> >
> > "Donald Allen" < [hidden email]> writes:
> >
> > > I am running gnucash 2.0.4 on an up-to-date Gentoo system. Today, I
> > was
> > > updating my financial records, which included the purchase of a
> > municipal
> > > bond in an investment account. First, I created the bond and
> > associated
> > > commodity under the brokerage asset account and then the income
> > subaccount
> > > for the interest from the bond. I then went back to the brokerage
> > account,
> > > which is where the cash lives, and attempted to enter a transaction
> > paying
> > > the accrued interest to the interest income account. I have had
> > accrued
> > > interest transactions before in this account, so I typed some part of
> > > 'accrued' and hit 'tab'. It completed the description and promptly
> > crashed.
> > > I then repeated the foregoing, saving after each step, and the crash
> > > occurred again. I brought up gnucash yet again, and this time the
> > steps
> > > preliminary to entering the accrued interest transaction weren't
> > necessary.
> > > So I entered the accrued interest transaction exactly the same way and
> > this
> > > time I was able to proceed without any problem. So something about
> > those
> > > preliminary steps would seem to have planted a time-bomb in the
> > internal
> > > data-structures, seemingly without corrupting the saved data file (I
> > did run
> > > a check-and-repair and as near as I can tell by comparing the
> > gunzipped
> > > before-and-after files, it did a little fiddling with a transaction
> > from
> > > several years ago and that's all).
> > >
> > > This warrants a bug report, though I'm not really sure how useful that
> > would
> > > be, since I can't help the developers reproduce it without
> > providing  the
> > > file with my complete financial history, which I'm obviously not
> > willing to
> > > do. I could try to reproduce this with a new set of fictitious
> > accounts. But
> > > I thought I'd post this here first, in case Derek or one of the other
> > > developers has an idea what the problem might be, in which case I
> > wouldn't
> > > need to bother trying to reproduce it.
> > >
> > > /Don Allen
> > > _______________________________________________
> > > gnucash-user mailing list
> > > [hidden email]
> > > https://lists.gnucash.org/mailman/listinfo/gnucash-user
> > > -----
> > > Please remember to CC this list on all your replies.
> > > You can do this by using Reply-To-List or Reply-All.
> > >
> > >
> >
> > --
> >        Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
> >        Member, MIT Student Information Processing Board  (SIPB)
> >        URL: http://web.mit.edu/warlord/    PP-ASEL-IA     N1NWH
> >        [hidden email]                         PGP key available
> >
>
>
_______________________________________________
gnucash-user mailing list
[hidden email]
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.
Reply | Threaded
Open this post in threaded view
|

Re: 2.0.4 crash

Josh Sled
On Mon, 2007-02-12 at 07:59 -0500, Donald Allen wrote:
> I spent some time trying to get gnucash 2.0.4, guile, and g-wrap built,
> failed,  and finally reached the conclusion that when the gentoo folks mark
> packages "testing" and mask them for that reason, there probably is a good
[...]
> that also worked without incident. So, either
>
> a. I didn't reproduce the problem sequence perfectly this morning
> b. The crash was due to a bug introduced since 2.0.1
> c. The crash was due to version mis-match issues between 2.0.4 and the

Or, maybe:
d. The bug is coincidental to all this.

IIRC, there is an unexplained, low-frequency crash that does exhibit
when tabbing off of a description.  As it's intermittent and hard to
reproduce, it's hard to debug. :/


W.r.t. Gentoo, yes ... unstable can be unstable.  Running ~x86 (or
whatever) system-wide is a bad idea, though (limited) use
of /etc/portage/package.keyword can be useful.  After participating in
some of the package-untanglement, I can suggest that gnucash-2.0.4-r1,
g-wrap-1.9.6-r1, slib-3.1.1 and guile-1.6.7 are a working combination;
as well, it seems, slib-3.1.1-r1 and guile-1.8.1-r1 play nicely
together.  Though, most of these versions are still masked.  In any
case, a stable 2.0.4 should hit the tree soon enough.

--
...jsled
http://asynchronous.org/ - a=jsled;b=asynchronous.org;echo ${a}@${b}

_______________________________________________
gnucash-user mailing list
[hidden email]
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

signature.asc (196 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: 2.0.4 crash

Donald Allen
On 2/12/07, Josh Sled <[hidden email]> wrote:

>
> On Mon, 2007-02-12 at 07:59 -0500, Donald Allen wrote:
> > I spent some time trying to get gnucash 2.0.4, guile, and g-wrap built,
> > failed,  and finally reached the conclusion that when the gentoo folks
> mark
> > packages "testing" and mask them for that reason, there probably is a
> good
> [...]
> > that also worked without incident. So, either
> >
> > a. I didn't reproduce the problem sequence perfectly this morning
> > b. The crash was due to a bug introduced since 2.0.1
> > c. The crash was due to version mis-match issues between 2.0.4 and the
>
> Or, maybe:
> d. The bug is coincidental to all this.
>
> IIRC, there is an unexplained, low-frequency crash that does exhibit
> when tabbing off of a description.  As it's intermittent and hard to
> reproduce, it's hard to debug. :/


Yes, that's certainly possible, though I had no trouble reproducing it on
Saturday.

W.r.t. Gentoo, yes ... unstable can be unstable.  Running ~x86 (or
> whatever) system-wide is a bad idea, though (limited) use
> of /etc/portage/package.keyword can be useful.  After participating in
> some of the package-untanglement, I can suggest that gnucash-2.0.4-r1,
> g-wrap-1.9.6-r1, slib-3.1.1 and guile-1.6.7 are a working combination;
> as well, it seems, slib-3.1.1-r1 and guile-1.8.1-r1 play nicely
> together.  Though, most of these versions are still masked.  In any
> case, a stable 2.0.4 should hit the tree soon enough.


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

That was when I gave up and reverted to 2.0.1. It's certainly possible this
was pilot error, but I think I'll wait for the stable 2.0.4 (thanks for
letting me know that should happen soon), since 2.0.1 looks like it's
working fine.

/Don


--
> ...jsled
> http://asynchronous.org/ - a=jsled;b=asynchronous.org;echo ${a}@${b}
>
>
_______________________________________________
gnucash-user mailing list
[hidden email]
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.
Reply | Threaded
Open this post in threaded view
|

Re: 2.0.4 crash

Derek Atkins
"Donald Allen" <[hidden email]> 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?

-derek
--
       Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
       Member, MIT Student Information Processing Board  (SIPB)
       URL: http://web.mit.edu/warlord/    PP-ASEL-IA     N1NWH
       [hidden email]                        PGP key available
_______________________________________________
gnucash-user mailing list
[hidden email]
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.
Reply | Threaded
Open this post in threaded view
|

Re: 2.0.4 crash

Donald Allen
On 2/12/07, Derek Atkins <[hidden email]> wrote:

>
> "Donald Allen" <[hidden email]> 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,
                 from /usr/include/g-wrap/core-runtime.h:23,
                 from /usr/include/g-wrap/guile-wct.h:23,
                 from /usr/include/g-wrap-wct.h:3,
                 from conftest.c:102:
/usr/lib/gcc/i686-pc-linux-gnu/3.4.6/include/ffi.h:63:23: ffitarget.h: No
such file or directory
In file included from /usr/include/g-wrap/ffi-support.h:24,
                 from /usr/include/g-wrap/core-runtime.h:23,
                 from /usr/include/g-wrap/guile-wct.h:23,
                 from /usr/include/g-wrap-wct.h:3,
                 from conftest.c:102:
/usr/lib/gcc/i686-pc-linux-gnu/3.4.6/include/ffi.h:161: error: syntax error
before "ffi_abi"
/usr/lib/gcc/i686-pc-linux-gnu/3.4.6/include/ffi.h:170: error: syntax error
before '}' token
/usr/lib/gcc/i686-pc-linux-gnu/3.4.6/include/ffi.h:183: error: syntax error
before "ffi_sarg"
/usr/lib/gcc/i686-pc-linux-gnu/3.4.6/include/ffi.h:184: error: syntax error
before "uint"
/usr/lib/gcc/i686-pc-linux-gnu/3.4.6/include/ffi.h:188: error: syntax error
before '}' token
/usr/lib/gcc/i686-pc-linux-gnu/3.4.6/include/ffi.h:190: error: syntax error
before '*' token
/usr/lib/gcc/i686-pc-linux-gnu/3.4.6/include/ffi.h:191: error:
`ffi_raw_call' declared as function returning a function
/usr/lib/gcc/i686-pc-linux-gnu/3.4.6/include/ffi.h:192: error: syntax error
before "void"
/usr/lib/gcc/i686-pc-linux-gnu/3.4.6/include/ffi.h:195: error: syntax error
before '*' token
/usr/lib/gcc/i686-pc-linux-gnu/3.4.6/include/ffi.h:196: error: syntax error
before '*' token
/usr/lib/gcc/i686-pc-linux-gnu/3.4.6/include/ffi.h:197: error: syntax error
before '*' token
/usr/lib/gcc/i686-pc-linux-gnu/3.4.6/include/ffi.h:203: error: syntax error
before '*' token
/usr/lib/gcc/i686-pc-linux-gnu/3.4.6/include/ffi.h:204: error:
`ffi_java_raw_call' declared as function returning a function
/usr/lib/gcc/i686-pc-linux-gnu/3.4.6/include/ffi.h:205: error: syntax error
before "void"
/usr/lib/gcc/i686-pc-linux-gnu/3.4.6/include/ffi.h:208: error: syntax error
before '*' token
/usr/lib/gcc/i686-pc-linux-gnu/3.4.6/include/ffi.h:209: error: syntax error
before '*' token
/usr/lib/gcc/i686-pc-linux-gnu/3.4.6/include/ffi.h:210: error: syntax error
before '*' token
/usr/lib/gcc/i686-pc-linux-gnu/3.4.6/include/ffi.h:266: error: syntax error
before '*' token
/usr/lib/gcc/i686-pc-linux-gnu/3.4.6/include/ffi.h:272: error: syntax error
before '*' token
/usr/lib/gcc/i686-pc-linux-gnu/3.4.6/include/ffi.h:273: error: `ffi_call'
declared as function returning a function
/usr/lib/gcc/i686-pc-linux-gnu/3.4.6/include/ffi.h:274: error: syntax error
before "void"
In file included from /usr/include/g-wrap/guile-wct.h:23,
                 from /usr/include/g-wrap-wct.h:3,
                 from conftest.c:102:
/usr/include/g-wrap/core-runtime.h:151: error: syntax error before "ffi_cif"
/usr/include/g-wrap/core-runtime.h:153: error: syntax error before '}' token
configure:25951: $? = 1
configure: failed program was:
| /* confdefs.h.  */
| #define PACKAGE_NAME "gnucash"
| #define PACKAGE_TARNAME "gnucash"
| #define PACKAGE_VERSION "2.0.4"
| #define PACKAGE_STRING "gnucash 2.0.4"
| #define PACKAGE_BUGREPORT "[hidden email]"

/Don


-derek
> --
>        Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
>        Member, MIT Student Information Processing Board  (SIPB)
>        URL: http://web.mit.edu/warlord/    PP-ASEL-IA     N1NWH
>        [hidden email]                        PGP key available
>
_______________________________________________
gnucash-user mailing list
[hidden email]
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.
Reply | Threaded
Open this post in threaded view
|

Re: 2.0.4 crash

Josh Sled
On Mon, 2007-02-12 at 11:14 -0500, Donald Allen wrote:

>
>
> On 2/12/07, Derek Atkins <[hidden email]> wrote:
>         "Donald Allen" <[hidden email]> 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. :(  The comment
there mentions 1.9.7, but it applies to 1.9.6 as well.

--
...jsled
http://asynchronous.org/ - a=jsled;b=asynchronous.org;echo ${a}@${b}

_______________________________________________
gnucash-user mailing list
[hidden email]
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

signature.asc (196 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: 2.0.4 crash

Donald Allen
On 2/12/07, Josh Sled <[hidden email]> wrote:

>
> On Mon, 2007-02-12 at 11:14 -0500, Donald Allen wrote:
> >
> >
> > On 2/12/07, Derek Atkins <[hidden email]> wrote:
> >         "Donald Allen" <[hidden email]> 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}
>
>
_______________________________________________
gnucash-user mailing list
[hidden email]
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.