Re: GnuCash win32 building...

2008-10-26 Thread Charles Day
On Sun, Oct 26, 2008 at 11:19 AM, Charles Day <[EMAIL PROTECTED]> wrote: > On Sat, Oct 25, 2008 at 3:44 PM, Martin Preuss <[EMAIL PROTECTED]> wrote: > >> Hi, >> >> On Samstag, 25. Oktober 2008, Andreas Köhler wrote: >> [...] >> > > Anyone know how to proceed? >> > >> > does adding -lz to the gcc c

Re: SQL backend

2008-10-26 Thread Phil Longstaff
The only think I can think of is that the dbi module isn't being loaded. >From your log: * 12:09:52 DEBUG [enter qofsession.c:qof_session_load_backend()] list=2, initted=false >From my log: * 18:03:14 DEBUG [enter qofsession.c:qof_session_load_backend()] list=5, initted=false The in

Re: Development on Mac Leopard (10.5.5)

2008-10-26 Thread David Reiser
On Oct 26, 2008, at 6:44 PM, Charles Day wrote: > What is the current state as far as doing GnuCash development on > Leopard? I > now have a spiffy new MacBook Pro at my disposal, so I am trying to > shift > away from developing on XP. I read the FAQ but the information sounded > enough out-o

Re: Development on Mac Leopard (10.5.5)

2008-10-26 Thread Graham Leggett
Charles Day wrote: 1. Is it readily possible to do GnuCash development, compilation, and testing work from within Leopard, via macports or fink or otherwise? Yes. 2. Is it just easier to do the work in Linux or XP running in a virtual machine, e.g. vmware fusion or parallels? (I would rather

Development on Mac Leopard (10.5.5)

2008-10-26 Thread Charles Day
What is the current state as far as doing GnuCash development on Leopard? I now have a spiffy new MacBook Pro at my disposal, so I am trying to shift away from developing on XP. I read the FAQ but the information sounded enough out-of-date that I thought I should ask for a update to double-check be

Re: GnuCash win32 building...

2008-10-26 Thread Charles Day
On Sat, Oct 25, 2008 at 3:44 PM, Martin Preuss <[EMAIL PROTECTED]> wrote: > Hi, > > On Samstag, 25. Oktober 2008, Andreas Köhler wrote: > [...] > > > Anyone know how to proceed? > > > > does adding -lz to the gcc command fix this error? Martin should know > > it :-) > Yes, adding -lz worked for m