On Dec 22, 2011, at 11:07 PM, John Ralls wrote:

> 
> On Dec 22, 2011, at 3:28 PM, John Ralls wrote:
> 
>> 
>> On Dec 21, 2011, at 9:44 AM, Geert Janssens wrote:
>> 
>>> On 21-12-11 15:43, John Ralls wrote:
>>>> I got an msys-1.0.11 installation working on my windows VM yesterday and 
>>>> got it to go as far as starting Gnucash (I have a link error that I think 
>>>> is left over from the weekend and a completely different setup using the 
>>>> latest mingw -- which didn't go away when I cleaned gnome, gwen and aqb, 
>>>> so I think I need to start over with a clean tree). Unfortunately the 2.4 
>>>> build bombed on gwen with an error that I don't immediately understand.
>>>> 
>>>> I'm not likely to have time to dig into that today, so if you can fix the 
>>>> gwen error, great. Otherwise, I think you should revert your change to 
>>>> custom.sh yesterday (so that it goes back to aqb4) and we'll see what 
>>>> happens on tonight's build.
>>>> 
>>>> If we have to bump guile to 1.8, that should still be OK. 2.4 does work 
>>>> with 1.8, that's what ships on OSX.
>>>> 
>>>> Regards,
>>>> John Ralls
>>>> 
>>> The gwenhywfar bomb was actually a mingw build failure. However, when 
>>> install.sh fails, dist.sh is started immediately without any check if 
>>> install.sh finished successfully. (The windows build system really is that 
>>> ugly).
>>> 
>>> Since gwen isn't built yet, dist.sh fails in copying its files.
>>> 
>>> I think mingw fails because the old directory was still around. To fix 
>>> this, I have chosen to run reset.sh first in order to get a clean build 
>>> environment and have manually started a 2.4 build. We'll see what the 
>>> result will be now.
>>> 
>>> Regarding the guile update: if it were only the guile package that had to 
>>> be replaced it would be no problem. However, I never managed to build the 
>>> slib library for guile 1.8 on windows. So in trunk I have applied a series 
>>> of patches (once provided by Andy Wingo) to eliminate slib. So updating 
>>> guile on the 2.4 branch means we also have to apply this set of patches to 
>>> GnuCash 2.4. Is that ok for the stable branch ?
>> 
>> I think it's probably easier at this point to try to stay with guile-1.6.7 
>> for 2.4.
>> 
>> I found that the error message maps to https://savannah.gnu.org/bugs/?29583,
>> which was against 1.8.6 when compiled with gcc-4.5. I first tried applying 
>> the patch (provided by that same Andy Wingo). While it applied fine, it 
>> didn't fix the problem. Now I'm trying to get gcc-4.4 to work, but I'm 
>> having a dinner party tonight and I don't know if I'll get it done until 
>> tomorrow.
> 
> This produced a problem with gettext, but it's too late to investigate 
> tonight. I'll have a look at it in the morning.
> 

After a bit of a struggle with gettext, goffice, and openSP (mismatched 
compiler for the binaries of gettext-0.18.1.1-2, but 0.18.1.1-1 works; 
goffice-0.7 uses a Gtk class that's supposed to be deprecated in Gtk-2.24 but 
seems to be removed, and the C++ packaging of mingw libstdc++ was screwed up), 
I got a build all the way through most of Gnucash (it failed to set up a gconf 
directory in gnucash-2.4/inst). Close enough to commit today's work and see 
what happens on the nightly, so I did.

Regards,
John Ralls


_______________________________________________
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Reply via email to