On Jul 5, 2014, at 11:34 PM, Sumit Bhardwaj wrote:
> Sure, John. Here you go. Interestingly, I didn't find conftest.c in the
> directory tree.
>
> 'tree | grep conftest.c' gave no output.
>
> Thanks,
> Sumit
>
> configure:25408: checking whether C++ compiler accepts
> -Wno-deprecated-regist
HI,
please make GnuCash dark themes compatible. Some fonts are fixed
colored. Blakc text on dark or black backgrounds are unreadable. Please
use system color settings for text color.
Currently GnuCash is unusable with dark themes (Linux).
___
gnucash-d
Hi,
Bug reports should go into bugzilla, not the gnucash-devel list. In fact, this
has been reported
as https://bugzilla.gnome.org/show_bug.cgi?id=707243
You are free to discuss a solution here or on the bug report if you feel you
can add to that.
Kind regards,
Geert
On Sunday 06 July 2014
Hi John,
On Saturday 28 June 2014 18:35:04 John Ralls wrote:
> On Jun 28, 2014, at 6:19 PM, Rainer Dorsch wrote:
> > On Saturday 28 June 2014 16:18:33 you wrote:
> >> On Jun 28, 2014, at 12:20 PM, Rainer Dorsch wrote:
> >>> Hello,
> >>>
> >>> Yahoo and Google start to list the bitcoin currency
On Jul 6, 2014, at 3:30 PM, Rainer Dorsch wrote:
> Hi John,
>
> On Saturday 28 June 2014 18:35:04 John Ralls wrote:
>> On Jun 28, 2014, at 6:19 PM, Rainer Dorsch wrote:
>>> On Saturday 28 June 2014 16:18:33 you wrote:
On Jun 28, 2014, at 12:20 PM, Rainer Dorsch wrote:
> Hello,
>
Hi John,
On Sunday 06 July 2014 16:33:16 John Ralls wrote:
> > If GnuCash does not use F:Q to fetch exchange rates, then the only benefit
> > of treating it as currency that it is easy to transfer BTC from one
> > wallet/account to another wallet/account. That seems to me much more
> > difficult
On Jul 6, 2014, at 4:38 PM, Rainer Dorsch wrote:
> Hi John,
>
> On Sunday 06 July 2014 16:33:16 John Ralls wrote:
>>> If GnuCash does not use F:Q to fetch exchange rates, then the only benefit
>>> of treating it as currency that it is easy to transfer BTC from one
>>> wallet/account to another
Hi John,
That works - to an extent. gcc fails and the current configuration is:
-Werror -Wdeclaration-after-statement -Wno-pointer-sign -D_FORTIFY_SOURCE=2
Configure doesn't fail, but that the flags are far fewer than earlier. Is
this, what we want to go ahead with?
If anyone wants to look at t
On Jul 6, 2014, at 6:38 PM, Sumit Bhardwaj wrote:
> Hi John,
>
> That works - to an extent. gcc fails and the current configuration is:
> -Werror -Wdeclaration-after-statement -Wno-pointer-sign -D_FORTIFY_SOURCE=2
>
> Configure doesn't fail, but that the flags are far fewer than earlier. Is
John,
I will be away on holidays soon. If you think my commit should be reverted,
feel free to do so. I
doubt I will have much online time available while I'm gone.
Geert
On Sunday 06 July 2014 10:05:27 John Ralls wrote:
> On Jul 5, 2014, at 11:34 PM, Sumit Bhardwaj wrote:
> > Sure, John. Her
On Jul 6, 2014, at 7:15 PM, Geert Janssens wrote:
> John,
>
> I will be away on holidays soon. If you think my commit should be reverted,
> feel free to do so. I doubt I will have much online time available while I'm
> gone.
Geert,
Yeah, you're not likely to have good connectivity. No worr
Dear John,
thanks for the pointers. It seems like the import-export/aqb use case of kvp
was the only place in the code that used them this way, so this is probably
why neither you nor anyone else so far has stumbled over this problem.
I can't even easily send you a gnucash file for reproducing
Just a quick update so everyone is on the same page: problem is not with
macro (autogen.sh) or configure. It seems the call for gfec.c mixes CFLAGS
and CXXFLAGS and then cc1plus or cc1 throws error. Diagnosis below.
I did have to make changes in macros/m4_ax_check_compile_flag.m4. I pushed
those c
On Jul 7, 2014, at 2:07 AM, Sumit Bhardwaj wrote:
> Just a quick update so everyone is on the same page: problem is not with
> macro (autogen.sh) or configure. It seems the call for gfec.c mixes CFLAGS
> and CXXFLAGS and then cc1plus or cc1 throws error. Diagnosis below.
>
> I did have to ma
14 matches
Mail list logo
