Re: gnucash maint: Multiple changes pushed
I would suggest checking what v. redhat & suse use and support the oldest. Better yet, include glibc in the release. tedc From: gnucash-devel on behalf of Geert Janssens Sent: Thursday, March 23, 2017 3:49:08 AM To: gnucash-devel@gnucash.org Subject: Re: gnucash maint: Multiple changes pushed On woensdag 22 maart 2017 22:05:25 CET Geert Janssens wrote: > commit 9f3ad5510427eb69c857814de15e1c1be0727d2d > Author: Jesse Olmer > Date: Sat Feb 13 21:59:05 2016 -0800 > > Bug 739571 - Matching imported transactions doesn't indicate previously > matched entries > > Track pending matches from the current import and display this > information in the match picker. > This commit (which I pushed myself) breaks travis because its unit test uses g_assert_true and friends. A quick lookup shows the maint branch of gnucash is still running travis tests on Ubuntu 12.04 (Precise), which ships with glib-2.0 2.32 while g_assert_true was introduced in glib-2.0 2.38. I'm in two minds about how to proceed. - I could revert the patch and rework it for master only. This will delay its formal release with a few months. - I could backport my patches that set the minimum required glib-2.0 version to 2.40 and adjust the travis environment to trusty (14.04) like master. The fundamental question here is do we still want to support Ubuntu 12.04 ? It will be EOL by the end of next month so I don't know whether it's still worth spending effort for ? What you others think ? Geert ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Missing Guile Bindings and False Positive Unit tests
FYI there is a swig problem in OpenSuse leap 4.2. Its not the latest version. Tedc From: gnucash-devel on behalf of Derek Atkins Sent: Tuesday, February 21, 2017 8:59:27 AM To: Chad Albers Cc: gnucash-devel@gnucash.org Subject: Re: Missing Guile Bindings and False Positive Unit tests Hi Chad, Please remember to CC gnucash-user on all replies so that everyone can remain "in the loop". Also, the gnc-modules should properly export swig-exported functions without a re-export. If it stopped doing that, that would be a bug IMHO. Note that these unit tests are probably 18 years old. A long long time ago (well, around GnuCash 1.6 or so), /usr/bin/gnucash was a guile script. It loaded everything in as guile modules (technically it loaded GncModules) and then jumped back and forth between C and Scheme. Still, not everything was available from Scheme, but I don't believe anything has been *removed* from the guile bindings. Anyways, this structure was very hard to debug. You couldn't run it under gdb; you needed to "attach" gdb to the running process, which made it nearly impossible to debug issues during application loading. Eventually the Schemer developers left the project to pursue other endeavors, and those that remained eventually switched back to the "main() in C" structure that we have today. Of course a bunch of the functionality is still in GncModules. Having said all that, you shouldn't need to export or re-export a wrapped API. It should "just work". And the unit tests should be properly failing when there are missing or broken APIs. -derek Chad Albers writes: > I'll file a bug report. > > But, for the record, swig isn't exporting. That's not what swig does. > Function exports are done by using 2 APIs - the Guile define-modules > API or Guiles' C API. > > For example, > > - Some guile functions are defined here: src/engine/swig-engine.c. > This is where qof-session-new is defined. > - swig-engine.c uses Guile's C API to create a module called sw_engine > - swig-engine.c exports the functions - including qof-session-new - > using scm_c_export(...) > - Several Guile scm files use this module: (use-modules (sw_engine)). > None of these scm files either (export...) or (re-export...) functions > from the sw_engine module. > > Therefore, none of the Guile defined modules expose sw_engine functions. > > There may be, though, one exception, but even that isn't exposing > anything from sw_engine. The following is speculation... > > - GnuCash seems to include, what I suspect, is another module system. > I think it's in the module (gnucash gnc-module). Calls such as these > - (gnc:module-system-init) - may be a part that system. > - Included in that system may be code from: src/engine/gncmod-engine.c > - This C code has a C function called 'libgncmod_engine_gnc_module_init(...) > - This includes the sw_engine module. It calls > scm_c_eval_string("(use-modules (sw_engine))"); > - This scm_c_eval_string does not include any (exports...) or > (re-exports...) in the gncmode-engine.c file. > > Therefore, the sw_engine functions are not available in this other > module system. > > To make the sw_engine functions available (which is what I would > like), this may have been how it was once accomplished. The units > test that pass when they shouldn't include this line: > > (gnc:module-load "gnucash/engine" 0) > > Maybe, at one time gnc:module-load exported functions from > "gnucash/engine" modules. Or something like that. I'm still > investigating the what/why/how of the other module system. > > In the meantime, one solution is just to re-export sw_engine functions > from (gnucash engine) or engine.scm. That's what I'm doing for my > experiments, and it works. Perhaps I will submit a patch for that, > but I'm thinking that that's a hack. I'm opening up the discussion > here for a better solution, if exposing more of the Guile API is a) > fixing a bug and/or b) adding a new feature. Since much of GnuCash > was written in Guile, I thought I would use that instead of Python. > As is, though, there doesn't seem to be a way to even source a GnuCash > using its Guile bindings. It can be done using Python. > > Chad > > -- > > On Sun, Feb 19, 2017 at 5:34 PM, Derek Atkins wrote: >> That srfi didn't exist when the tests were written, which was probably >> around 18 years ago. The fact the tests don't fail just means nobody tested >> the tests for false positives. Please file a bug report? >> >> There isn't a need to be-export. Swig exports do that automatically. >> >> -derek >> >> Sent from my mobile device. Please excuse any typos. >> >> - Reply message - >> From: "Chad Albers" >> To: "Derek Atkins" >> Subject: Missing Guile Bindings and False Positive Unit tests >> Date: Sun, Feb 19, 2017 5:23 PM >> >> Definitely, though, the unit tests it is checking is >> 'qof-session-new'. It passes, but it hasn't been exported in the >> Guile cod
Re: Eclipse CDT IDE
Derick No I just thought you might be interested. I use my own builder shell script, not the built ins for heimdal + oafs. That solved many problems. The FIXME suggestions are a great help in cleaning up old code. ted From: Geert Janssens Sent: Tuesday, February 21, 2017 9:14:59 AM To: gnucash-devel@gnucash.org Cc: Ted Creedon Subject: Re: Eclipse CDT IDE Op dinsdag 21 februari 2017 16:38:10 CET schreef Ted Creedon: > Just a suggestion, > > I've finally succeeded in getting openafs up under the IBM eclipse IDE. > > Its my opinion that the task/team/remote debugging feature would reduce > support effort considerably. > > I encourage experimenting with it. > > Tedc Heh, I've been using Eclipse for a couple of years now. For me it's a mixed success. It's pretty convenient when it works as intended. Then I found it slow for certain things so I learned the command line equivalents and ended up using the IDE as an intelligent text editor. "Intelligent" because it does real time code analysis and comes with pop-up help while moving the mouse over words. However it happened more than once that an Eclipse update breaks my complete setup and I have to spend hours getting it working properly again. And that's getting tiresome. This week still an update suddenly lost the complete index of all referenced functions and variables. So all my code was full of red markers, suggestions and inline help stopped working. Most of it was fixed by restoring the search path for includes. But this shouldn't have happened in the first place. And what's worse, Eclipse still refuses to include one of my own (gnucash) header files in its index, so each parameter I'm using from that file is unknown. I've already spent a couple of hours -again- to try and resolve this. And so this week I finally gave up on Eclipse. I'm currently experimenting with KDevelop which has similar features. I'll see how it will go. Regardless, I'm glad Eclipse is improving your life! Geert ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Eclipse CDT IDE
Just a suggestion, I've finally succeeded in getting openafs up under the IBM eclipse IDE. Its my opinion that the task/team/remote debugging feature would reduce support effort considerably. I encourage experimenting with it. Tedc ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Are There Plans For A GUI Overhaul?
If you read and understand Scott Meyers books you're good to go. From: rhymeswithd...@gmail.com on behalf of Dave Sent: Wednesday, October 5, 2016 8:44 AM To: Ted Creedon Cc: John Ralls; gnucash-devel@gnucash.org Subject: Re: Are There Plans For A GUI Overhaul? Thanks, Jon and Ted. John, you inspired my optimism. Ted, you gave me a healthy dose of caution. :) So, I've done SysAdmin work for a living. In this field, lines of code are thought of as liabilities. If I can get something done with 10 lines of BASH code, I'll probably do it. Almost always, there needs to be a tangible result to efforts within 1-2 weeks of starting. So I'm used to being ruled more by economy and less by elegance. If I have an elegant solution, but it will take time to write, I have to essentially work in secret, burning the midnight oil. And even then, the idea may have actually been a bad one and I just wasted all that time that I didn't get paid or praised for. :( This is why I've by a Pythonista for some time. I use OOP when it makes sense, and don't when it doesn't. I write a working solution today, and can easily come back tomorrow to abstract this or that and make it maintainable for my future self and others. So I've learned a little about evolving a project, but only really in Python. I've wanted to get back to C/C++ for some time. My main motivation was AVR programming, which I've done a little bit of recently. However, none of my background has been in larger application design and programming. It seems that C++ has matured quite a bit since I touched it almost a decade ago. When I learned it, I got as far as the STL, which seemed very advanced to me at the time, but very interesting at the same time as I was finishing up a mathematics degree and the STL seemed like a great way to create the sort of abstractions that would help me begin writing programs to do computational analysis. I probably would have gone that direction too, but life took a turn for me and I got into managing Linux systems and hardware and data centers. Ted, I promise I'll give it some time. :) I'm not in any particular rush. I learn best by doing and it would be a pleasure if I could get up to speed in C++ again and help out GnuCash at the same time. I really just need to dive into C++ again. If I can't swim, then I can't swim and I'll have to move on. From what I've read about it, though, things like "shallow hierarchies" are practices I've already conceptually learned in the Python world. When I learned Python, I began writing it like a Java programmer. I have since been coaches completely away from that and classes are mostly used for a type of namespacing, easier testing or the like. I've also found that more and more, my programs are made up of generic computation over data. So most of what's happening is that the application gets directed by dictionaries that get processed to produce results. Basically, the Python becomes more akin to a scheme program. I've found that this produces a great amount of flexibility. Thanks again for the pointers, warnings and generally good discussion. I will look at the resources given. I've also found this<https://github.com/rigtorp/awesome-modern-cpp>, which I'm hoping is also a good place to start educating myself. On Wed, Oct 5, 2016 at 5:09 AM, Ted Creedon mailto:tcree...@easystreet.net>> wrote: As a retired Senior Project Manager responsible for maintaining many million lines of code I offer the following advice: 1. Stop and think. 2. Mark up the existing GUI's to indicate changes. 3. Write the New User's Manual and the System Adminstrator's Guide and Reference manual (tedious) 4. Select an IDE and non make build system (CMake,Scons, etc.) 4. Write subroutine headers that compile and link 5. Complete coding (very boring) If you doubt my wisdom, ask Scott Meyers to confirm Ted Creedon's advice. Stay away from C++ unless you have significant decades of experience. ROM effort for 1,000,000 lines of code / 100 lines per sub /per day = 10,000 subroutines /365= more time than we have.. => We're prisoners of the existing code. Ted Creedon, P.E. From: gnucash-devel mailto:easystreet@gnucash.org>> on behalf of John Ralls mailto:jra...@ceridwen.us>> Sent: Wednesday, October 5, 2016 12:12:59 AM To: Dave Cc: gnucash-devel@gnucash.org<mailto:gnucash-devel@gnucash.org> Subject: Re: Are There Plans For A GUI Overhaul? > On Oct 5, 2016, at 6:34 AM, Dave > mailto:linuxlu...@gmail.com>> wrote: > > Thanks for the great responses! It does clarify quite a bit. > > > From the looks of things, it seems that the C -- C++ port would have the > most impact right now. It wou
Re: Are There Plans For A GUI Overhaul?
As a retired Senior Project Manager responsible for maintaining many million lines of code I offer the following advice: 1. Stop and think. 2. Mark up the existing GUI's to indicate changes. 3. Write the New User's Manual and the System Adminstrator's Guide and Reference manual (tedious) 4. Select an IDE and non make build system (CMake,Scons, etc.) 4. Write subroutine headers that compile and link 5. Complete coding (very boring) If you doubt my wisdom, ask Scott Meyers to confirm Ted Creedon's advice. Stay away from C++ unless you have significant decades of experience. ROM effort for 1,000,000 lines of code / 100 lines per sub /per day = 10,000 subroutines /365= more time than we have.. => We're prisoners of the existing code. Ted Creedon, P.E. From: gnucash-devel on behalf of John Ralls Sent: Wednesday, October 5, 2016 12:12:59 AM To: Dave Cc: gnucash-devel@gnucash.org Subject: Re: Are There Plans For A GUI Overhaul? > On Oct 5, 2016, at 6:34 AM, Dave wrote: > > Thanks for the great responses! It does clarify quite a bit. > > > From the looks of things, it seems that the C -- C++ port would have the > most impact right now. It would take me awhile to get my C/C++ abilities > ramped up again. Where's the best place to start learning about gnucash > code? I don't know when I'd be able to start helping, but I'd at least want > to learn what I could. I think the best leverage for an additional developer at this point would be to work on extracting the business logic from the GUI code. That work could be in C since it's mostly extract function refactors and the extracted functions have to be callable by the C GUI. Part of that same job is to extract and combine the common code from Register and Register2; when Bob wrote it his vision was that the Reg2 stuff would work well enough that we could just drop Register, so he just copied the Register code and modified it. It didn't work out that way and it's become something of a maintenance headache because whenever we touch the guts of Register we have to remember to make the same changes in Register2. That hasn't always happened, so there are probably bugs that have been fixed in Register that still exist in Register2. To start learning the code read through the Doxygen documentation at http://code.gnucash.org/docs/MASTER and browse the code at https://github.com/gnucash/gnucash. For refreshing your C++ skills bear in mind that we're using C++11, templates, and shallow hierarchies (sometimes called "modern C++"). Have a look at http://wiki.gnucash.org/wiki/C%2B%2B, in particular http://wiki.gnucash.org/wiki/C%2B%2B#Developer_Preparation. Regards, John Ralls ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Authorization for commercial derivative work of GnuCash Tutorial and Concepts Guide
Submit to the previous authors. Consensus. From: Aaron Laws Sent: Wednesday, July 6, 2016 6:02:36 AM To: Ted Creedon Cc: John Ralls; stepbystepf...@mtdata.com; gnucash-devel@gnucash.org Subject: Re: Authorization for commercial derivative work of GnuCash Tutorial and Concepts Guide On Tue, Jul 5, 2016 at 8:54 PM, Ted Creedon mailto:tcree...@easystreet.net>> wrote: best thing to do is to prototype a sample & submit for approval. Submit to whom for approval? By what authority can anyone approve anything that might be submitted? If you said "submit for comments", I would not object. ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Authorization for commercial derivative work of GnuCash Tutorial and Concepts Guide
best thing to do is to prototype a sample & submit for approval. A hardcopy must have an accompanying website for source code editing. From: gnucash-devel on behalf of Ted Creedon Sent: Tuesday, July 5, 2016 5:30:38 PM To: John Ralls; stepbystepf...@mtdata.com Cc: gnucash-devel@gnucash.org Subject: Re: Authorization for commercial derivative work of GnuCash Tutorial and Concepts Guide Look at Broderbund. If a derived work has the same "look & feel" as gnucash, its is infringing. trfc From: gnucash-devel on behalf of Mike or Penny Novack Sent: Monday, July 4, 2016 4:56:36 PM To: John Ralls Cc: gnucash-devel@gnucash.org Subject: Re: Authorization for commercial derivative work of GnuCash Tutorial and Concepts Guide On 7/4/2016 9:54 AM, John Ralls wrote: > Read the original letter again. He's asking about copying parts of the > Tutorial and Concepts Guide, which is published under the GNU Free > Documentation License, or GFDL. That's separate from the program's > copyrights and licenses. Regards, John Ralls . Yes of course, he could not do THAT, actually incorporate it. I was responding to what appeared to be a broader interpretation of what he could not do. That's because I can see how he could accomplish (much, probably all) of what he says he wants to do without being in non-compliance. Michael D Novack Michael D Novack -- There is no possibility of social justice on a dead planet except the equality of the grave. ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Authorization for commercial derivative work of GnuCash Tutorial and Concepts Guide
Look at Broderbund. If a derived work has the same "look & feel" as gnucash, its is infringing. trfc From: gnucash-devel on behalf of Mike or Penny Novack Sent: Monday, July 4, 2016 4:56:36 PM To: John Ralls Cc: gnucash-devel@gnucash.org Subject: Re: Authorization for commercial derivative work of GnuCash Tutorial and Concepts Guide On 7/4/2016 9:54 AM, John Ralls wrote: > Read the original letter again. He's asking about copying parts of the > Tutorial and Concepts Guide, which is published under the GNU Free > Documentation License, or GFDL. That's separate from the program's > copyrights and licenses. Regards, John Ralls . Yes of course, he could not do THAT, actually incorporate it. I was responding to what appeared to be a broader interpretation of what he could not do. That's because I can see how he could accomplish (much, probably all) of what he says he wants to do without being in non-compliance. Michael D Novack Michael D Novack -- There is no possibility of social justice on a dead planet except the equality of the grave. ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Tax Sched report duplicates accounts
For year 2015 There is an apparent conflict between options>general>>from >>to buttons and alternate period drop down box It works fine if alternate period>>is not "last year" but is set to >>"use from to" if left as the default "last year" ; the "last year" setting creates the problem of duplication and incorrectly adds in 2014 to 2015 I.e. the reset defaults box/button doesn't work properly either.. I hope this helps email if more info needed tedc From: Alex Aycinena Sent: Tuesday, February 9, 2016 1:53 PM To: gnucash-devel; Ted Creedon Subject: Re: Tax Sched report duplicates accounts -- Forwarded message -- From: Ted Creedon mailto:tcree...@easystreet.net>> To: "gnucash-devel@gnucash.org<mailto:gnucash-devel@gnucash.org>" mailto:gnucash-devel@gnucash.org>> Cc: Date: Mon, 8 Feb 2016 19:12:54 + Subject: Tax Sched reoprt duplicates accounts Depending on the General tab settings the report duplicates accounts 2x or 3x gc ver 2.6.11 on 86_64 x86_64 x86_64 GNU/Linux tedc Can you provide more information? I would like to reproduce the problem. What does "depending on the General tab settings ..." mean? With some settings it does but with others it doesn't? You're referring to the General tab in the report options? How do I have to set it up to get the same problem? Alex ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Tax Sched reoprt duplicates accounts
Is there a workaround or quick fix? I'm doing my taxes. tedx From: Ted Creedon Sent: Monday, February 8, 2016 11:12 AM To: gnucash-devel@gnucash.org Subject: Tax Sched report duplicates accounts Depending on the General tab settings the report duplicates accounts 2x or 3x gc ver 2.6.11 on 86_64 x86_64 x86_64 GNU/Linux tedc ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Tax Sched reoprt duplicates accounts
Depending on the General tab settings the report duplicates accounts 2x or 3x gc ver 2.6.11 on 86_64 x86_64 x86_64 GNU/Linux tedc ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
add hot keys to account page howto
It looks like the howto add hot (accelerator) keys info is not up to date. Could one revise/detail the generics in https://lists.gnucash.org/pipermail/gnucash-user/2011-January/038021.html ? I'd like to use ctrl j for jump & ctrl d for delete in all menus Gnucash ver 2.6.7 suse tumbleweed tedc ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Using LaTex for Documentation
I hack using word and do a word to latex conversion If you want I can setup a tooling stream, I presume that the permuted index needs to be created after conversion Send me a file to convert Tedc From: Geert Janssens Sent: Wednesday, September 2, 2015 8:39:34 AM To: gnucash-devel@gnucash.org Cc: John Ralls; Ted Creedon Subject: Re: Using LaTex for Documentation On Tuesday 01 September 2015 07:07:13 John Ralls wrote: > > On Sep 1, 2015, at 3:38 AM, Ted Creedon > > wrote: > > > > whats wrong with Latex? > > > > It works fine and produces a permuted index too > > Besides being even geekier and harder to convert to ePub and HTML than > Docbook? Probably nothing much. > For me the geeky nature is not relevant. I care about an easy way to write documentation ideally wysiwym (as opposed to wysiwyg) and easy to merge patches. For latex documents I found LyX [1], which seems to be a free wysiwym editor available on all major platforms. I haven't found ways yet to convert from docbook to latex, so getting started may be a bigger hurdle here. There is dblatex but my first run failed to do the conversion. It may work after some more tweaking. The conversion to epub should not be too hard. Generating pdf from latex is the natural flow of things and there are lots of pdf to epub convertors around. So I presume one of them will be able to do the job. Html is less clear. There's a document (last modified in 2007) which documents a process to convert from latex to docbook [3] which would extend our current workflow. I is unfortunately based on lyx 1.2.0, which is ancient and in addition it brings in a lot of dependencies. Then this page lists several latex to html converters [4]. I haven't gotten around to test them so I can't say much for the quality of the generated html. Geert [1] https://en.wikipedia.org/wiki/LyX http://www.lyx.org/ [2] http://dblatex.sourceforge.net/ [3] http://www.karakas-online.de/mySGML/ [4] http://www.tex.ac.uk/FAQ-LaTeX2HTML.html ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Using LaTex for Documentation
I find I quite easy to use and the typesetting is superb. Especially if equations are needed. Xml is a hack Ted From: John Ralls Sent: Tuesday, September 1, 2015 7:07:13 AM To: Ted Creedon Cc: gnucash-devel@gnucash.org Subject: Re: Using LaTex for Documentation > On Sep 1, 2015, at 3:38 AM, Ted Creedon wrote: > > whats wrong with Latex? > > It works fine and produces a permuted index too Besides being even geekier and harder to convert to ePub and HTML than Docbook? Probably nothing much. Regards, John Ralls ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Using LaTex for Documentation
whats wrong with Latex? It works fine and produces a permuted index too tedc From: gnucash-devel on behalf of Mike Evans Sent: Tuesday, September 1, 2015 2:56 AM Cc: gnucash-devel@gnucash.org Subject: Re: Using AsciiDoc for Documentation On Sun, 30 Aug 2015 19:16:24 -0500 Rob Gowin wrote: > [Hello List. Long time GnuCash user, -devel list lurker, > coming out of the shadows.] > > > On Aug 29, 2015, at 5:43 AM, Mike Evans wrote: > > Another random thought then. > > > > I use asciidoc for pretty much all the docs I write, not much > > admittedly but it's easy to learn and can produce many output formats. > > I just used https://github.com/oreillymedia/docbook2asciidoc to > > convert the guide to asciidoc using: > > > > $ java -jar /home/mikee/Projects/docbook2asciidoc/saxon9he.jar > > -s gnucash-guide.xml -o gnucash-guide.asc > > /home/mikee/Projects/docbook2asciidoc/d2a.xsl chunk-output=true > > > > This produces an asccidoc file for each chapter plus the master page. > > > > [...] > > > > I'm not an expert on XML parsing using .xsl stylesheets but I suspect > > this could be easily(?) remedied by editing the d2a.xsl to correctly > > include the figures[...] > > I am also a fan of using AsciiDoc as a documentation format. A > while back I did some of the XSL hacking Mike refers to that is needed > to get a decent conversion from the existing DocBook files. It's to > the point where I would like to get some feedback. > > I've done a first-pass conversion of the English version of the T & CG to > AsciiDoc at https://github.com/codesmythe/gnucash-docs/tree/asciidoc/guide/C > . > You can click on the *.asc files there like ch_oview.asc to see GitHub's > rendered verison of the file, including non-SVG images. (Note that SVG files > and inter-chapter links don't work on GitHub's render.) You can click on the > 'Raw' button for a file to see the AsciiDoc source. The source needs clean > up > (lines too long, etc), but it is clean enough for folks to get an idea of > the > syntax. The GitHub web interace is useful because I think small edits could > be > done and sent as pull requests all from the web. > > Like Mike said, the AsciiDoc tools (asciidoctor, at http://asciidoctor.org > in > this case) support the generation of DocBook XML files, so it's relatively > simple to insert AsciiDoc support into the current document generation > flow. > The asciidoctor tool generates DocBook output, and the existing flow for > generating PDFs, HTML, EPUB, MOBI etc. works the same. My branch has the > changes to the various Makefile.am files to support this. Those interested > should be able to clone the repo, switch to the asciidoc branch and then > 'make > pdf' as usual. Note that the 'configure' script will expect to find the > asciidoctor program on the system. I think the generated PDF is reasonably > close to the original for a first pass proof of concept. I've tested the > flow > on OS X and Fedora 21. Dunno about Windows. > > Hopefully this little demo can move the documentation file format > discussion > forward a bit. :-) Thoughts? > > > Regards, > > Rob Hi Rob Looks good to me. Still a few minor bugs with the Asciidoc. Some of the Figure titles are missing Second level bullet indents missing But these are minor and some tweaking of the XSL should fix that. Speaking of which, I notice the XSL isn't in github can you make that available somewhere so others can chip in with help? I'd also like to generate the Asciidoc locally so I can ensure both formats are from the same source for comparison purposes. Now you (we) have to convince others to use Asciidoc! I use Geany for my coding/writing and there is a Markdown plugin for preview, no Asciidoc at the moment though. I'm looking at the PEG code to see how difficult it would be to produce an Asciidoc previewer plugin. It may be beyond my learning tolerance though. Mike E -- PGP key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x00CDB13500D7AB53 ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
calc2qif hack of oDialog.Execute()
after some experimentation here is a hack that loads alc2qif into the main menu file open calc2qif.sxc change line 147 of Calc2qif. Standard. Install. install_en from oDialog.Execute() to oDialog.endExecute() and run macro install_en it at least runs Ok No time to rewrite the GUI using the GUI editor and re-use appropriate macros exercise left to readers My squid bank doesn't save qif files longer than 12 months so I have to cut & paste into lebreoffice 4.1.1 tedc From: gnucash-devel on behalf of John Ralls Sent: Monday, August 17, 2015 9:29 AM To: wwhk10 Cc: gnucash-devel@gnucash.org Subject: Re: report guid > On Aug 17, 2015, at 4:23 PM, wwhk10 wrote: > > Hi. > > I am trying to add a report and read in the documentation that each report > needs a unique ID. How can I run gnucash-make-guids or uuidgen? I am using > the Windows version. > > I did a search but cannot find these commands. Google turns up many web-based uuid generators. You can use any of them. Just remove the ‘-‘ chanracters from the result after you paste it in to your custom report. Regards, John Ralls ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: C++ work
All changes to the Tektronix MRP system made 1981-1985 were zero defect Some were quite extensive. The entire corporation's manufacturing system handling 1,000,000 parts was netted daily. Any defect would have caused the parts delivery/ordering system to crash on the IBM mainframe. Several thousand users.. Tek went bankrupt because the replacement MRP system and a major software offering were not zero defect.. Also look at the space shuttle manipulator code, written in Forth. tedc On Wed, Sep 10, 2014 at 6:51 AM, John Ralls wrote: > > On Sep 10, 2014, at 5:05 AM, Ted Creedon wrote: > > > mark up the screenshots with proposed changes > > > > then write the user's manual, systems administrator's manual & systems > > administrator's reference manual - submit for comments & approvals > > > > then write C++ header files that wrap your subroutines &compile & link > > > > only then can you begin code conversion > > > > writing code is the last step, not the first step - and its very boring- > > but you do get zero defect code > > I know of no project, waterfall or otherwise, that ever produced > zero-defect code. > > The changes we're discussing in this context are not reflected in the GUI > and so there would be no markup on screen shots and no changes to the > documentation. > > Regards, > John Ralls > > > > ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: C++ work
mark up the screenshots with proposed changes then write the user's manual, systems administrator's manual & systems administrator's reference manual - submit for comments & approvals then write C++ header files that wrap your subroutines &compile & link only then can you begin code conversion writing code is the last step, not the first step - and its very boring- but you do get zero defect code tedc retired senior project manager Tektronix Research Labs On Tue, Sep 9, 2014 at 2:50 PM, John Ralls wrote: > > On Sep 9, 2014, at 2:24 PM, Geert Janssens > wrote: > > > On Tuesday 09 September 2014 15:12:33 Aaron Laws wrote: > >> The short question is: What GUI framework is gnucash likely to target > >> in c++? > >> > > Equally short answer: likely Qt or WxWidgets. But we never did a > detailed evaluation yet. > > > >> I've heard it mentioned that the current framework (GTK?) doesn't make > >> sense in c++ because it's so gobject-oriented, but I didn't hear > >> anything else suggested. I know there's a QT effort which seems like > >> a reasonable way to go, but haven't heard it actually endorsed > >> anywhere. > >> > > Exactly > > > >> Currently, c++ work is starting at the deepest point (the part of the > >> code that is relied on by everything), qof, so that a C api has to be > >> maintained until everything that relies on QOF has a way of accessing > >> the c++ interfaces. This means that c++ and C interfaces need to be > >> created and maintained in parallel until everything's ready to > >> switch. This has grated on me for quite a while, but I see it as a > >> very difficult problem. I don't see a quick way to fix it. I've tried > >> (and technically succeeded ^_^) compiling the whole project as c++, > >> but that's not so great because the dynamic linking doesn't work > >> because of mangling. Repairing this solution doesn't seem like a > >> profitable way forward. It's sort of like throwing all your > >> belongings into a river, then swimming across yourself, and trying to > >> collect everything on the other side, making sure you didn't lose > >> anything. > >> > >> Another way that I've been trying to consider is to start on the part > >> of project upon which nothing relies. That way, that part of the > >> project can be completely C++. Then, take the next thing which > >> doesn't expose a *used* C api. Rinse and repeat. This way, there will > >> never (?) have to be a duplicated API in any system. > >> > > Sounds nice in theory. I fear it will be equally if not more difficult > than the current approach > > though. > > > > Taking your example of first replacing the gui. > > > > As you bring up yourself it is heavily gobject based. And in addition > the controller, model and > > view code are mixed up. Rewriting it in (say) Qt, means it will now use > Qt objects. But the > > "business logic" (our engine code) is still gobject based. > > > > So now in order for the gui to talk to the business logic you have to > create an interface layer > > between the engine and the gui that will do the proper translations > between the two object > > models. That is probably more work than maintaining the existing C api > in the path currently > > chosen. > > > > In addition logically it doesn't make sense to start from the gui and > drill down to the model. > > Your gui should be based on the model and controller logic so it only > makes sense to start there. > > Going the other way around as a sure way to make wrong assumptions about > how the lower > > layers will be implemented and in the best case mean several revisions > to the higher layers or > > having to start over in the worst case. > > > >> Another way to think about this is as a tree structure. I'll throw > >> something up, and I'll eagerly await corrections! Read "->" as "relies > >> on": > >> > >> GUI (GTK?) -> Business Logic > > So rewrite the gui and an interface layer between the two > >> Alternate gui (WEB?) -> Business Logic > > Same here. > >> GUI (GTK?) -> Reporting Infrastructure > > Same here. > >> Business Logic -> QOF > > Rewrite the business logic and write an interface layer between the two. > > Oops, the way we write the business logic now means we need to change > the gui layer, because > > it made some invalid assumptions on what the business logic would be. > > So rewrite the gui here as well > >> Reporting Infrastructure -> QOF > > Rewrite the reporting infrastructure and write an interface layer > between the two. > > Oops, the way we write the reporting infrastructure now means we need to > change the gui > > layer, because it made some invalid assumptions on what the business > logic would be. > > So rewrite the gui here as well > > > >> QOF -> libdrm, etc. > > Rewrite qof and realize we end up with a different implementation that > we thought we would. > > So rewrite the business logic and the reporting infrastructure once > more. And bollocks, that kills > > our gui design again. Rewrite the gui... > > > >> > >> So, if
Re: Gnucash c++
Its very possible to begin he transition to C++ by writing C++ header files. The real advantage of C++ is the ability to take a specification (in my case the Intel IBIS electronic buffer modeling specification http://www.eigroup.org/ibis/ibis.htm) and modelling it with C++ header files that compile. This provides an unambiguous representation of a specification allowing multiple vendors to create data structures that always run correctly. In addition, the early on representation (i.e is this an iterator or whatever) and class definition really tie the code writers down. The particular project I mentioned took a summer grad student 3 months to create the header files from a complicated spec. Then the project was cancelled (because it worked)! As a result vendor A's models might not work with vendor B's simulator... As difficult as I find C++ to understand I highly recommend its use. Tedc On Wed, Aug 13, 2014 at 5:20 PM, John Ralls wrote: > > On Aug 13, 2014, at 3:42 PM, Gour wrote: > > > On Wed, 13 Aug 2014 11:21:59 -0400 > > Derek Atkins wrote: > > > >> Ummm.. No. > > > > OK. > > > >> The benefit of C -> C++ is that except for a few minor issues with > >> keywords you can *generally* compile C code using the C++ compiler and > >> it will *just work*. > > > > That's clear. > > > >> The same cannot be said for Go or any other language. > > > > Btw, Go team converts Go compiler from C to Go. ;) > > > >> Please read the FAQ entry on "Why don't you (re)write GnuCash in >> favorite language>" at http://wiki.gnucash.org/wiki/FAQ > > > > Well, being in #gnucash I got the feeling that there is plan to abandon > > glib, rewrite the engine and possibly even to consider Qt 'cause > > without glib, one is not tied so much to GTK any longer. > > > > Considering that C --> C++ (and taking advantage of it) might be more > > strange than C --> Go which is created to be picked easily by C devs, I > > did throw my suggestion. > > > > Otoh, I believe that C --> C++ is not to be done in order to just > > increase build time.* :-) > > > > * Rob Bike from the Go team says that long build times (~45mins) for C++ > > * projects was the time when Go was conceived. ;) > > > > I'm aware of FAQ entry, but was thinking that GC is on the verge of > > possible (partial) rewrite. > > All true, but you missed Derek's point. The advantage of C++ is that one > can use it with C *in the same file*. That means I can take a C file, tell > the compiler it's really a C++ file, and compile it almost as-is (that's > what Aaron's change is about, cleaning up all of the almosts). Then I can > make a C++ class and move the functionality into it one function at a time, > converting the C function to a wrapper with C linkage. I can test that > against the existing C tests, add C++ tests, and move on to the next > function. The rest of GnuCash can't tell anything's changed; new work now > has two versions of the API to use depending on whether it's completely new > or a modification of existing. If it comes time to start the release cycle > and the conversion isn't complete, we can ship it as-is because nothing's > broken. > > There other languages like that, but they're all AFAIK tied to particular > proprietary platforms to some extent: Objective C and Apple, C# and > Microsoft, Vala and Gtk+. C++ is ISO-standard with an extremely active > committee. > > Regards, > John Ralls > > > ___ > gnucash-devel mailing list > gnucash-devel@gnucash.org > https://lists.gnucash.org/mailman/listinfo/gnucash-devel > ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Fwd: Fw: [Oxygen] [Bug 331927] Oxygen crashes gnucash
Some one is looking at Oxygen for us Can you clarify the versions? ted -- Forwarded message -- From: ted c Date: Mon, Mar 10, 2014 at 5:41 PM Subject: Fw: [Oxygen] [Bug 331927] Oxygen crashes gnucash To: "tcree...@easystreet.net" - Forwarded Message - *From:* Jekyll Wu *To:* tedc...@yahoo.com *Sent:* Sunday, March 9, 2014 7:45 PM *Subject:* [Oxygen] [Bug 331927] Oxygen crashes gnucash https://bugs.kde.org/show_bug.cgi?id=331927 Jekyll Wu changed: What|Removed|Added Version|4.12.2 |unspecified Severity|grave |crash --- Comment #1 from Jekyll Wu --- Does gnucash use gkt3 or gtk2 ? What is the version of oxygen-gtk2/3 in your system ? -- You are receiving this mail because: You reported the bug. ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: 2.6.2 segfaulting (gtk/oxygen version apparently broken)
Theme HighContrast seems to work See: https://bugzilla.novell.com/post_bug.cgi bug 867253 On Thu, Mar 6, 2014 at 2:30 PM, Bill Nottingham wrote: > Christian Stimming (christ...@cstimming.de) said: > > Am Donnerstag, 6. März 2014, 12:33:58 schrieb John Ralls: > > > On Mar 6, 2014, at 12:23 PM, Ted Creedon > wrote: > > > > Looks like the GTK/Oxygen theme is broken, changed thmres & seems to > work > > > > OK > > > > > > > > How do i report this, & to who? > > > > > > I'd start with SuSE and let them figure out if it's an upstream > problem or > > > if it's their fault. Since Bill Nottingham reported that RedHat has > also > > > seen some issued with Oxygen, it will probably wind up there, but > unless > > > you want to get VCS checkouts of both Gtk and Oxygen and debug the > actual > > > problem it's better to let the SuSE packagers deal with upstream. > > > > FTR: I'm also experiencing crashes recently due to oxygen theme/gtk, on > Ubuntu > > 13.10 with gtk-2.24.20 with gtk2-engines-oxygen-1.3.4. Backtrace below. > The > > crash happens when hovering over the toolbar, quite reproducibly (read: > rather > > often - quite annoying). > > > Just in case anyone is interested: > > > > Program received signal SIGSEGV, Segmentation fault. > > 0x764fc92a in IA__gtk_widget_queue_draw (widget=0xa65d290) > > at /build/buildd/gtk+2.0-2.24.20/gtk/gtkwidget.c:3772 > > (gdb) bt > > #0 0x764fc92a in IA__gtk_widget_queue_draw (widget=0xa65d290) > > at /build/buildd/gtk+2.0-2.24.20/gtk/gtkwidget.c:3772 > > #1 0x7fffe406616e in Oxygen::ToolBarStateData::delayedUpdate(void*) > () > >from /usr/lib/x86_64-linux-gnu/gtk-2.0/2.10.0/engines/liboxygen-gtk.so > > #2 0x7fffe4066845 in > Oxygen::ToolBarStateData::updateState(_GtkWidget*, > > bool, bool) () > >from /usr/lib/x86_64-linux-gnu/gtk-2.0/2.10.0/engines/liboxygen-gtk.so > ... > > While different than the trace Ted reported, that seems to match the trace > we've had reported for the Fedora builds in our bugzilla. > > Bill > ___ > gnucash-devel mailing list > gnucash-devel@gnucash.org > https://lists.gnucash.org/mailman/listinfo/gnucash-devel > ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: 2.6.2 segfaulting
Bug 867253 submitted to opensuse https://bugzilla.novell.com/post_bug.cgi On Thu, Mar 6, 2014 at 12:33 PM, John Ralls wrote: > > On Mar 6, 2014, at 12:23 PM, Ted Creedon wrote: > > > Looks like the GTK/Oxygen theme is broken, changed thmres & seems to > work OK > > > > How do i report this, & to who? > > I'd start with SuSE and let them figure out if it's an upstream problem or > if it's their fault. Since Bill Nottingham reported that RedHat has also > seen some issued with Oxygen, it will probably wind up there, but unless > you want to get VCS checkouts of both Gtk and Oxygen and debug the actual > problem it's better to let the SuSE packagers deal with upstream. > > Regards, > John Ralls > > ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: 2.6.2 segfaulting
Looks like the GTK/Oxygen theme is broken, changed thmres & seems to work OK How do i report this, & to who? tedc On Wed, Mar 5, 2014 at 2:41 AM, Ted Creedon wrote: > > FYI I had to blind type "bt full" into gdb after gnucash is running to > capture the trace, before the bug freezes the screen.. > > tedc > > > On Wed, Mar 5, 2014 at 2:14 AM, Geert Janssens > wrote: > >> On Tuesday 04 March 2014 15:56:15 John Ralls wrote: >> >> > On Mar 4, 2014, at 3:11 PM, Ted Creedon >> wrote: >> >> > > Crash back trace - gnucash froze up but nothing else - yet - >> >> > >> >> > [Long, detailed backtrace elided]. >> >> > >> >> > OK. It's Gtk and Oxygen almost all the way down, and it's crashing >> >> > trying to draw something. I don't think that there's anything we can >> >> > do to help you here. As a first guess, ditch the Oxygen theme, but >> >> > ISTM you need to get help from the SuSE GnuCash packager. >> >> > >> >> > Regards, >> >> > John Ralls >> >> > >> >> > >> >> > ___ >> >> > gnucash-devel mailing list >> >> > gnucash-devel@gnucash.org >> >> > https://lists.gnucash.org/mailman/listinfo/gnucash-devel >> >> >> >> You could try to use another theme for gtk applications within kde. On >> Fedora I can change this via >> >> System Settings -> Application Appearance -> Gtk+ appearance. >> >> >> >> Just for the record, my KDE-Gtk+ theme is oxygen-gtk as well. On Fedora >> 20 this seems to work without a hitch. >> >> >> >> Geert >> > > ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: 2.6.2 segfaulting
FYI I had to blind type "bt full" into gdb after gnucash is running to capture the trace, before the bug freezes the screen.. tedc On Wed, Mar 5, 2014 at 2:14 AM, Geert Janssens wrote: > On Tuesday 04 March 2014 15:56:15 John Ralls wrote: > > > On Mar 4, 2014, at 3:11 PM, Ted Creedon wrote: > > > > Crash back trace - gnucash froze up but nothing else - yet - > > > > > > [Long, detailed backtrace elided]. > > > > > > OK. It's Gtk and Oxygen almost all the way down, and it's crashing > > > trying to draw something. I don't think that there's anything we can > > > do to help you here. As a first guess, ditch the Oxygen theme, but > > > ISTM you need to get help from the SuSE GnuCash packager. > > > > > > Regards, > > > John Ralls > > > > > > > > > ___ > > > gnucash-devel mailing list > > > gnucash-devel@gnucash.org > > > https://lists.gnucash.org/mailman/listinfo/gnucash-devel > > > > You could try to use another theme for gtk applications within kde. On > Fedora I can change this via > > System Settings -> Application Appearance -> Gtk+ appearance. > > > > Just for the record, my KDE-Gtk+ theme is oxygen-gtk as well. On Fedora 20 > this seems to work without a hitch. > > > > Geert > ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: 2.6.2 segfaulting
I'll keep trying to get my taxes & a backtrace done Would running under Gnome help? ted On Mon, Mar 3, 2014 at 8:52 PM, Bill Nottingham wrote: > John Ralls (jra...@ceridwen.us) said: > > Yeah, I dunno what Oxygen::MenuStateData::menuItemIsActive is except that > > it doesn't have anything to do with GnuCash, Gtk+, or GLib. You need to > > explain your environment in detail and why we should support it, > otherwise > > you're totally on your own. > > It's a port of the oxygen KDE theme to GTK2, used to make gtk/GNOME apps > match KDE when running under KDE. And yes, we've seen some crash reports in > Fedora when GnuCash is run with it, although not with that specific > backtrace: > https://bugzilla.redhat.com/show_bug.cgi?id=1039286 > > Bill > ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: 2.6.2 segfaulting
Another fault, looks like troubleshooting will be difficult Seems too be related to focusing on the menu bar. Moving the mouse over it causes a crash Program terminated with signal SIGSEGV, Segmentation fault. The program no longer exists. (gdb) bt full No stack. On Tue, Mar 4, 2014 at 9:13 AM, Ted Creedon wrote: > I'll keep trying to get my taxes & a backtrace done > > Would running under Gnome help? > > ted > > > On Mon, Mar 3, 2014 at 8:52 PM, Bill Nottingham wrote: > >> John Ralls (jra...@ceridwen.us) said: >> > Yeah, I dunno what Oxygen::MenuStateData::menuItemIsActive is except >> that >> > it doesn't have anything to do with GnuCash, Gtk+, or GLib. You need to >> > explain your environment in detail and why we should support it, >> otherwise >> > you're totally on your own. >> >> It's a port of the oxygen KDE theme to GTK2, used to make gtk/GNOME apps >> match KDE when running under KDE. And yes, we've seen some crash reports >> in >> Fedora when GnuCash is run with it, although not with that specific >> backtrace: >> https://bugzilla.redhat.com/show_bug.cgi?id=1039286 >> >> Bill >> > > ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: 2.6.2 segfaulting
Just a vanilla SuSE 13.1 x64 Linux system. Gnucash has run fine on Suse for years. I have 2 other 13.1's I'll try them tedc On Mon, Mar 3, 2014 at 7:46 PM, John Ralls wrote: > > On Mar 3, 2014, at 5:30 PM, Ted Creedon wrote: > > > Another crash, output from gdb (bt not possible) > > > > gdb) run^M(gdb) run^M(gdb) run > > Starting program: /usr/local/bin/gnucash > > [Thread debugging using libthread_db enabled] > > Using host libthread_db library "/lib64/libthread_db.so.1". > > [New Thread 0x7fffe21e8700 (LWP 6203)] > > [New Thread 0x7fffe19e7700 (LWP 6204)] > > [New Thread 0x7fffda733700 (LWP 6205)] > > [New Thread 0x7fffb684b700 (LWP 6207)] > > [Thread 0x7fffb684b700 (LWP 6207) exited] > > [New Thread 0x7fffb684b700 (LWP 6208)] > > [New Thread 0x7fffabdfa700 (LWP 6397)] > > [Thread 0x7fffabdfa700 (LWP 6397) exited] > > [New Thread 0x7fffabdfa700 (LWP 6440)] > > [Thread 0x7fffabdfa700 (LWP 6440) exited] > > [New Thread 0x7fffabdfa700 (LWP 6465)] > > [New Thread 0x7fffab4f7700 (LWP 6466)] > > [New Thread 0x7fffa9f98700 (LWP 6469)] > > [New Thread 0x7fffa9797700 (LWP 6470)] > > [New Thread 0x7fffa8f96700 (LWP 6471)] > > [New Thread 0x7fff5b372700 (LWP 6489)] > > [New Thread 0x7fff5ab71700 (LWP 6490)] > > [New Thread 0x7fff5a370700 (LWP 6491)] > > [New Thread 0x7fff59b6f700 (LWP 6492)] > > [New Thread 0x7fff5936e700 (LWP 6493)] > > [New Thread 0x7fff58b6d700 (LWP 6494)] > > [New Thread 0x7fff43fff700 (LWP 6495)] > > [New Thread 0x7fff3b7f5700 (LWP 6496)] > > [Thread 0x7fff3b7f5700 (LWP 6496) exited] > > [New Thread 0x7fff3b7f5700 (LWP 6562)] > > [Thread 0x7fff3b7f5700 (LWP 6562) exited] > > [New Thread 0x7fff3b7f5700 (LWP 6617)] > > [Thread 0x7fff3b7f5700 (LWP 6617) exited] > > [New Thread 0x7fff3b7f5700 (LWP 6657)] > > [Thread 0x7fff3b7f5700 (LWP 6657) exited] > > > > Program received signal SIGSEGV, Segmentation fault. > > 0x7fffe28e84dc in > Oxygen::MenuStateData::menuItemIsActive(_GtkWidget*) > > const () > > from /usr/lib64/gtk-2.0/2.10.0/engines/liboxygen-gtk.so > > (gdb) > > (gdb) Error detected on fd 0 > > error detected on stdin > > A debugging session is active. > > > >Inferior 1 [process 6200] will be killed. > > > > Quit anyway? (y or n) > > output.log lines 27-78/78 > > > > Yeah, I dunno what Oxygen::MenuStateData::menuItemIsActive is except that > it doesn't have anything to do with GnuCash, Gtk+, or GLib. You need to > explain your environment in detail and why we should support it, otherwise > you're totally on your own. > > Regards, > John Ralls > > ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: 2.6.2 segfaulting
Another crash, output from gdb (bt not possible) gdb) run^M(gdb) run^M(gdb) run Starting program: /usr/local/bin/gnucash [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". [New Thread 0x7fffe21e8700 (LWP 6203)] [New Thread 0x7fffe19e7700 (LWP 6204)] [New Thread 0x7fffda733700 (LWP 6205)] [New Thread 0x7fffb684b700 (LWP 6207)] [Thread 0x7fffb684b700 (LWP 6207) exited] [New Thread 0x7fffb684b700 (LWP 6208)] [New Thread 0x7fffabdfa700 (LWP 6397)] [Thread 0x7fffabdfa700 (LWP 6397) exited] [New Thread 0x7fffabdfa700 (LWP 6440)] [Thread 0x7fffabdfa700 (LWP 6440) exited] [New Thread 0x7fffabdfa700 (LWP 6465)] [New Thread 0x7fffab4f7700 (LWP 6466)] [New Thread 0x7fffa9f98700 (LWP 6469)] [New Thread 0x7fffa9797700 (LWP 6470)] [New Thread 0x7fffa8f96700 (LWP 6471)] [New Thread 0x7fff5b372700 (LWP 6489)] [New Thread 0x7fff5ab71700 (LWP 6490)] [New Thread 0x7fff5a370700 (LWP 6491)] [New Thread 0x7fff59b6f700 (LWP 6492)] [New Thread 0x7fff5936e700 (LWP 6493)] [New Thread 0x7fff58b6d700 (LWP 6494)] [New Thread 0x7fff43fff700 (LWP 6495)] [New Thread 0x7fff3b7f5700 (LWP 6496)] [Thread 0x7fff3b7f5700 (LWP 6496) exited] [New Thread 0x7fff3b7f5700 (LWP 6562)] [Thread 0x7fff3b7f5700 (LWP 6562) exited] [New Thread 0x7fff3b7f5700 (LWP 6617)] [Thread 0x7fff3b7f5700 (LWP 6617) exited] [New Thread 0x7fff3b7f5700 (LWP 6657)] [Thread 0x7fff3b7f5700 (LWP 6657) exited] Program received signal SIGSEGV, Segmentation fault. 0x7fffe28e84dc in Oxygen::MenuStateData::menuItemIsActive(_GtkWidget*) const () from /usr/lib64/gtk-2.0/2.10.0/engines/liboxygen-gtk.so (gdb) (gdb) Error detected on fd 0 error detected on stdin A debugging session is active. Inferior 1 [process 6200] will be killed. Quit anyway? (y or n) output.log lines 27-78/78 On Mon, Mar 3, 2014 at 4:31 PM, Ted Creedon wrote: > Noticed this on startup: > > Missing separate debuginfo for /usr/lib64/libgobject-2.0.so.0 > Try: zypper install -C > "debuginfo(build-id)=a3f8edc19f47fd2290dbbf3d05670ed13ba6a93c" > Traceback (most recent call last): > File "/usr/share/gdb/auto-load/usr/lib64/ > libgobject-2.0.so.0.3800.2-gdb.py", line 9, in > from gobject import register > File "/usr/share/glib-2.0/gdb/gobject.py", line 3, in > import gdb.backtrace > ImportError: No module named backtrace > Missing separate debuginfo for /usr/lib64/libglib-2.0.so.0 > T > > > On Mon, Mar 3, 2014 at 4:12 PM, Ted Creedon wrote: > >> do I need a pointer to the sources for >> >> libgobject-2_0-0 - General-Purpose Utility Library -- Object-Oriented >> Framework for C? >> >> >> >> >> On Mon, Mar 3, 2014 at 3:47 PM, John Ralls wrote: >> >>> >>> On Mar 3, 2014, at 3:30 PM, Ted Creedon wrote: >>> >>> > Program received signal SIGSEGV, Segmentation fault. >>> > 0x7fffef356cac in g_type_check_instance_is_a () from >>> > /usr/lib64/libgobject-2.0.so.0 >>> > >>> > >>> > can't do a bt because the fault freezes the X Screen >>> > >>> > had to ssh in from another box & kill -TERM gdb >>> > >>> > Should I do a debug build? >>> >>> Yes, of course. You'll also want the symbols and sources at least for >>> glib. >>> >>> Regards, >>> John Ralls >>> >>> >> > ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: 2.6.2 segfaulting
Noticed this on startup: Missing separate debuginfo for /usr/lib64/libgobject-2.0.so.0 Try: zypper install -C "debuginfo(build-id)=a3f8edc19f47fd2290dbbf3d05670ed13ba6a93c" Traceback (most recent call last): File "/usr/share/gdb/auto-load/usr/lib64/libgobject-2.0.so.0.3800.2-gdb.py", line 9, in from gobject import register File "/usr/share/glib-2.0/gdb/gobject.py", line 3, in import gdb.backtrace ImportError: No module named backtrace Missing separate debuginfo for /usr/lib64/libglib-2.0.so.0 T On Mon, Mar 3, 2014 at 4:12 PM, Ted Creedon wrote: > do I need a pointer to the sources for > > libgobject-2_0-0 - General-Purpose Utility Library -- Object-Oriented > Framework for C? > > > > > On Mon, Mar 3, 2014 at 3:47 PM, John Ralls wrote: > >> >> On Mar 3, 2014, at 3:30 PM, Ted Creedon wrote: >> >> > Program received signal SIGSEGV, Segmentation fault. >> > 0x7fffef356cac in g_type_check_instance_is_a () from >> > /usr/lib64/libgobject-2.0.so.0 >> > >> > >> > can't do a bt because the fault freezes the X Screen >> > >> > had to ssh in from another box & kill -TERM gdb >> > >> > Should I do a debug build? >> >> Yes, of course. You'll also want the symbols and sources at least for >> glib. >> >> Regards, >> John Ralls >> >> > ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
2.6.2 segfaulting
Program received signal SIGSEGV, Segmentation fault. 0x7fffef356cac in g_type_check_instance_is_a () from /usr/lib64/libgobject-2.0.so.0 can't do a bt because the fault freezes the X Screen had to ssh in from another box & kill -TERM gdb Should I do a debug build? Tedc ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: 2.6.2 comple
/usr/local/share needs to be explicitly added to XDG_DATA_DIRS echo $XDG_DATA_DIRS /usr/share:/usr/share:/usr/local:/usr/local/share ted On Mon, Mar 3, 2014 at 9:02 AM, John Ralls wrote: > > On Mar 3, 2014, at 8:32 AM, Ted Creedon wrote: > > > Compiles fine but needs one last thing to run: > > > > export XDG_DATA_DIRS=$XDG_DATA_DIRS:/usr/local/share > > ldconfig > > > > #gnucash: error while loading shared libraries: libgnc-gnome.so.0: cannot > > open shared object file: No such file or directory > > > > tedc > > > > PS Where are the docs? > > Or `unset XDG_DATA_DIRS`. Does your distro misconfigure it or did you do > that yourself? > > The online released user docs are at http://www.gnucash.org/documentation, > and the nightly snapshots from git master at http://code.gnucash.org/docs/, > where the user docs are in their respective locales and the developer docs > are in HEAD. > > Regards, > John Ralls > > > ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
2.6.2 comple
Compiles fine but needs one last thing to run: export XDG_DATA_DIRS=$XDG_DATA_DIRS:/usr/local/share ldconfig #gnucash: error while loading shared libraries: libgnc-gnome.so.0: cannot open shared object file: No such file or directory tedc PS Where are the docs? ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Gnucash Segfaults
ps in a make what should the prefix be? tedc On Fri, Feb 28, 2014 at 5:15 AM, Ted Creedon wrote: > needs to set to /usr/local/shareexport > > export XDG_DATA_DIRS=$XDG_DATA_DIRS:/usr/local/share > > now running fine > > lets see how my tax run works out > > thank you > > tedc > > > On Fri, Feb 28, 2014 at 4:43 AM, Geert Janssens > wrote: > >> Ah, it looks like gnucash (or better GIO) is not finding the gsettings >> schemas. GIO aborts in that case. >> >> >> >> I have seen this happen before when environment variable XDG_DATA_DIRS is >> not set correctly for your specific set up. >> >> >> >> Is XDG_DATA_DIRS set on your system ? >> >> >> >> What is your installation prefix ? >> >> >> >> Geert >> >> >> >> On Friday 28 February 2014 04:15:53 Ted Creedon wrote: >> >> > Yes, removed the cp - it was there all the time >> >> > Yes make install >> >> > >> >> > strace gnucash: >> >> > >> >> > open("/etc/localtime", O_RDONLY) = 6 >> >> > fstat(6, {st_mode=S_IFREG|0644, st_size=2819, ...}) = 0 >> >> > mmap(NULL, 2819, PROT_READ, MAP_PRIVATE, 6, 0) = 0x7f7dcbf7 >> >> > close(6) = 0 >> >> > munmap(0x7f7dcbf7, 2819) = 0 >> >> > write(3, "* 04:01:07 OTHER Sett"..., 83) = 83 >> >> > --- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} --- >> >> > +++ killed by SIGTRAP +++ >> >> > >> >> > >> >> > gdb Stack trace: >> >> > Program received signal SIGTRAP, Trace/breakpoint trap. >> >> > 0x73b3d309 in g_logv () from /usr/lib64/libglib-2.0.so.0 >> >> > (gdb) bt full >> >> > #0 0x73b3d309 in g_logv () from /usr/lib64/libglib-2.0.so.0 >> >> > No symbol table info available. >> >> > #1 0x73b3d452 in g_log () from /usr/lib64/libglib-2.0.so.0 >> >> > No symbol table info available. >> >> > #2 0x7454f5b7 in ?? () from /usr/lib64/libgio-2.0.so.0 >> >> > No symbol table info available. >> >> > #3 0x73e046a9 in ?? () from /usr/lib64/libgobject-2.0.so.0 >> >> > No symbol table info available. >> >> > #4 0x73e06424 in g_object_new_valist () from >> >> > /usr/lib64/libgobject-2.0.so.0 >> >> > No symbol table info available. >> >> > #5 0x73e06804 in g_object_new () from >> >> > /usr/lib64/libgobject-2.0.so.0 >> >> > No symbol table info available. >> >> > #6 0x771bf9d8 in gnc_gsettings_get_schema_ptr >> >> > (schema_str=schema_str@entry=0x771d06f7 "general") at >> >> > gnc-gsettings.c:104 >> >> > gset = 0x0 >> >> > full_name = 0x76c4e0 "org.gnucash.general" >> >> > __FUNCTION__ = "gnc_gsettings_get_schema_ptr" >> >> > #7 0x771c03ef in gnc_gsettings_get_float >> >> > (schema=0x771d06f7 "general", key=0x771d10da "retain-days") >> >> > at gnc-gsettings.c:354 >> >> > schema_ptr = >> >> > __PRETTY_FUNCTION__ = "gnc_gsettings_get_float" >> >> > __FUNCTION__ = "gnc_gsettings_get_float" >> >> > #8 0x771c2187 in file_retain_changed_cb (user_data=0x0, >> >> > key=0x0, gsettings=0x0) at gnc-prefs-utils.c:48 >> >> > days = >> >> > #9 0x771c23b5 in file_retain_changed_cb (user_data=0x0, >> >> > key=0x0, gsettings=0x0) at gnc-prefs-utils.c:123 >> >> > No locals. >> >> > #10 gnc_prefs_init () at gnc-prefs-utils.c:89 >> >> > __FUNCTION__ = "gnc_prefs_init" >> >> > #11 0x7744f8a3 in gnc_gui_init () at gnc-gnome-utils.c:672 >> >> > main_window = 0x0 >> >> > map = >> >> > idx = >> >> > icon_filenames = {0x774aaeef "gnucash-icon-16x16.png", >> >> > 0x774aaf06 "gnucash-icon-32x32.png", >> >> > 0x774aaf1d "gnucash-icon-48x48.png", 0x0} >> >> > icons = 0x763720 = {0x763a80} >> >> > fullname = 0x76d660 "" >> >> > __FUNCTION__ = "gnc_gui_init" >> >> > #12 0x00402bd6 in main (argc=1, argv=0x7fffd8b8) at >> >> > gnucash-bin.c:773 >> >> > sys_locale = 0x654500 ":0" >> >> > __FUNCTION__ = "main" >> >> > >> >> > >> >> > >> >> >> > > ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Gnucash Segfaults
needs to set to /usr/local/shareexport export XDG_DATA_DIRS=$XDG_DATA_DIRS:/usr/local/share now running fine lets see how my tax run works out thank you tedc On Fri, Feb 28, 2014 at 4:43 AM, Geert Janssens wrote: > Ah, it looks like gnucash (or better GIO) is not finding the gsettings > schemas. GIO aborts in that case. > > > > I have seen this happen before when environment variable XDG_DATA_DIRS is > not set correctly for your specific set up. > > > > Is XDG_DATA_DIRS set on your system ? > > > > What is your installation prefix ? > > > > Geert > > > > On Friday 28 February 2014 04:15:53 Ted Creedon wrote: > > > Yes, removed the cp - it was there all the time > > > Yes make install > > > > > > strace gnucash: > > > > > > open("/etc/localtime", O_RDONLY) = 6 > > > fstat(6, {st_mode=S_IFREG|0644, st_size=2819, ...}) = 0 > > > mmap(NULL, 2819, PROT_READ, MAP_PRIVATE, 6, 0) = 0x7f7dcbf7 > > > close(6) = 0 > > > munmap(0x7f7dcbf7, 2819) = 0 > > > write(3, "* 04:01:07 OTHER Sett"..., 83) = 83 > > > --- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} --- > > > +++ killed by SIGTRAP +++ > > > > > > > > > gdb Stack trace: > > > Program received signal SIGTRAP, Trace/breakpoint trap. > > > 0x73b3d309 in g_logv () from /usr/lib64/libglib-2.0.so.0 > > > (gdb) bt full > > > #0 0x73b3d309 in g_logv () from /usr/lib64/libglib-2.0.so.0 > > > No symbol table info available. > > > #1 0x73b3d452 in g_log () from /usr/lib64/libglib-2.0.so.0 > > > No symbol table info available. > > > #2 0x7454f5b7 in ?? () from /usr/lib64/libgio-2.0.so.0 > > > No symbol table info available. > > > #3 0x73e046a9 in ?? () from /usr/lib64/libgobject-2.0.so.0 > > > No symbol table info available. > > > #4 0x73e06424 in g_object_new_valist () from > > > /usr/lib64/libgobject-2.0.so.0 > > > No symbol table info available. > > > #5 0x73e06804 in g_object_new () from > > > /usr/lib64/libgobject-2.0.so.0 > > > No symbol table info available. > > > #6 0x771bf9d8 in gnc_gsettings_get_schema_ptr > > > (schema_str=schema_str@entry=0x771d06f7 "general") at > > > gnc-gsettings.c:104 > > > gset = 0x0 > > > full_name = 0x76c4e0 "org.gnucash.general" > > > __FUNCTION__ = "gnc_gsettings_get_schema_ptr" > > > #7 0x771c03ef in gnc_gsettings_get_float > > > (schema=0x771d06f7 "general", key=0x771d10da "retain-days") > > > at gnc-gsettings.c:354 > > > schema_ptr = > > > __PRETTY_FUNCTION__ = "gnc_gsettings_get_float" > > > __FUNCTION__ = "gnc_gsettings_get_float" > > > #8 0x771c2187 in file_retain_changed_cb (user_data=0x0, > > > key=0x0, gsettings=0x0) at gnc-prefs-utils.c:48 > > > days = > > > #9 0x771c23b5 in file_retain_changed_cb (user_data=0x0, > > > key=0x0, gsettings=0x0) at gnc-prefs-utils.c:123 > > > No locals. > > > #10 gnc_prefs_init () at gnc-prefs-utils.c:89 > > > __FUNCTION__ = "gnc_prefs_init" > > > #11 0x7744f8a3 in gnc_gui_init () at gnc-gnome-utils.c:672 > > > main_window = 0x0 > > > map = > > > idx = > > > icon_filenames = {0x774aaeef "gnucash-icon-16x16.png", > > > 0x774aaf06 "gnucash-icon-32x32.png", > > > 0x774aaf1d "gnucash-icon-48x48.png", 0x0} > > > icons = 0x763720 = {0x763a80} > > > fullname = 0x76d660 "" > > > __FUNCTION__ = "gnc_gui_init" > > > #12 0x00402bd6 in main (argc=1, argv=0x7fffd8b8) at > > > gnucash-bin.c:773 > > > sys_locale = 0x654500 ":0" > > > __FUNCTION__ = "main" > > > > > > > > > > > > ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Gnucash Segfaults
echo $XDG_DATA_DIRS /usr/share:/usr/share no prefixes On Fri, Feb 28, 2014 at 4:43 AM, Geert Janssens wrote: > Ah, it looks like gnucash (or better GIO) is not finding the gsettings > schemas. GIO aborts in that case. > > > > I have seen this happen before when environment variable XDG_DATA_DIRS is > not set correctly for your specific set up. > > > > Is XDG_DATA_DIRS set on your system ? > > > > What is your installation prefix ? > > > > Geert > > > > On Friday 28 February 2014 04:15:53 Ted Creedon wrote: > > > Yes, removed the cp - it was there all the time > > > Yes make install > > > > > > strace gnucash: > > > > > > open("/etc/localtime", O_RDONLY) = 6 > > > fstat(6, {st_mode=S_IFREG|0644, st_size=2819, ...}) = 0 > > > mmap(NULL, 2819, PROT_READ, MAP_PRIVATE, 6, 0) = 0x7f7dcbf7 > > > close(6) = 0 > > > munmap(0x7f7dcbf7, 2819) = 0 > > > write(3, "* 04:01:07 OTHER Sett"..., 83) = 83 > > > --- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} --- > > > +++ killed by SIGTRAP +++ > > > > > > > > > gdb Stack trace: > > > Program received signal SIGTRAP, Trace/breakpoint trap. > > > 0x73b3d309 in g_logv () from /usr/lib64/libglib-2.0.so.0 > > > (gdb) bt full > > > #0 0x73b3d309 in g_logv () from /usr/lib64/libglib-2.0.so.0 > > > No symbol table info available. > > > #1 0x73b3d452 in g_log () from /usr/lib64/libglib-2.0.so.0 > > > No symbol table info available. > > > #2 0x7454f5b7 in ?? () from /usr/lib64/libgio-2.0.so.0 > > > No symbol table info available. > > > #3 0x73e046a9 in ?? () from /usr/lib64/libgobject-2.0.so.0 > > > No symbol table info available. > > > #4 0x73e06424 in g_object_new_valist () from > > > /usr/lib64/libgobject-2.0.so.0 > > > No symbol table info available. > > > #5 0x73e06804 in g_object_new () from > > > /usr/lib64/libgobject-2.0.so.0 > > > No symbol table info available. > > > #6 0x771bf9d8 in gnc_gsettings_get_schema_ptr > > > (schema_str=schema_str@entry=0x771d06f7 "general") at > > > gnc-gsettings.c:104 > > > gset = 0x0 > > > full_name = 0x76c4e0 "org.gnucash.general" > > > __FUNCTION__ = "gnc_gsettings_get_schema_ptr" > > > #7 0x771c03ef in gnc_gsettings_get_float > > > (schema=0x771d06f7 "general", key=0x771d10da "retain-days") > > > at gnc-gsettings.c:354 > > > schema_ptr = > > > __PRETTY_FUNCTION__ = "gnc_gsettings_get_float" > > > __FUNCTION__ = "gnc_gsettings_get_float" > > > #8 0x771c2187 in file_retain_changed_cb (user_data=0x0, > > > key=0x0, gsettings=0x0) at gnc-prefs-utils.c:48 > > > days = > > > #9 0x771c23b5 in file_retain_changed_cb (user_data=0x0, > > > key=0x0, gsettings=0x0) at gnc-prefs-utils.c:123 > > > No locals. > > > #10 gnc_prefs_init () at gnc-prefs-utils.c:89 > > > __FUNCTION__ = "gnc_prefs_init" > > > #11 0x7744f8a3 in gnc_gui_init () at gnc-gnome-utils.c:672 > > > main_window = 0x0 > > > map = > > > idx = > > > icon_filenames = {0x774aaeef "gnucash-icon-16x16.png", > > > 0x774aaf06 "gnucash-icon-32x32.png", > > > 0x774aaf1d "gnucash-icon-48x48.png", 0x0} > > > icons = 0x763720 = {0x763a80} > > > fullname = 0x76d660 "" > > > __FUNCTION__ = "gnc_gui_init" > > > #12 0x00402bd6 in main (argc=1, argv=0x7fffd8b8) at > > > gnucash-bin.c:773 > > > sys_locale = 0x654500 ":0" > > > __FUNCTION__ = "main" > > > > > > > > > > > > ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Gnucash Segfaults
Yes, removed the cp - it was there all the time Yes make install strace gnucash: open("/etc/localtime", O_RDONLY)= 6 fstat(6, {st_mode=S_IFREG|0644, st_size=2819, ...}) = 0 mmap(NULL, 2819, PROT_READ, MAP_PRIVATE, 6, 0) = 0x7f7dcbf7 close(6)= 0 munmap(0x7f7dcbf7, 2819)= 0 write(3, "* 04:01:07 OTHER Sett"..., 83) = 83 --- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} --- +++ killed by SIGTRAP +++ gdb Stack trace: Program received signal SIGTRAP, Trace/breakpoint trap. 0x73b3d309 in g_logv () from /usr/lib64/libglib-2.0.so.0 (gdb) bt full #0 0x73b3d309 in g_logv () from /usr/lib64/libglib-2.0.so.0 No symbol table info available. #1 0x73b3d452 in g_log () from /usr/lib64/libglib-2.0.so.0 No symbol table info available. #2 0x7454f5b7 in ?? () from /usr/lib64/libgio-2.0.so.0 No symbol table info available. #3 0x73e046a9 in ?? () from /usr/lib64/libgobject-2.0.so.0 No symbol table info available. #4 0x73e06424 in g_object_new_valist () from /usr/lib64/libgobject-2.0.so.0 No symbol table info available. #5 0x73e06804 in g_object_new () from /usr/lib64/libgobject-2.0.so.0 No symbol table info available. #6 0x771bf9d8 in gnc_gsettings_get_schema_ptr (schema_str=schema_str@entry=0x771d06f7 "general") at gnc-gsettings.c:104 gset = 0x0 full_name = 0x76c4e0 "org.gnucash.general" __FUNCTION__ = "gnc_gsettings_get_schema_ptr" #7 0x771c03ef in gnc_gsettings_get_float (schema=0x771d06f7 "general", key=0x771d10da "retain-days") at gnc-gsettings.c:354 schema_ptr = __PRETTY_FUNCTION__ = "gnc_gsettings_get_float" __FUNCTION__ = "gnc_gsettings_get_float" #8 0x771c2187 in file_retain_changed_cb (user_data=0x0, key=0x0, gsettings=0x0) at gnc-prefs-utils.c:48 days = #9 0x771c23b5 in file_retain_changed_cb (user_data=0x0, key=0x0, gsettings=0x0) at gnc-prefs-utils.c:123 No locals. #10 gnc_prefs_init () at gnc-prefs-utils.c:89 __FUNCTION__ = "gnc_prefs_init" #11 0x7744f8a3 in gnc_gui_init () at gnc-gnome-utils.c:672 main_window = 0x0 map = idx = icon_filenames = {0x774aaeef "gnucash-icon-16x16.png", 0x774aaf06 "gnucash-icon-32x32.png", 0x774aaf1d "gnucash-icon-48x48.png", 0x0} icons = 0x763720 = {0x763a80} fullname = 0x76d660 "" __FUNCTION__ = "gnc_gui_init" #12 0x00402bd6 in main (argc=1, argv=0x7fffd8b8) at gnucash-bin.c:773 sys_locale = 0x654500 ":0" __FUNCTION__ = "main" On Fri, Feb 28, 2014 at 4:10 AM, Geert Janssens wrote: > Hmm, you should not be copying files around like that. That makes > everything much harder to track. > > > > First question: how do you install gnucash ? I presume using make install ? > > > > What prefix are you using for this ? I strongly suggest using something > other than /usr or /usr/local. These two paths are special cases for the > linker/installer and should only be used by package managers. In case your > intent it to package gnucash for suse, you can ignore this bit :) > > > > Lastly: libgnc-gnome.so is an internal library for gnucash. It should get > installed automatically when running make install. > > > > If that's not the case on your system, you should first figure out why > that didn't happen. > > > > Geert > > > > On Friday 28 February 2014 04:00:30 Ted Creedon wrote: > > > deleted 2.4, 2.6.1 compiled fine but when executing: > > > > > > gnucash: error while loading shared libraries: libgnc-gnome.so.0: > > > cannot open shared object file: No such file or directory > > > > > > libgnc-gnome. was deleted when 2.4 was removed > > > > > > and its not in the suse distro. So I moved it & did ldconfig > > > > > > cp /data/gnucash-2.6.1/src/gnome/.libs/libgnc-gnome.so > > > /usr/lib64/libgnc-gnome.soi > > > > > > & now get [1]+ Trace/breakpoint trap gnucash > > > > > > > > > > > > tedc > > > > > > > > > > > > > > > > > > On Fri, Feb 28, 2014 at 3:28 AM, Geert Janssens > > > > > > wrote: > > > > On Friday 28 February 2014 02:12:23 Ted Creedon wrote: > > > > > It might be best to work on 2.6..1. > > > > > > > > > > > > > > > > > > > > Here'e the 2.6.1 compile error - which involves libgnc: > > > > > > > > > > &g
Re: Gnucash Segfaults
deleted 2.4, 2.6.1 compiled fine but when executing: gnucash: error while loading shared libraries: libgnc-gnome.so.0: cannot open shared object file: No such file or directory libgnc-gnome. was deleted when 2.4 was removed and its not in the suse distro. So I moved it & did ldconfig cp /data/gnucash-2.6.1/src/gnome/.libs/libgnc-gnome.so /usr/lib64/libgnc-gnome.soi & now get [1]+ Trace/breakpoint trap gnucash tedc On Fri, Feb 28, 2014 at 3:28 AM, Geert Janssens wrote: > On Friday 28 February 2014 02:12:23 Ted Creedon wrote: > > > It might be best to work on 2.6..1. > > > > > > Here'e the 2.6.1 compile error - which involves libgnc: > > > > > > libtool: link: gcc -Wdeclaration-after-statement -g -O2 -Wall -Wunused > > > -Wmissing-prototypes -Wmissing-declarations -Wno-unused -o > > > .libs/gnucash gnucash-bin.o -pthread -Wl,--export-dynamic -pthread > > > ../../src/register/ledger-core/.libs/libgncmod-ledger-core.so > > > ../../src/report/report-gnome/.libs/libgncmod-report-gnome.so > > > ../../src/gnome/.libs/libgnc-gnome.so > > > ../../src/gnome-utils/.libs/libgncmod-gnome-utils.so > > > ../../src/app-utils/.libs/libgncmod-app-utils.so > > > ../../src/engine/.libs/libgncmod-engine.so > > > ../../src/gnc-module/.libs/libgnc-module.so > > > ../../src/core-utils/.libs/libgnc-core-utils.so > > > ../../src/libqof/qof/.libs/libgnc-qof.so /usr/lib64/libguile.so -lgmp > > > -lcrypt /usr/lib64/libltdl.so -lgthread-2.0 -lgmodule-2.0 > > > -lgtk-x11-2.0 -lgdk-x11-2.0 -lpangocairo-1.0 -latk-1.0 -lcairo > > > -lgdk_pixbuf-2.0 -lgio-2.0 -lpangoft2-1.0 -lpango-1.0 -lgobject-2.0 > > > -lglib-2.0 -lfontconfig -lfreetype -lm -pthread -Wl,-rpath > > > -Wl,/usr/local/lib64/gnucash -Wl,-rpath -Wl,/usr/lib64 > > > /usr/lib64/libgnc-backend-xml-utils.so.0: undefined reference to > > > `safe_strcmp' > > > collect2: error: ld returned 1 exit status > > > make[4]: *** [gnucash] Error 1 > > > make[3]: *** [all-recursive] Error 1 > > > make[2]: *** [all-recursive] Error 1 > > > make[1]: *** [all-recursive] Error 1 > > > make: *** [all] Error 2 > > > > > That looks like your linker is trying to link against libraries from an > older gnucash version installed on the system. safe_strcmp is not used in > gnucash 2.6.1 anymore. > > > > There is a bug report for this [1]. The workaround is to remove gnucash > from your system before compiling. > > > > Geert > > > > [1] https://bugzilla.gnome.org/show_bug.cgi?id=644897 > ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Installing gnucash-2.6.1-1.1.x86_64.rpm
rpmfiind has suse rpm's anyway I grabbed lobofx6 from suse factory & has the same error tedc On Fri, Feb 28, 2014 at 3:20 AM, Micha Lenk wrote: > Hi Ted, > > > On 28.02.2014 12:13, Ted Creedon wrote: > >> Got 2.6.1 from suse >> rpm --upgrade --test gnucash-2.6.1-1.1.x86_64.rpm >> error: Failed dependencies: >> libofx.so.6()(64bit) is needed by gnucash-2.6.1-1.1.x86_64 >> >> OK got libofx.so.6 from rpm find >> >> rpm --install --test libofx6-0.9.9-1.1.x86_64.rpm >> error: Failed dependencies: >> libofx >= 0.9.9 is needed by libofx6-0.9.9-1.1.x86_64 >> >> rpm -qa|grep libofx >> libofx-0.9.8-2.1.4.x86_64 >> libofx5-0.9.8-2.1.4.x86_64 >> >> Not a clue why libofx6 won't install >> > > If I understood you correctly you got Gnucash from SuSE and libofx from > RPM find. These two sources likely have differences in how they package the > software. In general it is best common practice to not mix software from > different sources/distributions. So you might get better results if you > search for a libofx package originating from SuSE too. > > Good luck. > > Regards, > Micha > ___ > gnucash-devel mailing list > gnucash-devel@gnucash.org > https://lists.gnucash.org/mailman/listinfo/gnucash-devel > ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Installing gnucash-2.6.1-1.1.x86_64.rpm
Got 2.6.1 from suse rpm --upgrade --test gnucash-2.6.1-1.1.x86_64.rpm error: Failed dependencies: libofx.so.6()(64bit) is needed by gnucash-2.6.1-1.1.x86_64 OK got libofx.so.6 from rpm find rpm --install --test libofx6-0.9.9-1.1.x86_64.rpm error: Failed dependencies: libofx >= 0.9.9 is needed by libofx6-0.9.9-1.1.x86_64 rpm -qa|grep libofx libofx-0.9.8-2.1.4.x86_64 libofx5-0.9.8-2.1.4.x86_64 Not a clue why libofx6 won't install Still a compile problem too, which I'd be more comfortable w/ fixing tedc ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Gnucash Segfaults
ibgtk-x11-2.0.so.0 No symbol table info available. #41 0x7624e0d4 in ?? () from /usr/lib64/libgtk-x11-2.0.so.0 No symbol table info available. #42 0x762c69d5 in ?? () from /usr/lib64/libgtk-x11-2.0.so.0 No symbol table info available. #43 0x73054292 in g_closure_invoke () from /usr/lib64/libgobject-2.0.so.0 No symbol table info available. #44 0x73065a6b in ?? () from /usr/lib64/libgobject-2.0.so.0 No symbol table info available. #45 0x7306d689 in g_signal_emit_valist () from /usr/lib64/libgobject-2.0.so.0 No symbol table info available. #46 0x7306dc72 in g_signal_emit () from /usr/lib64/libgobject-2.0.so.0 No symbol table info available. #47 0x763d6864 in ?? () from /usr/lib64/libgtk-x11-2.0.so.0 No symbol table info available. #48 0x7624f548 in gtk_container_propagate_expose () from /usr/lib64/libgtk-x11-2.0.so.0 No symbol table info available. #49 0x7624e0d4 in ?? () from /usr/lib64/libgtk-x11-2.0.so.0 No symbol table info available. #50 0x762c69d5 in ?? () from /usr/lib64/libgtk-x11-2.0.so.0 No symbol table info available. ---Type to continue, or q to quit--- #51 0x73054318 in g_closure_invoke () from /usr/lib64/libgobject-2.0.so.0 No symbol table info available. #52 0x73065a6b in ?? () from /usr/lib64/libgobject-2.0.so.0 No symbol table info available. #53 0x7306d689 in g_signal_emit_valist () from /usr/lib64/libgobject-2.0.so.0 No symbol table info available. #54 0x7306dc72 in g_signal_emit () from /usr/lib64/libgobject-2.0.so.0 No symbol table info available. #55 0x763d6864 in ?? () from /usr/lib64/libgtk-x11-2.0.so.0 No symbol table info available. #56 0x762c57d0 in gtk_main_do_event () from /usr/lib64/libgtk-x11-2.0.so.0 No symbol table info available. #57 0x73ea276f in ?? () from /usr/lib64/libgdk-x11-2.0.so.0 No symbol table info available. #58 0x73e9f3ae in ?? () from /usr/lib64/libgdk-x11-2.0.so.0 No symbol table info available. #59 0x73e9fc98 in gdk_window_process_all_updates () from /usr/lib64/libgdk-x11-2.0.so.0 No symbol table info available. #60 0x73e9fcf9 in ?? () from /usr/lib64/libgdk-x11-2.0.so.0 No symbol table info available. #61 0x73e7f537 in ?? () from /usr/lib64/libgdk-x11-2.0.so.0 No symbol table info available. #62 0x75ed7316 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 No symbol table info available. #63 0x75ed7668 in ?? () from /usr/lib64/libglib-2.0.so.0 No symbol table info available. #64 0x75ed7a6a in g_main_loop_run () from /usr/lib64/libglib-2.0.so.0 No symbol table info available. #65 0x762c4627 in gtk_main () from /usr/lib64/libgtk-x11-2.0.so.0 No symbol table info available. #66 0x778ef5d9 in gnc_ui_start_event_loop () from /usr/lib64/gnucash/libgncmod-gnome-utils.so No symbol table info available. #67 0x004036d0 in _start () No symbol table info available. On Thu, Feb 27, 2014 at 5:51 PM, Derek Atkins wrote: > Hi, > > On Thu, February 27, 2014 8:16 pm, Ted Creedon wrote: > > gnucash[12625]: segfault at 10016 ip 7f15bd5d4cac sp > > 7fff24f1a228 error 4 in > libgobject-2.0.so.0.3800.2[7f15bd5a2000+4f000] > > Any chance you could pull a full backtrace? This says that the crash > happened in one of GnuCash's dependent libraries, libgobject, which is > part of glib. Without a full trace there's no way we could track this > down. See http://wiki.gnucash.org/wiki/Stack_Trace > > > built from r4dc6397+ on 2013-09-28. > > No idea what release this is... > > > OpenSuSe 13.1 > > > > What is a stable release? > > 2.6.1 is the current stable release. > > > Tedc > > -derek > > -- >Derek Atkins 617-623-3745 >de...@ihtfp.com www.ihtfp.com >Computer and Internet Security Consultant > > ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Gnucash Segfaults
It might be best to work on 2.6..1. Here'e the 2.6.1 compile error - which involves libgnc: libtool: link: gcc -Wdeclaration-after-statement -g -O2 -Wall -Wunused -Wmissing-prototypes -Wmissing-declarations -Wno-unused -o .libs/gnucash gnucash-bin.o -pthread -Wl,--export-dynamic -pthread ../../src/register/ledger-core/.libs/libgncmod-ledger-core.so ../../src/report/report-gnome/.libs/libgncmod-report-gnome.so ../../src/gnome/.libs/libgnc-gnome.so ../../src/gnome-utils/.libs/libgncmod-gnome-utils.so ../../src/app-utils/.libs/libgncmod-app-utils.so ../../src/engine/.libs/libgncmod-engine.so ../../src/gnc-module/.libs/libgnc-module.so ../../src/core-utils/.libs/libgnc-core-utils.so ../../src/libqof/qof/.libs/libgnc-qof.so /usr/lib64/libguile.so -lgmp -lcrypt /usr/lib64/libltdl.so -lgthread-2.0 -lgmodule-2.0 -lgtk-x11-2.0 -lgdk-x11-2.0 -lpangocairo-1.0 -latk-1.0 -lcairo -lgdk_pixbuf-2.0 -lgio-2.0 -lpangoft2-1.0 -lpango-1.0 -lgobject-2.0 -lglib-2.0 -lfontconfig -lfreetype -lm -pthread -Wl,-rpath -Wl,/usr/local/lib64/gnucash -Wl,-rpath -Wl,/usr/lib64 /usr/lib64/libgnc-backend-xml-utils.so.0: undefined reference to `safe_strcmp' collect2: error: ld returned 1 exit status make[4]: *** [gnucash] Error 1 make[3]: *** [all-recursive] Error 1 make[2]: *** [all-recursive] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 On Thu, Feb 27, 2014 at 5:51 PM, Derek Atkins wrote: > Hi, > > On Thu, February 27, 2014 8:16 pm, Ted Creedon wrote: > > gnucash[12625]: segfault at 10016 ip 7f15bd5d4cac sp > > 7fff24f1a228 error 4 in > libgobject-2.0.so.0.3800.2[7f15bd5a2000+4f000] > > Any chance you could pull a full backtrace? This says that the crash > happened in one of GnuCash's dependent libraries, libgobject, which is > part of glib. Without a full trace there's no way we could track this > down. See http://wiki.gnucash.org/wiki/Stack_Trace > > > built from r4dc6397+ on 2013-09-28. > > No idea what release this is... > > > OpenSuSe 13.1 > > > > What is a stable release? > > 2.6.1 is the current stable release. > > > Tedc > > -derek > > -- >Derek Atkins 617-623-3745 >de...@ihtfp.com www.ihtfp.com >Computer and Internet Security Consultant > > ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Gnucash Segfaults
gnucash[12625]: segfault at 10016 ip 7f15bd5d4cac sp 7fff24f1a228 error 4 in libgobject-2.0.so.0.3800.2[7f15bd5a2000+4f000] built from r4dc6397+ on 2013-09-28. OpenSuSe 13.1 What is a stable release? Tedc ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Bitcoins
better add bitcoins and the upcoming gold bitcoins from BOE/Alderney Could someone trademark new currency symbols for both? Like a B with superimposed || for bitcoins & a G with superimposed ||? Would make gnucash the only software capable of tracking Bitcoins. Tedc ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Bug 336843 - Attach files to Transactions
File bloat should be avoided adding scanned files would make the data file impossible to administer Have you considered a check & repair function to detect link rot? On Thu, Nov 14, 2013 at 9:55 PM, Bob Brush wrote: > I really like the file management implementation of the program > Shotwell, the comments on Gramps reminded me. It is much the same > situation as here, some users want the program to store the files, > others say please don't touch my files, so it handles this by prompting > at the beginning, and by answering the question the user self educates > and creates the appropriate expectations. If this would be a good > model, I'm thinking it would work like this: > > "GnuCash can copy the image into your data folder or it can import > without copying" Cancel, Copy Image, Import in Place? > > I don't know if image is the correct wording, it could be receipt if > that isn't limiting, or pdf, I would hate to limit some future case not > yet imagined, maybe just "file"? > > I also find the "Preferences" in shotwell to be helpful and may also be > a good model? If so maybe like this: > > Import files to: (default to same location as data file) > Directory structure: (Custom) > Pattern: (%Y/%B/%B %d, %Y - %A) > Example - 2009/March/March 10, 2009 - Tuesday > Rename imported files to lowercase: (y/n) > > I think that using this type of file organization would be great and > allow flexibility, some will want less than ten folders for their > images, others will want a labyrinth of organization, and others will > want to use either an existing system or something unrelated to the > program to organize. It would also be best to have patterns for GnuCash > specific things in case you would want your image folders to have the > same pattern as the account tree list, or organize by vendor, customer, > or employee? > > And finally not to throw in the kitchen sink, but it would be cool to > add metadata to the file also, maybe a visible summary of the > transaction (for those outside GnuCash) it is linked to with a gnc link > (gncthing:thing=eb9a14a0e076e0029bfd2e623b2f2cc8#) to the transaction, > the Company name, the date of the transaction it was linked to, and/or > things like that.. > > Would it be good to display the file in GnuCash using webkit? > Would it be good to have thumbnails? > > -Bob > > > > On Wed, 2013-11-13 at 20:55 -0800, John Ralls wrote: > > On Nov 13, 2013, at 5:09 PM, Patrick wrote: > > > > > Indeed, a very relevant question. I had thought about storing the file > > > itself in the database as a binary blob, but had concerns the db would > > > grow too large and cause other stability issues. Also, that wouldn't > > > work well with the XML back-end. > > > > > > I'm not sure how to ensure file availability, given any other program > > > or user outside of GNUCash could alter the filesystem (and, for > > > instance, delete the file.) That sounds intractable to me, assuming a > > > file:// url is used. Granted, there's nothing to guarantee an > > > http/https url will be around at next retrieval either. There is no > > > URL validation code in the input phase of the "Associate Location" > > > function - it'll just fail on retrieval. Same problem, different > > > space. > > > > > > Fundamentally, they are just links. But, to Derek's point, how then to > > > educate the user-base so as not to cause resentment when someone's > > > relative removes the linked files and the user blames GnuCash. > > > > > > In the end, I gave up pondering this further as I wasn't getting > > > anywhere. Definitely non-trivial. > > > > The other application project I work on, Gramps [1], has a similar > feature for linking "media" (image) files. It offers some tools for > (re)configuring the root path on relative file names along with an option > for storing either relative or absolute pathnames and a tool for switching > from relative to absolute and back. It also offers an option to include > "media" in a zipped backup bundle. > > > > The way to manage user expectations is documentation, which there isn't > any yet for this new feature. Considering that I'm holding off string and > feature freeze for this, is it *really* mature enough to add 6 weeks before > release? Roger it's a widely-requested feature, roger that someone made a > public announcement implying that it's going to be in the next release, > roger the code is simple and straightforward. But it's not documented and > we don't really know what users expect. Can we get that information and > meet the bulk of those expectations in 6 weeks? > > > > Regards, > > John Ralls > > > > [1] http://www.gramps-project.org > > ___ > > gnucash-devel mailing list > > gnucash-devel@gnucash.org > > https://lists.gnucash.org/mailman/listinfo/gnucash-devel > > -- > Bob Brush > > ___ > gnucash-devel mailing list > gnucash-devel@gnucash.org > https://lists.gnucash.org/mail
Re: Screenshots for the 2.5.0 release
Use Norma http://www.ormfoundation.org/files/folders/normalabs/category1343.aspx On Sat, Apr 6, 2013 at 7:58 AM, John Ralls wrote: > > On Apr 6, 2013, at 6:10 AM, Cristian Marchi wrote: > > > As the 2.5.0 release is approaching, I would like to add some > screenshots in the 2.5.0 wiki page [1] to highlight some new features. As > it is not possible to upload file in the GnuCash wiki, I'm asking help for > this task. > > I attach to this email the screenshots I took from a freshly built > GnuCash from trunk. > > > > This came up a couple of weeks ago WRT the ERD diagram for the SQL page, > and never got a good answer. > > Is there a hosting mechanism set up for putting illustrations on the Wiki? > > Regards, > John Ralls > > > > ___ > gnucash-devel mailing list > gnucash-devel@gnucash.org > https://lists.gnucash.org/mailman/listinfo/gnucash-devel > ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Recommend IDE for coding in "C" -- some historical context
Vi replaced Ed (Editor) tedc On Thu, Mar 21, 2013 at 1:41 PM, Hendrik Boom wrote: > On Thu, Mar 21, 2013 at 02:56:04PM -0400, Buddha Buck wrote: > > On Thu, Mar 21, 2013 at 2:31 PM, Hendrik Boom >wrote: > > > > > On Wed, 20 Mar 2013 13:13:00 -0400, Buddha Buck wrote: > > > > > > > Paul, > > > > > > > > > > > > It should be noted that in Linux/Unix, all the development tools are > > > > command-line based, and so any IDE is going to call make, gcc, git, > gdb, > > > > javac, etc behind the scenes anyway to do the actual work. > > > > > > And C was originally invented jointly with a command-line Unix system. > > > So using it this way fits with tradition. > > > > > > Yup. Worse, from an editing/developing standpoint, the standard terminal > > was a teletype terminal, a combination printer and keyboard that usually > > printed at the rate of about 4 characters/second (45 Baud). > > The slowest I ever encountreed in the 60's was 110 boud, about 10 > characters per second. But for typing, the old KSR teletypes required > so much force that it may well have taken superhuman finger strength to > enter more than about 4 characters per second, whatever the baud rate. > > > This virtually > > demanded a terse command line syntax and the bare minimum of excess > output. > > And it's why the common Unix commands are so cryptically short. > > > > > > > What emacs accomplished in those early days was to be a UI for text > > > terminals. You had multiple 'buffers', which could be put in > differennt > > > places on the screen, or placed in the background to be recalled later. > > > Some buffers would contain files t edit, others aould act as command- > > > language terminals, and so forth. > > > > > > > It still does those things, which is still very, very useful. > > Yes. > > > > > > > > > > > > X was started as a project in 1984 at MIT. Both Emacs (from MIT) and vi > > (from Berkeley) were first written in 1976 or so. Both Emacs and vi came > > out of a desire to make line or tape oriented editors easier to use on > the > > new-fangled CRT displays. Emacs was originally a set of macros for the > > TECO (Tape Editor and COrrector) editor, > > Yes.. But it's not the one we have now. Richard Stallman had a > copyright dispute with MIT, which resulted in MIT taking his emacs > proprietary. He has an early free-software licence in the emacs manual, > declaring emacs to be free, and MIT decided that it was work-for-hire > and took it over. > > THis was one of the events on the way to his GNU public license ans the > dree software foundation. As I understand it, one of the first pieces > of GNU software was a new emacs, this time based on a Lisp dialect. The > result was the emacs we have today. > > -- hendrik > ___ > gnucash-devel mailing list > gnucash-devel@gnucash.org > https://lists.gnucash.org/mailman/listinfo/gnucash-devel > ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Unplanning network maintenance/outage
Do you need a UPS? Sounds like a power related problem tedc On Sun, Mar 17, 2013 at 5:18 AM, Derek Atkins wrote: > Good morning, GnuCashers, > > Some (many?) of you may have noticed the outage of 'code.gnucash.org' > starting with a lot of packet loss on Thursday and escalating into a > complete outage by Friday. This took out our Subversion, Wiki, Email > List, everything server. Well, as of 2:15pm US/EDT on Saturday > (yesterday) everything should be back to normal and operational. If you > don't want to hear the gory details of what happened feel free to stop > reading now. > > The issue was multiple simultaneous failures of multiple pieces of > equipment. What I thought was a power outage turned out be caused by a > failure in my main network switch. It started dropping ports, or > causing ports to fail partially (dropping packets). This was also the > main cause of the packet loss, too. However I didn't discover this > until later. > > My main DHCP server was off the net; I swapped ethernet cables and it > appeared to fix the problem. > > My main database server, however, lost its main network controller so I > had to install a new one (I have a few on hand, so it was a relatively > painless operation -- I just had to remember the magic voodoo to get the > system to call the new card 'eth0', but that was also only a few > minutes). > > It was only after I got this working that I realized that it was the > switch that had failed -- many of the ports connected to actual hosts > had a 'dead link'. I also noticed that my main DHCP server was > bouncing. It would come on the net, stay for a bit, and then go dark. > Luckily I also had a few extra (smaller) switches lying around so I > linked a few of them together and moved all the non-working ports over. > This also fixed the bouncing DHCP server. > > Last, but not least, the VM Server Host's network was wedged, requiring > a complete reboot to reset. This also required resetting all the VMs, > some of which required a bit of hand-holding to come back (and many of > which required a virtual disk fsck as well, taking even more time). The > last of the systems returned to service shortly after 2pm. > > I do plan to acquire a new switch to replace the failing one, but what I > have now is working so I'll watch it closely for now. > > Thanks, > > -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 >warl...@mit.eduPGP key available > ___ > gnucash-devel mailing list > gnucash-devel@gnucash.org > https://lists.gnucash.org/mailman/listinfo/gnucash-devel > ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: font sizing
On startup the register increase, decrease & balance column widths do not automatically widen for 12.5 bold fonts Tedc On Thu, Mar 14, 2013 at 1:49 PM, Ted Creedon wrote: > BTW the larger fonts don't fit into the columns. > > Double right click on the column header and it will resize to fit > > tedc > > > On Thu, Mar 14, 2013 at 10:24 AM, Ted Creedon wrote: > >> Yes, Looks great as your eyes tire >> >> tedc >> >> >> On Thu, Mar 14, 2013 at 10:13 AM, Fernando de Oliveira < >> fam...@yahoo.com.br> wrote: >> >>> --- Em qui, 14/3/13, Geert Janssens escreveu: >>> >>> > De: Geert Janssens >>> > Assunto: Re: font sizing >>> > Para: gnucash-devel >>> > Data: Quinta-feira, 14 de Março de 2013, 13:56 >>> > Op 14-03-13 17:34, Ted Creedon >>> > schreef: >>> > > this works fine in ~/..gtkrc-2.0-kde4 >>> >>> >>> I believe it is with one dot: ~/.gtkrc-2.0-kde4 ? >>> >>> ... >>> >>> > Except for the missing quote in the last line. I presume it >>> > just got >>> > lost while copying to the mail message. Anyway, thanks for >>> > supplying >>> > your gtkrc-2.0-kde4 file. Perhaps it will be of use to >>> > others. >>> > >>> > Geert >>> >>> >>> []s, >>> Fernando >>> >>> ___ >>> gnucash-devel mailing list >>> gnucash-devel@gnucash.org >>> https://lists.gnucash.org/mailman/listinfo/gnucash-devel >>> >> >> > ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: imbalance usd removal
Yes, never thought to select the individual split for deletion works fine thanks On Thu, Mar 14, 2013 at 6:25 PM, Derek Atkins wrote: > Sure, just click on the first non empty cell in the row and keep hitting > del tab until you reach the end of the row. > > -derek > > Sent from my HTC smartphone > > > - Reply message - > From: "Ted Creedon" > To: > Subject: imbalance usd removal > Date: Thu, Mar 14, 2013 8:13 PM > > > Is there any way to remove zero value i"mbalance-USD" from transaction > splits? > > tedc > ___ > gnucash-devel mailing list > gnucash-devel@gnucash.org > https://lists.gnucash.org/mailman/listinfo/gnucash-devel > ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
imbalance usd removal
Is there any way to remove zero value i"mbalance-USD" from transaction splits? tedc ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: font sizing
BTW the larger fonts don't fit into the columns. Double right click on the column header and it will resize to fit tedc On Thu, Mar 14, 2013 at 10:24 AM, Ted Creedon wrote: > Yes, Looks great as your eyes tire > > tedc > > > On Thu, Mar 14, 2013 at 10:13 AM, Fernando de Oliveira < > fam...@yahoo.com.br> wrote: > >> --- Em qui, 14/3/13, Geert Janssens escreveu: >> >> > De: Geert Janssens >> > Assunto: Re: font sizing >> > Para: gnucash-devel >> > Data: Quinta-feira, 14 de Março de 2013, 13:56 >> > Op 14-03-13 17:34, Ted Creedon >> > schreef: >> > > this works fine in ~/..gtkrc-2.0-kde4 >> >> >> I believe it is with one dot: ~/.gtkrc-2.0-kde4 ? >> >> ... >> >> > Except for the missing quote in the last line. I presume it >> > just got >> > lost while copying to the mail message. Anyway, thanks for >> > supplying >> > your gtkrc-2.0-kde4 file. Perhaps it will be of use to >> > others. >> > >> > Geert >> >> >> []s, >> Fernando >> >> ___ >> gnucash-devel mailing list >> gnucash-devel@gnucash.org >> https://lists.gnucash.org/mailman/listinfo/gnucash-devel >> > > ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: font sizing
Yes, Looks great as your eyes tire tedc On Thu, Mar 14, 2013 at 10:13 AM, Fernando de Oliveira wrote: > --- Em qui, 14/3/13, Geert Janssens escreveu: > > > De: Geert Janssens > > Assunto: Re: font sizing > > Para: gnucash-devel > > Data: Quinta-feira, 14 de Março de 2013, 13:56 > > Op 14-03-13 17:34, Ted Creedon > > schreef: > > > this works fine in ~/..gtkrc-2.0-kde4 > > > I believe it is with one dot: ~/.gtkrc-2.0-kde4 ? > > ... > > > Except for the missing quote in the last line. I presume it > > just got > > lost while copying to the mail message. Anyway, thanks for > > supplying > > your gtkrc-2.0-kde4 file. Perhaps it will be of use to > > others. > > > > Geert > > > []s, > Fernando > > ___ > gnucash-devel mailing list > gnucash-devel@gnucash.org > https://lists.gnucash.org/mailman/listinfo/gnucash-devel > ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: font sizing
this works fine in ~/..gtkrc-2.0-kde4 style "user-font" { font_name="Sans Serif Bold" } widget_class "*" style "user-font" gtk-theme-name="oxygen-gtk" gtk-font-name="Sans Serif Bold 12.5 On Thu, Mar 14, 2013 at 6:58 AM, Geert Janssens wrote: > Op 14-03-13 10:48, Ted Creedon schreef: > > OpenSuse 12.3 rc2 >> >> Already changed ..gtkrc-2.0-kde4 works OK but would like to use bold. Is >> there a directory w/ available fonts? >> > You can use System settings->Font manager to get an overview of installed > fonts. Is that what you mean ? > > You can probably use a bold font by simply configuring it in the gtk > module. When you choose a font and size, you can also choose for bold, > italic and other modifiers (font dependent). I'm pretty sure that you will > need the additional step of copying the generated font definition from > gtk-font-name to font_name in your .gtkrc-2.0-kde4 file for it to actually > show up though. > > > thanks >> >> tedc >> >> PS The multi year capability of gnucash is very helpful. Especially w/ IRS >> audits for 2010 & 2011 & capital gains for property bought 8 years ago. >> >> The IRS said I was the most organized taxpayer ever. >> >> >> Nice :) > > Geert > > __**_ > gnucash-devel mailing list > gnucash-devel@gnucash.org > https://lists.gnucash.org/**mailman/listinfo/gnucash-devel<https://lists.gnucash.org/mailman/listinfo/gnucash-devel> > ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: font sizing
OpenSuse 12.3 rc2 Already changed ..gtkrc-2.0-kde4 works OK but would like to use bold. Is there a directory w/ available fonts? thanks tedc PS The multi year capability of gnucash is very helpful. Especially w/ IRS audits for 2010 & 2011 & capital gains for property bought 8 years ago. The IRS said I was the most organized taxpayer ever. On Thu, Mar 14, 2013 at 2:26 AM, Geert Janssens wrote: > When using kde, you should be able to change the font size in > (Kde) System Settings -> Application Appearance -> Gtk+ Appearance > There is an option there to use a custom font (with size). > > On Fedora 18 this doesn't work properly though due to a bug [1]. So to get > this fixed, you need to do two things: > - Configure a font and size using the above setting panel > - Manually edit the generated config file ($HOME/.gtkrc-2.0-kde4): > If you look into this file you will find (among others) two lines: > font_name="" > gtk-font-name=" " > You will have to add your chosen font size to the font_name line similar > to how it was added to gtk-font-name > > I'm not sure what linux flavour you are using, so perhaps you have more > luck and don't need the second step. > > Good luck. > > Geert > > [1] > https://bugzilla.redhat.com/**show_bug.cgi?id=921459<https://bugzilla.redhat.com/show_bug.cgi?id=921459> > > Op 13-03-13 21:20, Ted Creedon schreef: > >> Even if KDE is used? >> >> thanks >> >> ted >> >> >> On Wed, Mar 13, 2013 at 11:19 AM, Geert Janssens >> **wrote: >> >> Op 13-03-13 18:28, Ted Creedon schreef: >>> >>> any way to adjust the font size for the register views?? >>>> >>>> thanks >>>> >>>> tedc >>>> ___ >>>> gnucash-devel mailing list >>>> gnucash-devel@gnucash.org >>>> https://lists.gnucash.org/mailman/listinfo/gnucash-devel<https://lists.gnucash.org/**mailman/listinfo/gnucash-devel> >>>> **<https://lists.gnucash.org/**mailman/listinfo/gnucash-devel<https://lists.gnucash.org/mailman/listinfo/gnucash-devel> >>>> **> >>>> >>>> The font sizes are gtk's defaults. You can alter this. How is system >>> dependent. >>> >>> On linux, use the gnome control panel to change the system's default font >>> sizes. >>> >>> On Windows GnuCash ships with a small tool to change the theme. This tool >>> also lets you change the default font sizes. You can find it in the start >>> menu together with the gnucash applications. >>> >>> On Mac OS X, I have forgotten the details again. I believe you have to >>> hand edit a .gtkrc file if I remember correctly. I think you can find >>> more >>> information either in the wiki or in the list archives. It has been >>> mentioned a couple of times already. >>> >>> Geert >>> ___ >>> gnucash-devel mailing list >>> gnucash-devel@gnucash.org >>> https://lists.gnucash.org/mailman/listinfo/gnucash-devel<https://lists.gnucash.org/**mailman/listinfo/gnucash-devel> >>> **<https://lists.gnucash.org/**mailman/listinfo/gnucash-devel<https://lists.gnucash.org/mailman/listinfo/gnucash-devel> >>> **> >>> >>> __**_ >> gnucash-devel mailing list >> gnucash-devel@gnucash.org >> https://lists.gnucash.org/**mailman/listinfo/gnucash-devel<https://lists.gnucash.org/mailman/listinfo/gnucash-devel> >> > > __**_ > gnucash-devel mailing list > gnucash-devel@gnucash.org > https://lists.gnucash.org/**mailman/listinfo/gnucash-devel<https://lists.gnucash.org/mailman/listinfo/gnucash-devel> > ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: font sizing
Even if KDE is used? thanks ted On Wed, Mar 13, 2013 at 11:19 AM, Geert Janssens wrote: > Op 13-03-13 18:28, Ted Creedon schreef: > >> any way to adjust the font size for the register views?? >> >> thanks >> >> tedc >> __**_ >> gnucash-devel mailing list >> gnucash-devel@gnucash.org >> https://lists.gnucash.org/**mailman/listinfo/gnucash-devel<https://lists.gnucash.org/mailman/listinfo/gnucash-devel> >> > The font sizes are gtk's defaults. You can alter this. How is system > dependent. > > On linux, use the gnome control panel to change the system's default font > sizes. > > On Windows GnuCash ships with a small tool to change the theme. This tool > also lets you change the default font sizes. You can find it in the start > menu together with the gnucash applications. > > On Mac OS X, I have forgotten the details again. I believe you have to > hand edit a .gtkrc file if I remember correctly. I think you can find more > information either in the wiki or in the list archives. It has been > mentioned a couple of times already. > > Geert > __**_ > gnucash-devel mailing list > gnucash-devel@gnucash.org > https://lists.gnucash.org/**mailman/listinfo/gnucash-devel<https://lists.gnucash.org/mailman/listinfo/gnucash-devel> > ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
font sizing
any way to adjust the font size for the register views?? thanks tedc ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Lot transfers
IRS allows FIFO, LIFO, etc you get to select once On Thu, Feb 21, 2013 at 4:21 AM, Peter Dey wrote: > Just thought I'd followup on this -- I didn't receive any replies. > > Any idea about the technical complexity involved in implementing this > functionality/modification? > > Thanks, > Peter > > On Wed, Jan 23, 2013 at 10:52:03PM +1100, Peter Dey wrote: > > Hi all, > > > > I've got a bit over AU$100 credit leftover at a freelance developer site > called > > freelancer.com. > > > > I'd like to create a project on the site to fund the implementation of > the lot > > transfer functionality described here: > > > > http://wiki.gnucash.org/wiki/Concept_of_Lots > > > > Since I know very little about GnuCash's internal architecture, I was > hoping > > someone here would be willing to help me write the specification to > ensure it's > > done in a way suitable to be merged into the mainline, for everyone to > benefit > > from it. > > > > As far as I can tell, it would involve: > > > > 1. Addition of a checkbox to the New/Edit account screens to mark an > account as > >a "lot account" > > 2. A hook somewhere auto-create a new lot when there's a new entry. Code > >could probably be borrowed from the scrubber? > > 3. (personal preference, not on the wiki) add a column to "lot accounts" > to show > >the lot title against every split > > 4. Assume LIFO like the scrubber does -- add a hook to auto-assign (and > close) > >lots on outgoing transactions. Again,. probably could be borrowed > from > >the lot scrubber. > > 5. The most complicated: alter the data structure to remove the tie > between lots > >and accounts (i.e., guid only). This will probably need changes in > other > >places that make an assumption or have a dependency that lot guids > lie in a > >single account. I can only think of the lot scrubber at the moment? > > 6. Assuming it would go into a future release of GnuCash, presumably > some logic > >to upgrade the data file/database schema > > > > Any and all help appreciated... > > > > Cheers, > > Peter > ___ > gnucash-devel mailing list > gnucash-devel@gnucash.org > https://lists.gnucash.org/mailman/listinfo/gnucash-devel > ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Beyond 2.6 (was:Re: Gnucash 2.5/6)
* would recommend writing C++ header files as a starting point tedc * On Mon, Feb 11, 2013 at 1:21 PM, Christian Stimming wrote: > Am Montag, 11. Februar 2013, 10:36:31 schrieb John Ralls: > > > I was just pointing out that if we had to spend a lot of time migrating > > > to Gtk3 we might be better off spending the time migrating to something > > > else. > > > > OK. In fact we've (meaning Geert's) already done 90% of the job. All > that's > > left is fixing the register to draw with Cairo surfaces instead of the > > ancient libgnome stuff. Not an easy job, but much easier than porting > > everything to Qt. > > Very good. > > > > I still wish I had written QOF in C++ instead of C a decade ago. :-( > > > > Me too. But that's not too hard to fix, once I figure out how to get > GObject > > to inherit from a C++ object. The answer is no doubt somewhere in glibmm. > > But it's not quite time for that yet. > > Have a look at the existing cutecash code: In > src/optional/gtkmm/gncmm/Account.hpp there's an gnc::Account, and as you > see > there, the module has a gnc::GncInstance base class that wraps the > QofInstance > "object" that manages the qof parts. This in turn is derived from > Glib::Object > which is the C++ version of a GObject. In my opinion, this wrapping of > GObject and also (while it still exists) QofInstance in the end looks very > well possible and the resulting C++ classes look well enough like a real > C++ > class. > > Disclaimer for all other readers: The C++ part of this discussion is > currently > only an academic one. It has not yet anything to do with the real work > that is > done in the coming months. > > Regards, > > Christian > > ___ > gnucash-devel mailing list > gnucash-devel@gnucash.org > https://lists.gnucash.org/mailman/listinfo/gnucash-devel > ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Trivia: If GnuCash were a commercial program...
If it were for profit, triple the estimate for marketing, distribution, documentation, sales & support. Ted (Tektronix Retired Senior Project Manager) On Thu, Sep 13, 2012 at 1:31 PM, Mike Evans wrote: > On Thu, 13 Sep 2012 20:20:33 +0200 > Geert Janssens wrote: > > > ... it is estimated it would have costed about 90 person years to > develop :) > > > > At least that's what the program sloccount claims. This is obviously not > > scientific calculation, just for fun. The program is primarily meant to > > calculate the effective source lines of code (sloc) in a project. I have > > ran it on GnuCash, here's the full summary for those interested: > > > > Totals grouped by language (dominant language first): > > ansic: 260622 (77.04%) > > lisp: 42674 (12.61%) > > sh: 16955 (5.01%) > > python:6823 (2.02%) > > cpp: 6387 (1.89%) > > perl: 4835 (1.43%) > > > > > > > > > > Total Physical Source Lines of Code (SLOC)= 338,296 > > Development Effort Estimate, Person-Years (Person-Months) = 90.53 > (1,086.36) > > (Basic COCOMO model, Person-Months = 2.4 * (KSLOC**1.05)) > > Schedule Estimate, Years (Months) = 2.97 (35.61) > > (Basic COCOMO model, Months = 2.5 * (person-months**0.38)) > > Estimated Average Number of Developers (Effort/Schedule) = 30.50 > > Total Estimated Cost to Develop = $ 12,229,349 > > (average salary = $56,286/year, overhead = 2.40). > > SLOCCount, Copyright (C) 2001-2004 David A. Wheeler > > SLOCCount is Open Source Software/Free Software, licensed under the GNU > GPL. > > SLOCCount comes with ABSOLUTELY NO WARRANTY, and you are welcome to > > redistribute it under certain conditions as specified by the GNU GPL > > license; > > see the documentation for details. > > Please credit this data as "generated using David A. Wheeler's > 'SLOCCount'." > > > > Have fun ! > > > > Geert > > ___ > > Hi all > > I found this cost estimate the other day which has a similar cost estimate. > > http://www.ohloh.net/p/gnucash/estimated_cost > > Mike E > ___ > gnucash-devel mailing list > gnucash-devel@gnucash.org > https://lists.gnucash.org/mailman/listinfo/gnucash-devel > ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Add IRS audit capabilities
Good idea. Using RO OpenAFS volumes would prevent accidental removal But GIT might be better yet thanks ted On Wed, Feb 15, 2012 at 8:30 AM, Derek Atkins wrote: > Ted, > > On Wed, February 15, 2012 11:15 am, Ted Creedon wrote: > > Being audited for 2 years, Gnucash is very helpful. > > > > Suggestion, it would be helpful if receipts, check stubs and other > > documents could be scanned in and made part of the transaction record. > > > > Binary BLOBS would require a lot of database storage but the generated > > report would be IRS proof. > > > > The IRS wants the data sorted by account & date. > > > > Just a thought. > > Patches always welcome. > > However I would suggest that it would just be easier to have your receipts > scanned into a directory hierarchy that matches your accounts and then > order your receipts by date. I honestly don't think GnuCash should have a > scanner built-in -- xsane is pretty large, and I'm fairly sure does not > have a good way to integrate. > > > > > Tedc > > ___ > > gnucash-devel mailing list > > gnucash-devel@gnucash.org > > https://lists.gnucash.org/mailman/listinfo/gnucash-devel > > -derek > > -- > Derek Atkins 617-623-3745 > de...@ihtfp.com www.ihtfp.com > Computer and Internet Security Consultant > > ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Add IRS audit capabilities
Several links would be OK. On Wed, Feb 15, 2012 at 8:29 AM, Graham Leggett wrote: > On 15 Feb 2012, at 6:15 PM, Ted Creedon wrote: > > > Being audited for 2 years, Gnucash is very helpful. > > > > Suggestion, it would be helpful if receipts, check stubs and other > > documents could be scanned in and made part of the transaction record. > > > > Binary BLOBS would require a lot of database storage but the generated > > report would be IRS proof. > > > > The IRS wants the data sorted by account & date. > > Ideally you want to store this stuff by reference, and not turn gnucash > into a content management system. > > In other words, if gnucash could store a link to a document, and for extra > points display that document if practical or launch an external viewer if > not, it would be ideal. > > This is just an extra metadata field against a transaction. > > The document could be stored in the cloud, in svn, wherever, it's all just > a URL. > > The customer or vendor statements could then include links to data where > present, give that to the IRS, done. > > Regards, > Graham > -- > > ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Trust closeout
The secret is double entry accounting. An accountant's dream. On Wed, Feb 15, 2012 at 8:33 AM, Geert Janssens wrote: > Op woensdag 15 februari 2012 08:08:45 schreef Ted Creedon: > > I'm closing out my Mom's trust and a complete set GnuCash reports for > > 2005-2011 was included in the distribution agreement signed by all the > > beneficiaries. > > > > Worked great, reviewed by 3 tax attorneys. > > > > Tedc > > > > Trustee > > Thanks for sharing this experience with GnuCash. It's nice to know that tax > attorneys find the output GnuCash generates acceptable in such formal > processes. > > Geert > ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Add IRS audit capabilities
Being audited for 2 years, Gnucash is very helpful. Suggestion, it would be helpful if receipts, check stubs and other documents could be scanned in and made part of the transaction record. Binary BLOBS would require a lot of database storage but the generated report would be IRS proof. The IRS wants the data sorted by account & date. Just a thought. Tedc ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Trust closeout
I'm closing out my Mom's trust and a complete set GnuCash reports for 2005-2011 was included in the distribution agreement signed by all the beneficiaries. Worked great, reviewed by 3 tax attorneys. Tedc Trustee ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Transaction report error
Happens in 2.4.8 but not 2.2.9 ted On Mon, Feb 13, 2012 at 1:59 PM, John Ralls wrote: > > On Feb 13, 2012, at 1:30 PM, Ted Creedon wrote: > > > I'm getting the following error: > > > > Report error > > An error occurred while running the report. > > > > Any clues how to troubleshoot? > > > http://wiki.gnucash.org/wiki/FAQ#Q:_Something_bad_happened.3B_how_can_I_help_debug.3F > > Regards, > John Ralls > > ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Transaction report error
I'm getting the following error: Report error An error occurred while running the report. Any clues how to troubleshoot? tedc ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Longer term projects
So how can I help? I'd rather see python, even if it takes a while. Tedc On Thu, Jan 12, 2012 at 8:51 AM, John Ralls wrote: > > On Jan 12, 2012, at 7:54 AM, Ted Creedon wrote: > > > Guile 2.x support needs to be added. > > More likely, ripped out in favor of Python. > > Regards, > John Ralls > > ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Longer term projects
Sorry, tried & failed. I can ssh -X -A into an obsolete box in the meanwhile. tted On Thu, Jan 12, 2012 at 8:05 AM, Derek Atkins wrote: > > On Thu, January 12, 2012 10:54 am, Ted Creedon wrote: > > Guile 2.x support needs to be added. > > I think I just heard a volunteer. Thank you, Ted. > We look forward to your patches! > > (This *is* the -devel list, after all):-) > > > ___ > > gnucash-devel mailing list > > gnucash-devel@gnucash.org > > https://lists.gnucash.org/mailman/listinfo/gnucash-devel > > > > -derek > > -- > Derek Atkins 617-623-3745 > de...@ihtfp.com www.ihtfp.com > Computer and Internet Security Consultant > > ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Longer term projects
Guile 2.x support needs to be added. On Thu, Jan 12, 2012 at 7:33 AM, John Ralls wrote: > > On Jan 12, 2012, at 5:51 AM, Phil Longstaff wrote: > > > There are a number of longer term projects, among them Gtk3 and engine > cleanup. I've been distracted by other matters but can now devote some > time to Gnucash. From what I can tell, John Ralls has been pushing the > engine work (unit testing, converting to real gobjects). Geert (I think) > has been converting to GtkBuilder which I assume is part of the gtk3 work. > Where would I be most useful? I do have a few specific itches to scratch, > mostly around budgetting, but want to help with the infrastructure changes > as well. > > > Super! > > My bias is toward getting as much as possible under good test coverage > (both unit test and "integration" or "acceptance" tests), rewriting into a > good object-oriented design using the GObject framework, and improving the > MVC separation. From that POV: > > You could scratch your budgeting itch by writing unit tests for the > budgeting code, then working it over to make sure that it fully uses Glib > and GObject and has good MVC separation. > > Or unit testing and GObject-ifying the sql/dbi backends, or the xml > backend, or you could pick up where Muslim left off in libqof -- especially > getting rid of the parts like QofObject and QofEvent which duplicate > (badly) GObject facilities. > > > Regards, > John Ralls > > > ___ > gnucash-devel mailing list > gnucash-devel@gnucash.org > https://lists.gnucash.org/mailman/listinfo/gnucash-devel > ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: 2.6 Release -- SCheme
Nothing like progress, installing guile 1.8 doesn't work either Tedc On Sunday, January 1, 2012, John Ralls wrote: > > On Jan 1, 2012, at 7:00 AM, Ted Creedon wrote: > >> this talk is all well & good but meanwhile GC is inoperable on updated >> distros using Guile 2.0. > > And that is the distro maintainers problem. Go bug them or switch distros. > >> >> I think one should bite the bullet and eliminate swig/guile. >> > > That isn't in the cards for 2.6, Guile has its tentacles into a lot more places than the report writer. Until somebody figures out how to get Guile-2.0 to load extensions from somewhere other than /usr/lib, Guile-2.0 support isn't going to happen either. > > Regards, > John Ralls > > > ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: 2.6 Release -- SCheme
this talk is all well & good but meanwhile GC is inoperable on updated distros using Guile 2.0. I think one should bite the bullet and eliminate swig/guile. Tedc On Sun, Jan 1, 2012 at 4:51 AM, Donald Allen wrote: > On Sun, Jan 1, 2012 at 2:39 AM, Gour wrote: > > On Sat, 31 Dec 2011 18:36:28 -0500 > > Mike Alexander wrote: > > > >> Python is popular now, but will it be in 10 years? I've seen > >> lots of languages come and go. > > > > That's true, but I bet it will be more popular than Scheme for sure. > > > > Moreover, we can speculate what will happen with GTK+ in 10 years, but > > let's make GC more approachable *today*. ;) > > Well said. > > We do things all the time (drive cars, fly in airplanes) that have a > small, but non-zero, probability of a bad outcome. We just try to make > smart bets, on a risk/benefit basis. I think choosing Python for this > application is in that category. > > /Don > > > > > Sincerely, > > Gour > > > > > > -- > > A self-realized man has no purpose to fulfill in the discharge > > of his prescribed duties, nor has he any reason not to perform > > such work. Nor has he any need to depend on any other living being. > > > > http://atmarama.net | Hlapicina (Croatia) | GPG: 52B5C810 > > > > ___ > > gnucash-devel mailing list > > gnucash-devel@gnucash.org > > https://lists.gnucash.org/mailman/listinfo/gnucash-devel > > > > ___ > gnucash-devel mailing list > gnucash-devel@gnucash.org > https://lists.gnucash.org/mailman/listinfo/gnucash-devel > ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: 2.6 Release
Need the guile 2.x thing resolved soon Tedc On Friday, December 30, 2011, Christian Stimming wrote: > Am Donnerstag, 29. Dezember 2011, 14:18:38 schrieb John Ralls: >> > I propose to start a new 2.5.0 / 2.6.0 release series in order to make >> > those "small business user" improvements available in a stable release. >> > As already discussed in length, there haven't been that much >> > significant changes in gnucash apart from these features which might >> > seem minor to all users who don't happen to use gnucash for running a >> > business. >> >> Thank you. That's much better; perhaps we can turn it into a wiki page to >> point testers at. > > Yes. I've collected my list at > http://wiki.gnucash.org/wiki/Release_Schedule#Feature_Checklist_for_2.6.0 > Feel free to edit this list and/or add any comments, as usual in the wiki. > >> Are there unit tests for all of those features? > > No. The points I mentioned are all UI features, for which we don't have any > unittests so far. But all of those features have been implemented by direct > user requests who also acknowledged the successful implementation of the > feature, so they are indeed in daily use by some people. > > On the other hand some of them imply some additional engine layer features (or > "business logic features"), and of course those might get tested by unittests. > To my knowledge, none of those features have had "business logic" unittests > added. I will look into adding this, but I doubt it will cover any significant > parts of those features. > > Best Regards, > > Christian > >> I'll spend some more time chasing down edits that aren't immediately >> committed, so that the SQL backend is sure to work properly (and also add >> automated tests for that to setters). >> >> Is it feasible to remove Guile 1.6 support (by fixing the deprecation >> warnings with Guile 1.8)? Will that be sufficient to make Guile 2.0 work? >> (I'm willing to do the work.) >> >> >> Regards, >> John Ralls > ___ > gnucash-devel mailing list > gnucash-devel@gnucash.org > https://lists.gnucash.org/mailman/listinfo/gnucash-devel > ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: 2.6 Release
Need to update to guile 2.x Tedc On Tuesday, December 27, 2011, John Ralls wrote: > > On Dec 27, 2011, at 1:57 PM, Christian Stimming wrote: > >> Am Dienstag, 27. Dezember 2011, 22:51:46 schrieb Geert Janssens: >>> At this point I'm actually more inclined to go for plan B, forget the >>> dependency updates on 2.4 and instead focus on getting 2.6 ready and with >>> aqbanking 5. >> >> I can't add any wisdom as well. Concerning the errors the two of you are >> reporting, I also don't have any further idea. >> >> Hence, in order to get a new release up and running, I would indeed also vote >> for getting a 2.5/2.6 version ready in the rather near future, instead of >> trying other random bits with the 2.4 branch. Of course, if anyone still finds >> out what's wrong with the current 2.4 build, this would be fine as well, but >> on the other hand investing one's time in the new branch is probably the more >> future-proof investment of time... > > I said before I don't have any strong feelings about a 2.6 release. Well, they're growing on me, and they're pretty much opposed. > > * Bumping the minor number just because it's been a year is dumb and unprofessional. > > * There are no new features in Gnucash. The Win32 distribution had fallen behind because the shell scripts are so ugly that no one wants to maintain them. It's more up to date now, but the scripts don't suck any less. (Someone has hacked jhbuild to work with MinGW: http://afuera.me.uk/jhbuild-windows/ If that works it would be *way* better than the shell scripts.) > > * Any really important bug fixes should be backported, so that shouldn't be a reason to change the minor version. > > * Development efforts have really been focussed on 3.0: Geert is working through converting Druids to Assistants and libglade to GtkBuilder. I'm working over the core to make it suitable for a transactional backend. > > * There's no plan. > > * There are 4 bugs with a 2.5/2.6 milestone. (There were 6, but I just changed 644244 and 661093 to "future" because the first requires a rewrite of the register code and the second requires full GObjectification (it's caused by our messed-up memory management). Three of them are "reminders" that I wrote to myself; the 4th is 449395 that should have been fixed for 2.4 but just got "kicked down the road". > > If we're going to do a 2.6 release we need to set some goals for it and Geert and I should set aside the long-term work and go for those goals. > * One of the goals can certainly be Geert's credit memos and the accompanying backend changes, but I think we need a bit more than that. > * Another can be making sure that the SQL backend actually saves everything as soon as an edit is completed. I just fixed the bit for KVP, but the whole program needs to be audited (automated tests would be good!) to make sure that any persistent datum that gets edited is wrapped in the appropriate begin_edit/mark_dirty/commit_edit calls. (There's a better way to do this, of course, but it's part of GObjectification, so if it's going to get fixed before that, it needs to be done the hard way.) > > So that's two. ISTM we need 5 or 6 for a 2.6 release series to make sense. It shouldn't be hard to find them in the 868 open bugs. > > Frankly, I think it makes way more sense to work on the architectural problems and go 4 years before the next minor release, just like we did last time. If we get the big problems fixed a lot of the smaller ones will get fixed too. That's the "future-proof" way forward. > > Regards, > John Ralls > > > > ___ > gnucash-devel mailing list > gnucash-devel@gnucash.org > https://lists.gnucash.org/mailman/listinfo/gnucash-devel > ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: 2.4.9 release, 2.5.0 plans
what version of Guile will be supported? tedc On Sun, Dec 18, 2011 at 1:23 PM, Christian Stimming wrote: > Am Samstag, 17. Dezember 2011, 17:11:10 schrieb John Ralls: > > > Indeed I am rather sure it will not be possible to build the 2.4 branch > > > on windows with gtk >= 2.20, as it needs to be built with a newer > > > webkit as well, and I think this had other implications on some gnucash > > > webkit code. > > > > Having just done it, I'm quite sure that Gnucash-2.4 builds fine with the > > latest Gnome windows binaries. Webkit 1.1.90 presented no issues and > > appears to work just fine. (The multicolumn report whines about > > hicolor-theme not being installed, so perhaps that should get added.) > > This is great news! Thank you very much for looking into this. Even better > to > hear that it really works. In that case we can very well upgrade the > 2.4-build > to the newer binaries, and have a newer gwenhywfar/aqbanking included as > well. > > > The latest Gwen and AQB build fine as well, but I can't convince Gwen to > > find her plugins. Do I need to install the registry keys in > gwenhywfar.iss, > > or is there a more temporary and unix-y way? > > The plugin directories for gwenyhwfar are looked up in two ways: Firstly by > using the executable's installation location as a starting point (using > binreloc on Unix and GetModuleFileName() on Windows), assuming it's > installed > in some $prefix/bin, and going to $prefix/lib relative from there. > Secondly, > on windows the paths from the registry are used, and on Unix the > compile-time > paths are used. > > According to the reports from gnucash users, with the gnucash installer the > plugins are all found just fine. On the other hand, our gnucash.iss already > installs all those registry keys as well. Hence, I don't know how the paths > are actually looked up from the aqbanking in gnucash binary: Either the > relative lookup already succeeded, or the registry paths from our > gnucash.iss > works fine. > > > Oh, and when Gwen can't find her "dir" plugin, AQB asserts (in > config-mgr.c, > > line 250) and crashes everything, which is a bit rude. > > The crash in configmgr.c:250 is gwenhywfar code GWEN_ConfigMgr_GetGroup(), > which is called from aqbanking from somewhere. Most of the aqbanking calls > of > that function are already guarded against a NULL here. Any chance you can > find > out which aqbanking location called that function at crash time? > > Thanks again for the windows update! I hope this means we can go for a > 2.4.9 > with updated gtk on windows (and also updated gwen/aqbanking) before > Christmas... > > Regards, > > Christian > ___ > gnucash-devel mailing list > gnucash-devel@gnucash.org > https://lists.gnucash.org/mailman/listinfo/gnucash-devel > ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Guile 2
Is anyone working on the Guile 2 issues? tedc ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Komando advertizes GnuCash
She left out Linux. Expect a corresponding increase in support workload tedc On Wed, Dec 7, 2011 at 9:42 AM, Derek Atkins wrote: > Linas saw a huge uptick in GnuCash website access today and we tracked > it down to Kim Komando: > > > http://www.komando.com/downloads/category.aspx?id=6107&utm_medium=nl&utm_source=dotd&utm_content=2011-12-07-article&utm_campaign=end > > Anyone know about this? > > -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 > warl...@mit.eduPGP key available > ___ > gnucash-devel mailing list > gnucash-devel@gnucash.org > https://lists.gnucash.org/mailman/listinfo/gnucash-devel > ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Strategy
Better to either imbed Guile in the executable or start replacing it piece by piece. Too many dependencies on other peoples work. Mentor Graphics faced the same problem with 16,000,000 lines of source code for one product written in several languages. They laid off the US help and sent the code to India... An object oriented data design should be done first.. Tedc On Sat, Dec 3, 2011 at 7:38 PM, Ross Boylan wrote: > On Sat, 2011-12-03 at 16:40 -0500, Donald Allen wrote: > > The big question is, when is it worth it to cut your losses and > > start over? > I don't have strong opinions, but others do, in the opposite direction: > > Joel Spolsky says (in the context of Netsape) > > single worst strategic mistake that any software company can make: > > They decided to rewrite the code from scratch. > > and also > > > As a corollary of this axiom, you can ask almost any programmer today > > about the code they are working on. "It's a big hairy mess," they will > > tell you. "I'd like nothing better than to throw it out and start > > over." > > There's more in his essay "Things You Should Never Do" > http://www.joelonsoftware.com/articles/fog69.html > > Ross Boylan > > ___ > gnucash-devel mailing list > gnucash-devel@gnucash.org > https://lists.gnucash.org/mailman/listinfo/gnucash-devel > ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: FW: OpenSuse 12.1 Guile 2.0
Guile 2.0 has sabotaged guncash I'm told to build 2.4.99/2.4.8 against guile 1.8.x which I have with limited success Also discovered dbus problem with running via ssh -X -A tedc On Sat, Dec 3, 2011 at 2:44 AM, rbibr...@t-online.de wrote: > Hello, > > in the moment I am using this version (J.Engel) > http://download.opensuse.org/repositories/home:/j-engel/openSUSE_12.1/i586/ > It is working including the onelinebanking (hbci), but the the reports > have severe problems (hanging, crashing) > > In Guile 2.0 several procedures are completly deleted: > the GH Interface (isthis of any relevance??) > maxdepth, scm_string_chars (already corrected in trunk), > scm_stringp, scm_symbol_chars > > scm_symbol_chars appears in the following files: > > guile-util.c, option-util.c, engine-helpers.c, dialog-tax-info.c, > druid-qif-import.c > At least here a correction is needed > (may be with scm_symbol_to_string, scm_to_utf8_stringn) > > My capabilities are are limited, sorry > > Rudolf > > > > > ___ > gnucash-devel mailing list > gnucash-devel@gnucash.org > https://lists.gnucash.org/mailman/listinfo/gnucash-devel > ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: 2.4.99 on opensuse 12.1
2.4.99 from github On Fri, Dec 2, 2011 at 7:46 PM, John Ralls wrote: > > On Dec 2, 2011, at 5:06 PM, Ted Creedon wrote: > > > put guile 1.8.7 in its own directory > > > > # CPPFLAGS="-I/root/guile-1.8.7/include" > > LDFLAGS="-L/root/guile-1.8.7/lib64" ./configure > --disable-error-on-warning > > --disable-dbi --enable-debug > > > > # GUILE_AUTO_COMPILE=0 gnucash --debug --extra > > > > This is a development version. It may or may not work. > > Report bugs and other problems to gnucash-devel@gnucash.org. > > You can also lookup and file bug reports at http://bugzilla.gnome.org > > The last stable version was GnuCash 2.4.7 > > The next stable version will be GnuCash 2.6 > > > > WARNING: (gnucash import-export qif-import): `GNC-DENOM-AUTO' imported > from > > both (sw_engine) and (gnucash engine) > > WARNING: (gnucash import-export qif-import): `gnc-build-dotgnucash-path' > > imported from both (sw_engine) and (gnucash core-utils) > > WARNING: (gnucash report report-system): `GNC-DENOM-AUTO' imported from > > both (sw_engine) and (gnucash engine) > > overrides core binding `N_' > [Snip] > > WARNING: (gnucash report easy-invoice): imported module (gnucash > app-utils) > > overrides core binding `N_' > > ice-9/psyntax.scm:1326:30: In procedure chi-macro: > > ice-9/psyntax.scm:1326:30: Syntax error: > > unknown location: source expression failed to match any pattern in form > do > > What revision is this? Did you check it out from code.gnucash.org or > github.com/Gnucash/gnucash, or did it come from some other source? > > Regards, > John Ralls > > ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
2.4.99 on opensuse 12.1
put guile 1.8.7 in its own directory # CPPFLAGS="-I/root/guile-1.8.7/include" LDFLAGS="-L/root/guile-1.8.7/lib64" ./configure --disable-error-on-warning --disable-dbi --enable-debug # GUILE_AUTO_COMPILE=0 gnucash --debug --extra This is a development version. It may or may not work. Report bugs and other problems to gnucash-devel@gnucash.org. You can also lookup and file bug reports at http://bugzilla.gnome.org The last stable version was GnuCash 2.4.7 The next stable version will be GnuCash 2.6 WARNING: (gnucash import-export qif-import): `GNC-DENOM-AUTO' imported from both (sw_engine) and (gnucash engine) WARNING: (gnucash import-export qif-import): `gnc-build-dotgnucash-path' imported from both (sw_engine) and (gnucash core-utils) WARNING: (gnucash report report-system): `GNC-DENOM-AUTO' imported from both (sw_engine) and (gnucash engine) WARNING: (gnucash report report-system): imported module (gnucash app-utils) overrides core binding `N_' WARNING: (gnucash report report-system): imported module (gnucash app-utils) overrides core binding `N_' WARNING: (gnucash report report-system): `GNC-DENOM-AUTO' imported from both (sw_engine) and (gnucash engine) WARNING: (gnucash report report-system): imported module (gnucash app-utils) overrides core binding `N_' WARNING: (gnucash report report-system): `GNC-DENOM-AUTO' imported from both (sw_engine) and (gnucash engine) WARNING: (gnucash report report-system): imported module (gnucash app-utils) overrides core binding `N_' WARNING: (gnucash report stylesheet-plain): imported module (gnucash app-utils) overrides core binding `N_' WARNING: (gnucash report stylesheet-fancy): imported module (gnucash app-utils) overrides core binding `N_' WARNING: (gnucash report stylesheet-footer): imported module (gnucash app-utils) overrides core binding `N_' WARNING: (gnucash report stylesheet-easy): imported module (gnucash app-utils) overrides core binding `N_' WARNING: (gnucash report standard-reports daily-reports): imported module (gnucash app-utils) overrides core binding `N_' WARNING: (gnucash report standard-reports account-summary): imported module (gnucash app-utils) overrides core binding `N_' WARNING: (gnucash report standard-reports general-journal): imported module (gnucash app-utils) overrides core binding `N_' WARNING: (gnucash report standard-reports advanced-portfolio): imported module (gnucash app-utils) overrides core binding `N_' WARNING: (gnucash report standard-reports advanced-portfolio): `GNC-DENOM-AUTO' imported from both (sw_engine) and (gnucash engine) WARNING: (gnucash report standard-reports balance-sheet): imported module (gnucash app-utils) overrides core binding `N_' WARNING: (gnucash report standard-reports category-barchart): imported module (gnucash app-utils) overrides core binding `N_' WARNING: (gnucash report standard-reports budget-barchart): imported module (gnucash app-utils) overrides core binding `N_' WARNING: (gnucash report standard-reports price-scatter): imported module (gnucash app-utils) overrides core binding `N_' WARNING: (gnucash report standard-reports sx-summary): imported module (gnucash app-utils) overrides core binding `N_' WARNING: (gnucash report standard-reports average-balance): imported module (gnucash app-utils) overrides core binding `N_' WARNING: (gnucash report standard-reports equity-statement): imported module (gnucash app-utils) overrides core binding `N_' WARNING: (gnucash report standard-reports transaction): imported module (gnucash app-utils) overrides core binding `N_' WARNING: (gnucash report standard-reports budget-flow): imported module (gnucash app-utils) overrides core binding `N_' WARNING: (gnucash report standard-reports account-piecharts): imported module (gnucash app-utils) overrides core binding `N_' WARNING: (gnucash business-utils): imported module (gnucash app-utils) overrides core binding `N_' WARNING: (gnucash business-utils): imported module (gnucash app-utils) overrides core binding `N_' WARNING: (gnucash report hello-world): imported module (gnucash app-utils) overrides core binding `N_' WARNING: (gnucash report view-column): imported module (gnucash app-utils) overrides core binding `N_' WARNING: (gnucash report welcome-to-gnucash): imported module (gnucash app-utils) overrides core binding `N_' WARNING: (gnucash report report-gnome): imported module (gnucash app-utils) overrides core binding `N_' WARNING: (gnucash report business-reports): imported module (gnucash app-utils) overrides core binding `N_' WARNING: (gnucash report fancy-invoice): imported module (gnucash app-utils) overrides core binding `N_' WARNING: (gnucash report invoice): imported module (gnucash app-utils) overrides core binding `N_' WARNING: (gnucash report easy-invoice): imported module (gnucash app-utils) overrides core binding `N_' ice-9/psyntax.scm:1326:30: In procedure chi-macro: ice-9/psyntax.scm:1326:30: Syntax error: unknown location: source expression failed to match any pattern in form do __
Re: 2.4.8 git /w guile 2.0
GUILE_WARN_DEPRECATED=detailed make check cut = PASS: test-load-c FAIL: test-load-scm PASS: test-gwrapped-c PASS: test-scm-module FAIL: test-scm-multi FAIL: test-load-deps On Fri, Nov 11, 2011 at 10:33 AM, Geert Janssens wrote: > On vrijdag 11 november 2011, Ted Creedon wrote: > > here's what I did, it it correct? > > > > git clone git://github.com/Gnucash/gnucash.git > > cd gnucash/ > > ./autogen.sh > > ./configure --enable-debug --disable-error-on-warning #won't > > compile without this disable switch > > make > > > > gnucash --version > > gnc.bin-Message: main: binreloc relocation support was disabled at > > configure time. > > > > GnuCash 2.4.99 development version > > Built 2011-11-08 from r872d437+ > > > This is not the most recent git commit, but recent enough. It does have the > maxdepth bug fix. > > git checkout trunk > git-update (the perl script you displayed before) > should get you to the latest commit. > > I'll have to investigate the new errors you report below. > > Geert > > > > > rm -rf /root/.cache/guile/;GUILE_AUTO_COMPILE=0 gnucash --debug --extra > > --log="gnc.scm=debug" > > gnc.bin-Message: main: binreloc relocation support was disabled at > > configure time. > > > > This is a development version. It may or may not work. > > Report bugs and other problems to gnucash-devel@gnucash.org. > > You can also lookup and file bug reports at http://bugzilla.gnome.org > > The last stable version was GnuCash 2.4.7 > > The next stable version will be GnuCash 2.6 > > > > WARNING: (gnucash import-export qif-import): `GNC-DENOM-AUTO' imported > from > > both (sw_engine) and (gnucash engine) > > WARNING: (gnucash import-export qif-import): `gnc-build-dotgnucash-path' > > imported from both (sw_engine) and (gnucash core-utils) > > WARNING: (gnucash report report-system): `GNC-DENOM-AUTO' imported from > > both (sw_engine) and (gnucash engine) > > WARNING: (gnucash report report-system): imported module (gnucash > > app-utils) overrides core binding `N_' > > WARNING: (gnucash report report-system): imported module (gnucash > > app-utils) overrides core binding `N_' > > WARNING: (gnucash report report-system): `GNC-DENOM-AUTO' imported from > > both (sw_engine) and (gnucash engine) > > WARNING: (gnucash report report-system): imported module (gnucash > > app-utils) overrides core binding `N_' > > WARNING: (gnucash report report-system): `GNC-DENOM-AUTO' imported from > > both (sw_engine) and (gnucash engine) > > WARNING: (gnucash report report-system): imported module (gnucash > > app-utils) overrides core binding `N_' > > WARNING: (gnucash report stylesheet-plain): imported module (gnucash > > app-utils) overrides core binding `N_' > > WARNING: (gnucash report stylesheet-fancy): imported module (gnucash > > app-utils) overrides core binding `N_' > > WARNING: (gnucash report stylesheet-footer): imported module (gnucash > > app-utils) overrides core binding `N_' > > WARNING: (gnucash report stylesheet-easy): imported module (gnucash > > app-utils) overrides core binding `N_' > > WARNING: (gnucash report standard-reports daily-reports): imported module > > (gnucash app-utils) overrides core binding `N_' > > WARNING: (gnucash report standard-reports account-summary): imported > module > > (gnucash app-utils) overrides core binding `N_' > > WARNING: (gnucash report standard-reports general-journal): imported > module > > (gnucash app-utils) overrides core binding `N_' > > WARNING: (gnucash report standard-reports advanced-portfolio): imported > > module (gnucash app-utils) overrides core binding `N_' > > WARNING: (gnucash report standard-reports advanced-portfolio): > > `GNC-DENOM-AUTO' imported from both (sw_engine) and (gnucash engine) > > WARNING: (gnucash report standard-reports balance-sheet): imported module > > (gnucash app-utils) overrides core binding `N_' > > WARNING: (gnucash report standard-reports category-barchart): imported > > module (gnucash app-utils) overrides core binding `N_' > > WARNING: (gnucash report standard-reports budget-barchart): imported > module > > (gnucash app-utils) overrides core binding `N_' > > WARNING: (gnucash report standard-reports price-scatter): imported module > > (gnucash app-utils) overrides core binding `N_' > > WARNING: (gnucash report standard-reports sx-summary): imported module > > (gnucash app-utils) overrides
Re: 2.4.8 git /w guile 2.0
here's the trace file 10:04:12 INFO [gnc_hook_lookup] no hook lists * 10:04:12 INFO [init_from_file] guid_init got 512 bytes from /dev/urandom * 10:04:12 INFO [init_from_file] guid_init got 1375 bytes from /etc/passwd * 10:04:12 INFO [init_from_file] guid_init got 27 bytes from /proc/loadavg * 10:04:12 INFO [init_from_file] guid_init got 1170 bytes from /proc/meminfo * 10:04:12 INFO [init_from_file] guid_init got 571 bytes from /proc/net/dev * 10:04:12 INFO [init_from_file] guid_init got 4096 bytes from /proc/self/environ * 10:04:12 INFO [init_from_file] guid_init got 236 bytes from /proc/self/stat * 10:04:12 INFO [init_from_file] guid_init got 3041 bytes from /proc/stat * 10:04:12 INFO [init_from_file] guid_init got 19 bytes from /proc/uptime * 10:04:12 INFO [guid_init] got 38589 bytes * 10:04:12 INFO [gnc_module_init_backend_dbi] GNC_DBD_DIR not set: using libdbi built-in default * 10:04:12 INFO [gnc_module_init_backend_dbi] 3 DBD drivers found * 10:04:12 INFO [gnc_module_init_backend_dbi] Driver: mysql * 10:04:12 INFO [gnc_module_init_backend_dbi] Driver: sqlite3 * 10:04:12 INFO [gnc_module_init_backend_dbi] Driver: pgsql * 10:04:14 MESSG Could not locate optional module gnucash/import-export/aqbanking interface v.0 * 10:04:15 DEBUG dir-files=(daily-reports.scm account-summary.scm general-journal.scm advanced-portfolio.scm balance-sheet.scm category-barchart.scm budget-barchart.scm price-scatter.scm sx-summary.scm average-balance.scm equity-statement.scm transaction.scm budget-flow.scm account-piecharts.scm balsheet-eg.scm register.scm budget-income-statement.scm general-ledger.scm cash-flow.scm portfolio.scm trial-balance.scm budget.scm budget-balance-sheet.scm net-barchart.scm income-statement.scm) * 10:04:15 DEBUG processed=(daily-reports account-summary general-journal advanced-portfolio balance-sheet category-barchart budget-barchart price-scatter sx-summary average-balance equity-statement transaction budget-flow account-piecharts balsheet-eg register budget-income-statement general-ledger cash-flow portfolio trial-balance budget budget-balance-sheet net-barchart income-statement) * 10:04:15 DEBUG report-list=(daily-reports account-summary general-journal advanced-portfolio balance-sheet category-barchart budget-barchart price-scatter sx-summary average-balance equity-statement transaction budget-flow account-piecharts balsheet-eg register budget-income-statement general-ledger cash-flow portfolio trial-balance budget budget-balance-sheet net-barchart income-statement) On Fri, Nov 11, 2011 at 10:11 AM, Ted Creedon wrote: > here's what I did, it it correct? > > git clone git://github.com/Gnucash/gnucash.git > cd gnucash/ > ./autogen.sh > ./configure --enable-debug --disable-error-on-warning #won't > compile without this disable switch > make > > gnucash --version > > gnc.bin-Message: main: binreloc relocation support was disabled at > configure time. > > GnuCash 2.4.99 development version > Built 2011-11-08 from r872d437+ > > > rm -rf /root/.cache/guile/;GUILE_AUTO_COMPILE=0 gnucash --debug --extra > --log="gnc.scm=debug" > gnc.bin-Message: main: binreloc relocation support was disabled at > configure time. > > This is a development version. It may or may not work. > Report bugs and other problems to gnucash-devel@gnucash.org. > You can also lookup and file bug reports at http://bugzilla.gnome.org > The last stable version was GnuCash 2.4.7 > The next stable version will be GnuCash 2.6 > > WARNING: (gnucash import-export qif-import): `GNC-DENOM-AUTO' imported > from both (sw_engine) and (gnucash engine) > WARNING: (gnucash import-export qif-import): `gnc-build-dotgnucash-path' > imported from both (sw_engine) and (gnucash core-utils) > WARNING: (gnucash report report-system): `GNC-DENOM-AUTO' imported from > both (sw_engine) and (gnucash engine) > WARNING: (gnucash report report-system): imported module (gnucash > app-utils) overrides core binding `N_' > WARNING: (gnucash report report-system): imported module (gnucash > app-utils) overrides core binding `N_' > WARNING: (gnucash report report-system): `GNC-DENOM-AUTO' imported from > both (sw_engine) and (gnucash engine) > WARNING: (gnucash report report-system): imported module (gnucash > app-utils) overrides core binding `N_' > WARNING: (gnucash report report-system): `GNC-DENOM-AUTO' imported from > both (sw_engine) and (gnucash engine) > WARNING: (gnucash report report-system): imported module (gnucash > app-utils) overrides core binding `N_' > WARNING: (gnucash report stylesheet-plain): imported module (gnucash > app-utils) overrides core binding `N_' > WARNING: (gnucash report stylesheet-fancy): imported module (gnucash > app-utils) overrides core binding `N_'
Re: 2.4.8 git /w guile 2.0
sh app-utils) overrides core binding `N_' WARNING: (gnucash report fancy-invoice): imported module (gnucash app-utils) overrides core binding `N_' WARNING: (gnucash report invoice): imported module (gnucash app-utils) overrides core binding `N_' WARNING: (gnucash report easy-invoice): imported module (gnucash app-utils) overrides core binding `N_' ice-9/psyntax.scm:1326:30: In procedure chi-macro: ice-9/psyntax.scm:1326:30: Syntax error: unknown location: source expression failed to match any pattern in form do On Fri, Nov 11, 2011 at 9:39 AM, John Ralls wrote: > > On Nov 11, 2011, at 8:39 AM, Ted Creedon wrote: > > > Whats the correct incantation? > > To do what? > > Regards, > John Ralls > > > ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: 2.4.8 git /w guile 2.0
Whats the correct incantation? ted On Fri, Nov 11, 2011 at 8:30 AM, John Ralls wrote: > > On Nov 11, 2011, at 8:01 AM, Derek Atkins wrote: > > > Ted, > > > > Ted Creedon writes: > > > >> Brand new clean system "Lizzy" - first build did a git pull and ran the > >> perl script > >> > >> #!/usr/bin/perl > >> #-;-perl-;- > >> use strict; > >> > >> use lib (split(/:/, $ENV{GITPERLLIB} || > >> "/usr/local/git/lib/perl5/site_perl")); > >> use Git; > >> > >> Git::command_noisy("pull", ("--rebase", "origin", @ARGV)); > >> my @branches = Git::command("branch", "-r"); > >> map s/[*\s]//g, @branches; > >> @branches = map { /^origin\/([^\s>]+)$/ ? $1 : () } @branches; > >> map { Git::command("update-ref", ("refs/remotes/$_", > >> "refs/remotes/origin/$_")); } @branches; > > > > This script means absolutely nothing to me, and you didn't answer my > > question: > > > > Are you sure you're using the most recent trunk (of GnuCash)? > > > > The script just gets the latest from git (one hopes that that's git:// > github.com/Gnucash/gnucash.git) and renames the branch pointers -- > basically a no-op. > > What he's not telling us is what branch he has checked out to do his build. > > Regards, > John Ralls > > > ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Fwd: 2.4.8 git /w guile 2.0
Brand new clean system "Lizzy" - first build did a git pull and ran the perl script #!/usr/bin/perl #-;-perl-;- use strict; use lib (split(/:/, $ENV{GITPERLLIB} || "/usr/local/git/lib/perl5/site_perl")); use Git; Git::command_noisy("pull", ("--rebase", "origin", @ARGV)); my @branches = Git::command("branch", "-r"); map s/[*\s]//g, @branches; @branches = map { /^origin\/([^\s>]+)$/ ? $1 : () } @branches; map { Git::command("update-ref", ("refs/remotes/$_", "refs/remotes/origin/$_")); } @branches; On Thu, Nov 10, 2011 at 10:49 AM, Derek Atkins wrote: > Ted, > > Are you sure you're using the most recent trunk? > > Also, I wonder where it's finding ice-9/boot-9.scm? Are there any traces > of guile-1.8 on this system? Any traces of an old GnuCash build? > > -derek > > On Thu, November 10, 2011 1:37 pm, Ted Creedon wrote: > > Built a new system w. guile 2.0 > > > > export GUILE_AUTO_COMPILE=0 > > make clean;./configure --disable-error-on-warning;time nice make -s > > gnucash > > > > On Wed, Nov 9, 2izzy:/data/gnucash # rm -rf /root/.cache/guile/*;gnucash > > > > gnc.bin-Message: main: binreloc relocation support was disabled at > > configure time. > > > > WARNING: no socket to connect to > > Backtrace: > > In ice-9/boot-9.scm: > > 170: 12 [catch #t # ...] > > In unknown file: > >?: 11 [catch-closure] > > In ice-9/boot-9.scm: > > 2497: 10 [# > autoload version #:key ensure)> # ...] > > 2763: 9 [try-module-autoload (gnucash main) #f] > > 2103: 8 [save-module-excursion # > ice-9/boot-9.scm:2764:17 ()>] > > 2774: 7 [#] > > In unknown file: > >?: 6 [primitive-load-path "gnucash/main" #f] > > In ice-9/eval.scm: > > 458: 5 [# #] > > In ice-9/psyntax.scm: > > 1024: 4 [chi-top-sequence ((debug-set! maxdepth 10)) () ...] > > 922: 3 [scan ((debug-set! maxdepth 10)) () ...] > > 1015: 2 [scan ((#(syntax-object debug-options # ...) (# # #))) () ...] > > In ice-9/boot-9.scm: > > 2854: 1 [debug-options (show-file-name #t stack ...)] > > In unknown file: > > ?: 0 [debug-options-interface (show-file-name #t stack ...)] > > > > ERROR: In procedure debug-options-interface: > > ERROR: In procedure debug-options-interface: Unknown option name: > maxdepth > > 011 at 9:06 AM, Ted Creedon wrote: > > > >> can anyone suggest a suitable log.conf? > >> > >> thanks > >> ted > >> > >> > >> On Wed, Nov 9, 2011 at 8:59 AM, Ted Creedon > >> wrote: > >> > >>> announce window & tip of the day pop up before exiting > >>> > >>> rm -rf /root/.cache/guile/;GUILE_AUTO_COMPILE=0 gnucash --debug --extra > >>> > >>> gnc.bin-Message: main: binreloc relocation support was disabled at > >>> configure time. > >>> > >>> This is a development version. It may or may not work. > >>> Report bugs and other problems to gnucash-devel@gnucash.org. > >>> You can also lookup and file bug reports at http://bugzilla.gnome.org > >>> The last stable version was GnuCash 2.4.7 > >>> The next stable version will be GnuCash 2.6 > >>> > >>> WARNING: (gnucash import-export qif-import): `GNC-DENOM-AUTO' imported > >>> from both (sw_engine) and (gnucash engine) > >>> WARNING: (gnucash import-export qif-import): > >>> `gnc-build-dotgnucash-path' > >>> imported from both (sw_engine) and (gnucash core-utils) > >>> WARNING: (gnucash report report-system): `GNC-DENOM-AUTO' imported from > >>> both (sw_engine) and (gnucash engine) > >>> WARNING: (gnucash report report-system): imported module (gnucash > >>> app-utils) overrides core binding `N_' > >>> WARNING: (gnucash report report-system): imported module (gnucash > >>> app-utils) overrides core binding `N_' > >>> WARNING: (gnucash report report-system): `GNC-DENOM-AUTO' imported from > >>> both (sw_engine) and (gnucash engine) > >>> WARNING: (gnucash report report-system): imported module (gnucash > >>> app-utils) overrides core binding `N_' > >>> WARNING: (gnucash report report-system): `GNC-DENOM-AUTO' imported from > >>> both (sw_engine) and (gnucash engine) > >>> WARNING: (gnucash report report-system): imported module (gnucash > >>> app-utils) overrides core binding `N_' > >>> WARNI
Re: Fwd: 2.4.8 git /w guile 2.0
Built a new system w. guile 2.0 export GUILE_AUTO_COMPILE=0 make clean;./configure --disable-error-on-warning;time nice make -s gnucash On Wed, Nov 9, 2izzy:/data/gnucash # rm -rf /root/.cache/guile/*;gnucash gnc.bin-Message: main: binreloc relocation support was disabled at configure time. WARNING: no socket to connect to Backtrace: In ice-9/boot-9.scm: 170: 12 [catch #t # ...] In unknown file: ?: 11 [catch-closure] In ice-9/boot-9.scm: 2497: 10 [# # ...] 2763: 9 [try-module-autoload (gnucash main) #f] 2103: 8 [save-module-excursion #] 2774: 7 [#] In unknown file: ?: 6 [primitive-load-path "gnucash/main" #f] In ice-9/eval.scm: 458: 5 [# #] In ice-9/psyntax.scm: 1024: 4 [chi-top-sequence ((debug-set! maxdepth 10)) () ...] 922: 3 [scan ((debug-set! maxdepth 10)) () ...] 1015: 2 [scan ((#(syntax-object debug-options # ...) (# # #))) () ...] In ice-9/boot-9.scm: 2854: 1 [debug-options (show-file-name #t stack ...)] In unknown file: ?: 0 [debug-options-interface (show-file-name #t stack ...)] ERROR: In procedure debug-options-interface: ERROR: In procedure debug-options-interface: Unknown option name: maxdepth 011 at 9:06 AM, Ted Creedon wrote: > can anyone suggest a suitable log.conf? > > thanks > ted > > > On Wed, Nov 9, 2011 at 8:59 AM, Ted Creedon wrote: > >> announce window & tip of the day pop up before exiting >> >> rm -rf /root/.cache/guile/;GUILE_AUTO_COMPILE=0 gnucash --debug --extra >> >> gnc.bin-Message: main: binreloc relocation support was disabled at >> configure time. >> >> This is a development version. It may or may not work. >> Report bugs and other problems to gnucash-devel@gnucash.org. >> You can also lookup and file bug reports at http://bugzilla.gnome.org >> The last stable version was GnuCash 2.4.7 >> The next stable version will be GnuCash 2.6 >> >> WARNING: (gnucash import-export qif-import): `GNC-DENOM-AUTO' imported >> from both (sw_engine) and (gnucash engine) >> WARNING: (gnucash import-export qif-import): `gnc-build-dotgnucash-path' >> imported from both (sw_engine) and (gnucash core-utils) >> WARNING: (gnucash report report-system): `GNC-DENOM-AUTO' imported from >> both (sw_engine) and (gnucash engine) >> WARNING: (gnucash report report-system): imported module (gnucash >> app-utils) overrides core binding `N_' >> WARNING: (gnucash report report-system): imported module (gnucash >> app-utils) overrides core binding `N_' >> WARNING: (gnucash report report-system): `GNC-DENOM-AUTO' imported from >> both (sw_engine) and (gnucash engine) >> WARNING: (gnucash report report-system): imported module (gnucash >> app-utils) overrides core binding `N_' >> WARNING: (gnucash report report-system): `GNC-DENOM-AUTO' imported from >> both (sw_engine) and (gnucash engine) >> WARNING: (gnucash report report-system): imported module (gnucash >> app-utils) overrides core binding `N_' >> WARNING: (gnucash report stylesheet-plain): imported module (gnucash >> app-utils) overrides core binding `N_' >> WARNING: (gnucash report stylesheet-fancy): imported module (gnucash >> app-utils) overrides core binding `N_' >> WARNING: (gnucash report stylesheet-footer): imported module (gnucash >> app-utils) overrides core binding `N_' >> WARNING: (gnucash report stylesheet-easy): imported module (gnucash >> app-utils) overrides core binding `N_' >> WARNING: (gnucash report standard-reports daily-reports): imported module >> (gnucash app-utils) overrides core binding `N_' >> WARNING: (gnucash report standard-reports account-summary): imported >> module (gnucash app-utils) overrides core binding `N_' >> WARNING: (gnucash report standard-reports general-journal): imported >> module (gnucash app-utils) overrides core binding `N_' >> WARNING: (gnucash report standard-reports advanced-portfolio): imported >> module (gnucash app-utils) overrides core binding `N_' >> WARNING: (gnucash report standard-reports advanced-portfolio): >> `GNC-DENOM-AUTO' imported from both (sw_engine) and (gnucash engine) >> WARNING: (gnucash report standard-reports balance-sheet): imported module >> (gnucash app-utils) overrides core binding `N_' >> WARNING: (gnucash report standard-reports category-barchart): imported >> module (gnucash app-utils) overrides core binding `N_' >> WARNING: (gnucash report standard-reports budget-barchart): imported >> module (gnucash app-utils) overrides core binding `N_' >> WARNING: (gnucash report standard-reports price-scatter): imported module >> (gnucash app-utils) overrides core binding `N_' >
Re: [PATCH] Assorted guile-related build fixes
remember that with 2.0 configure errors out unless --disable-error-on-warning is used ted On Thu, Nov 10, 2011 at 7:54 AM, Ted Creedon wrote: > Self complied from srpm's including guile-devel > > do you want me to set up one system w/ guile 1.8 & 1 with 2.0? > > The 2.0 problem won't go away and I'd prefer to concentrate on 2.0. > > Right now I dual boot one system to get back to an operable gnucash so I'm > in no hurry. > > do you want (large) straces in addition to the stdio debug? > > Ted > > > > On Thu, Nov 10, 2011 at 6:57 AM, Geert Janssens > wrote: > >> On donderdag 10 november 2011, Ted Creedon wrote: >> > Guile 2.0.2 Derek suggested 1.8 but that creates other problems - >> autoconf >> > breaks >> > >> The question will be which of the breakages will be easiest to fix >> though... >> >> > I've built a separate suse 12.1 RC2 clean system to verify the >> integrity of >> > the releases just in case the removal of 1.8 wasn't complete. >> > >> How did you install guile 1.8 ? Via the suse package management ? Self- >> compiled ? >> >> And what errors did you get in autoconf ? >> >> Note that I'm explicitly focussing this thread on guile 1.8. >> >> Geert >> >> > Ted >> > >> > On Thu, Nov 10, 2011 at 6:39 AM, Geert Janssens >> > >> > wrote: >> > > On donderdag 10 november 2011, Derek Atkins wrote: >> > > > Hi, >> > > > >> > > > Ted Creedon writes: >> > > > > guile-config --version >> > > > > guile-config - Guile version 2.0.2 >> > > > >> > > > This implies you are still building against Guile-2, not 1.8. >> > > >> > > Hmm, we are having a couple of conversations mixing up here. >> > > >> > > In one thread Ted is working with me to uncover blocking problems >> > > concerning >> > > guile 2.0 and GnuCash. >> > > >> > > That's not what this thread is about though. Ted wrote >> > > >> > > > not finding guile 1.8 is what I've observed - I can send debug info >> > > >> > > With that I assumed he has both guile 1.8 and guile 2.0 on one >> machine. >> > > So I >> > > wondered where those two were located as a first step to figuring out >> why >> > > guile 1.8 is not detected. >> > > >> > > So perhaps before we continue, let's get an answer to this: >> > > Ted, what are we working at ? Getting GnuCash to run with guile 2.0 or >> > > getting >> > > GnuCash to run on your system, which seems to install guile 2 by >> default >> > > ? >> > > >> > > Geert >> > >> > ___ >> > gnucash-devel mailing list >> > gnucash-devel@gnucash.org >> > https://lists.gnucash.org/mailman/listinfo/gnucash-devel >> >> > ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: [PATCH] Assorted guile-related build fixes
Self complied from srpm's including guile-devel do you want me to set up one system w/ guile 1.8 & 1 with 2.0? The 2.0 problem won't go away and I'd prefer to concentrate on 2.0. Right now I dual boot one system to get back to an operable gnucash so I'm in no hurry. do you want (large) straces in addition to the stdio debug? Ted On Thu, Nov 10, 2011 at 6:57 AM, Geert Janssens wrote: > On donderdag 10 november 2011, Ted Creedon wrote: > > Guile 2.0.2 Derek suggested 1.8 but that creates other problems - > autoconf > > breaks > > > The question will be which of the breakages will be easiest to fix > though... > > > I've built a separate suse 12.1 RC2 clean system to verify the integrity > of > > the releases just in case the removal of 1.8 wasn't complete. > > > How did you install guile 1.8 ? Via the suse package management ? Self- > compiled ? > > And what errors did you get in autoconf ? > > Note that I'm explicitly focussing this thread on guile 1.8. > > Geert > > > Ted > > > > On Thu, Nov 10, 2011 at 6:39 AM, Geert Janssens > > > > wrote: > > > On donderdag 10 november 2011, Derek Atkins wrote: > > > > Hi, > > > > > > > > Ted Creedon writes: > > > > > guile-config --version > > > > > guile-config - Guile version 2.0.2 > > > > > > > > This implies you are still building against Guile-2, not 1.8. > > > > > > Hmm, we are having a couple of conversations mixing up here. > > > > > > In one thread Ted is working with me to uncover blocking problems > > > concerning > > > guile 2.0 and GnuCash. > > > > > > That's not what this thread is about though. Ted wrote > > > > > > > not finding guile 1.8 is what I've observed - I can send debug info > > > > > > With that I assumed he has both guile 1.8 and guile 2.0 on one machine. > > > So I > > > wondered where those two were located as a first step to figuring out > why > > > guile 1.8 is not detected. > > > > > > So perhaps before we continue, let's get an answer to this: > > > Ted, what are we working at ? Getting GnuCash to run with guile 2.0 or > > > getting > > > GnuCash to run on your system, which seems to install guile 2 by > default > > > ? > > > > > > Geert > > > > ___ > > gnucash-devel mailing list > > gnucash-devel@gnucash.org > > https://lists.gnucash.org/mailman/listinfo/gnucash-devel > > ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: [PATCH] Assorted guile-related build fixes
Guile 2.0.2 Derek suggested 1.8 but that creates other problems - autoconf breaks I've built a separate suse 12.1 RC2 clean system to verify the integrity of the releases just in case the removal of 1.8 wasn't complete. Ted On Thu, Nov 10, 2011 at 6:39 AM, Geert Janssens wrote: > On donderdag 10 november 2011, Derek Atkins wrote: > > Hi, > > > > Ted Creedon writes: > > > guile-config --version > > > guile-config - Guile version 2.0.2 > > > > This implies you are still building against Guile-2, not 1.8. > > > Hmm, we are having a couple of conversations mixing up here. > > In one thread Ted is working with me to uncover blocking problems > concerning > guile 2.0 and GnuCash. > > That's not what this thread is about though. Ted wrote > > not finding guile 1.8 is what I've observed - I can send debug info > > With that I assumed he has both guile 1.8 and guile 2.0 on one machine. So > I > wondered where those two were located as a first step to figuring out why > guile 1.8 is not detected. > > So perhaps before we continue, let's get an answer to this: > Ted, what are we working at ? Getting GnuCash to run with guile 2.0 or > getting > GnuCash to run on your system, which seems to install guile 2 by default ? > > Geert > ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Fwd: 2.4.8 git /w guile 2.0
can anyone suggest a suitable log.conf? thanks ted On Wed, Nov 9, 2011 at 8:59 AM, Ted Creedon wrote: > announce window & tip of the day pop up before exiting > > rm -rf /root/.cache/guile/;GUILE_AUTO_COMPILE=0 gnucash --debug --extra > > gnc.bin-Message: main: binreloc relocation support was disabled at > configure time. > > This is a development version. It may or may not work. > Report bugs and other problems to gnucash-devel@gnucash.org. > You can also lookup and file bug reports at http://bugzilla.gnome.org > The last stable version was GnuCash 2.4.7 > The next stable version will be GnuCash 2.6 > > WARNING: (gnucash import-export qif-import): `GNC-DENOM-AUTO' imported > from both (sw_engine) and (gnucash engine) > WARNING: (gnucash import-export qif-import): `gnc-build-dotgnucash-path' > imported from both (sw_engine) and (gnucash core-utils) > WARNING: (gnucash report report-system): `GNC-DENOM-AUTO' imported from > both (sw_engine) and (gnucash engine) > WARNING: (gnucash report report-system): imported module (gnucash > app-utils) overrides core binding `N_' > WARNING: (gnucash report report-system): imported module (gnucash > app-utils) overrides core binding `N_' > WARNING: (gnucash report report-system): `GNC-DENOM-AUTO' imported from > both (sw_engine) and (gnucash engine) > WARNING: (gnucash report report-system): imported module (gnucash > app-utils) overrides core binding `N_' > WARNING: (gnucash report report-system): `GNC-DENOM-AUTO' imported from > both (sw_engine) and (gnucash engine) > WARNING: (gnucash report report-system): imported module (gnucash > app-utils) overrides core binding `N_' > WARNING: (gnucash report stylesheet-plain): imported module (gnucash > app-utils) overrides core binding `N_' > WARNING: (gnucash report stylesheet-fancy): imported module (gnucash > app-utils) overrides core binding `N_' > WARNING: (gnucash report stylesheet-footer): imported module (gnucash > app-utils) overrides core binding `N_' > WARNING: (gnucash report stylesheet-easy): imported module (gnucash > app-utils) overrides core binding `N_' > WARNING: (gnucash report standard-reports daily-reports): imported module > (gnucash app-utils) overrides core binding `N_' > WARNING: (gnucash report standard-reports account-summary): imported > module (gnucash app-utils) overrides core binding `N_' > WARNING: (gnucash report standard-reports general-journal): imported > module (gnucash app-utils) overrides core binding `N_' > WARNING: (gnucash report standard-reports advanced-portfolio): imported > module (gnucash app-utils) overrides core binding `N_' > WARNING: (gnucash report standard-reports advanced-portfolio): > `GNC-DENOM-AUTO' imported from both (sw_engine) and (gnucash engine) > WARNING: (gnucash report standard-reports balance-sheet): imported module > (gnucash app-utils) overrides core binding `N_' > WARNING: (gnucash report standard-reports category-barchart): imported > module (gnucash app-utils) overrides core binding `N_' > WARNING: (gnucash report standard-reports budget-barchart): imported > module (gnucash app-utils) overrides core binding `N_' > WARNING: (gnucash report standard-reports price-scatter): imported module > (gnucash app-utils) overrides core binding `N_' > WARNING: (gnucash report standard-reports sx-summary): imported module > (gnucash app-utils) overrides core binding `N_' > WARNING: (gnucash report standard-reports average-balance): imported > module (gnucash app-utils) overrides core binding `N_' > WARNING: (gnucash report standard-reports equity-statement): imported > module (gnucash app-utils) overrides core binding `N_' > WARNING: (gnucash report standard-reports transaction): imported module > (gnucash app-utils) overrides core binding `N_' > WARNING: (gnucash report standard-reports budget-flow): imported module > (gnucash app-utils) overrides core binding `N_' > WARNING: (gnucash report standard-reports account-piecharts): imported > module (gnucash app-utils) overrides core binding `N_' > WARNING: (gnucash business-utils): imported module (gnucash app-utils) > overrides core binding `N_' > WARNING: (gnucash business-utils): imported module (gnucash app-utils) > overrides core binding `N_' > WARNING: (gnucash report hello-world): imported module (gnucash app-utils) > overrides core binding `N_' > WARNING: (gnucash report view-column): imported module (gnucash app-utils) > overrides core binding `N_' > WARNING: (gnucash report welcome-to-gnucash): imported module (gnucash > app-utils) overrides core binding `N_' > WARNING: (gnucash report report-gnome):
Re: Fwd: 2.4.8 git /w guile 2.0
e-9/psyntax.scm:1326:30: In procedure chi-macro: ice-9/psyntax.scm:1326:30: Syntax error: unknown location: source expression failed to match any pattern in form do On Wed, Nov 9, 2011 at 1:37 AM, Geert Janssens wrote: > Note that I don't have a guile 2 installed currently (and right now I don't > have time to set one up). So I'm making suggestions based on what I read > about > it and interpreting the errors you send here... > > What happens if you remove /root/.cache/guile/ and run again (still with > GUILE_AUTO_COMPILE=0) ? > > Geert > > On dinsdag 8 november 2011, Ted Creedon wrote: > > > ./configure --disable-error-on-warning --enable-debug;time make > > > > > > produces the following when executiing GUILE_AUTO_COMPILE=0 gnucash > > > > > > gnucash # GUILE_AUTO_COMPILE=0 gnucash > > > gnc.bin-Message: main: binreloc relocation support was disabled at > > > configure time. > > > > > > > > > > > > This is a development version. It may or may not work. > > > Report bugs and other problems to gnucash-devel@gnucash.org. > > > You can also lookup and file bug reports at http://bugzilla.gnome.org > > > The last stable version was GnuCash 2.4.7 > > > The next stable version will be GnuCash 2.6 > > > > > > ;;; note: source file > > > /usr/local/share/gnucash/guile-modules/gnucash/printf.scm > > > ;;; newer than compiled > > > > /root/.cache/guile/ccache/2.0-LE-8-2.0/usr/local/share/gnucash/guile-modu > > > les/gnucash/printf.scm.go ;;; note: source file > > > /usr/local/share/gnucash/scm/string.scm > > > ;;; newer than compiled > > > > /root/.cache/guile/ccache/2.0-LE-8-2.0/usr/local/share/gnucash/scm/string > > > .scm.go ;;; note: source file /usr/local/share/gnucash/scm/doc.scm > > > ;;; newer than compiled > > > /root/.cache/guile/ccache/2.0-LE-8-2.0/usr/local/share/gnucash/scm/ > doc.sc > > > m.go ;;; note: source file /usr/local/share/gnucash/scm/main-window.scm > > > ;;; newer than compiled > > > > /root/.cache/guile/ccache/2.0-LE-8-2.0/usr/local/share/gnucash/scm/main-w > > > indow.scm.go ;;; note: source file /usr/local/share/gnucash/scm/fin.scm > > > ;;; newer than compiled > > > /root/.cache/guile/ccache/2.0-LE-8-2.0/usr/local/share/gnucash/scm/ > fin.sc > > > m.go ;;; note: source file > /usr/local/share/gnucash/scm/build-config.scm > > > ;;; newer than compiled > > > > /root/.cache/guile/ccache/2.0-LE-8-2.0/usr/local/share/gnucash/scm/build- > > > config.scm.go WARNING: (gnucash import-export qif-import): > > > `GNC-DENOM-AUTO' imported from both (sw_engine) and (gnucash engine) > > > WARNING: (gnucash import-export qif-import): > `gnc-build-dotgnucash-path' > > > imported from both (sw_engine) and (gnucash core-utils) > > > WARNING: (gnucash report report-system): `GNC-DENOM-AUTO' imported from > > > both (sw_engine) and (gnucash engine) > > > WARNING: (gnucash report report-system): imported module (gnucash > > > app-utils) overrides core binding `N_' > > > WARNING: (gnucash report report-system): imported module (gnucash > > > app-utils) overrides core binding `N_' > > > WARNING: (gnucash report report-system): `GNC-DENOM-AUTO' imported from > > > both (sw_engine) and (gnucash engine) > > > WARNING: (gnucash report report-system): imported module (gnucash > > > app-utils) overrides core binding `N_' > > > WARNING: (gnucash report report-system): `GNC-DENOM-AUTO' imported from > > > both (sw_engine) and (gnucash engine) > > > WARNING: (gnucash report report-system): imported module (gnucash > > > app-utils) overrides core binding `N_' > > > WARNING: (gnucash report stylesheet-plain): imported module (gnucash > > > app-utils) overrides core binding `N_' > > > WARNING: (gnucash report stylesheet-fancy): imported module (gnucash > > > app-utils) overrides core binding `N_' > > > WARNING: (gnucash report stylesheet-footer): imported module (gnucash > > > app-utils) overrides core binding `N_' > > > WARNING: (gnucash report stylesheet-easy): imported module (gnucash > > > app-utils) overrides core binding `N_' > > > WARNING: (gnucash report standard-reports daily-reports): imported > module > > > (gnucash app-utils) overrides core binding `N_' > > > WARNING: (gnucash report standard-reports account-summary): imported > > > module (gnuc
Re: [PATCH] Assorted guile-related build fixes
guile-config --version guile-config - Guile version 2.0.2 On Wed, Nov 9, 2011 at 6:58 AM, Derek Atkins wrote: > Geert Janssens writes: > > > On dinsdag 8 november 2011, Ted Creedon wrote: > >> not finding guile 1.8 is what I've observed - I can send debug info > from an > >> strace of configure if desired > >> > >> i have 2 systems one guiile 1.8 & one 2.0 > >> > >>From which source are you starting, and where are guile-1.8 and guile-2.0 > > installed on your system ? > > More importantly, what does guile-config --version say to you? > > > Geert > > -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 > warl...@mit.eduPGP key available > ___ > gnucash-devel mailing list > gnucash-devel@gnucash.org > https://lists.gnucash.org/mailman/listinfo/gnucash-devel > ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Fwd: 2.4.8 git /w guile 2.0
summarizing: ./configure --disable-error-on-warning produces a gnucash executable ./configure produces deprecated-declarations errors ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Fwd: 2.4.8 git /w guile 2.0
> ./configure --disable-error-on-warning --enable-debug;time make > > produces the following when executiing GUILE_AUTO_COMPILE=0 gnucash > > gnucash # GUILE_AUTO_COMPILE=0 gnucash > gnc.bin-Message: main: binreloc relocation support was disabled at > configure time. > > > > This is a development version. It may or may not work. > Report bugs and other problems to gnucash-devel@gnucash.org. > You can also lookup and file bug reports at http://bugzilla.gnome.org > The last stable version was GnuCash 2.4.7 > The next stable version will be GnuCash 2.6 > > ;;; note: source file > /usr/local/share/gnucash/guile-modules/gnucash/printf.scm > ;;; newer than compiled > /root/.cache/guile/ccache/2.0-LE-8-2.0/usr/local/share/gnucash/guile-modules/gnucash/printf.scm.go > ;;; note: source file /usr/local/share/gnucash/scm/string.scm > ;;; newer than compiled > /root/.cache/guile/ccache/2.0-LE-8-2.0/usr/local/share/gnucash/scm/string.scm.go > ;;; note: source file /usr/local/share/gnucash/scm/doc.scm > ;;; newer than compiled > /root/.cache/guile/ccache/2.0-LE-8-2.0/usr/local/share/gnucash/scm/doc.scm.go > ;;; note: source file /usr/local/share/gnucash/scm/main-window.scm > ;;; newer than compiled > /root/.cache/guile/ccache/2.0-LE-8-2.0/usr/local/share/gnucash/scm/main-window.scm.go > ;;; note: source file /usr/local/share/gnucash/scm/fin.scm > ;;; newer than compiled > /root/.cache/guile/ccache/2.0-LE-8-2.0/usr/local/share/gnucash/scm/fin.scm.go > ;;; note: source file /usr/local/share/gnucash/scm/build-config.scm > ;;; newer than compiled > /root/.cache/guile/ccache/2.0-LE-8-2.0/usr/local/share/gnucash/scm/build-config.scm.go > WARNING: (gnucash import-export qif-import): `GNC-DENOM-AUTO' imported > from both (sw_engine) and (gnucash engine) > WARNING: (gnucash import-export qif-import): `gnc-build-dotgnucash-path' > imported from both (sw_engine) and (gnucash core-utils) > WARNING: (gnucash report report-system): `GNC-DENOM-AUTO' imported from > both (sw_engine) and (gnucash engine) > WARNING: (gnucash report report-system): imported module (gnucash > app-utils) overrides core binding `N_' > WARNING: (gnucash report report-system): imported module (gnucash > app-utils) overrides core binding `N_' > WARNING: (gnucash report report-system): `GNC-DENOM-AUTO' imported from > both (sw_engine) and (gnucash engine) > WARNING: (gnucash report report-system): imported module (gnucash > app-utils) overrides core binding `N_' > WARNING: (gnucash report report-system): `GNC-DENOM-AUTO' imported from > both (sw_engine) and (gnucash engine) > WARNING: (gnucash report report-system): imported module (gnucash > app-utils) overrides core binding `N_' > WARNING: (gnucash report stylesheet-plain): imported module (gnucash > app-utils) overrides core binding `N_' > WARNING: (gnucash report stylesheet-fancy): imported module (gnucash > app-utils) overrides core binding `N_' > WARNING: (gnucash report stylesheet-footer): imported module (gnucash > app-utils) overrides core binding `N_' > WARNING: (gnucash report stylesheet-easy): imported module (gnucash > app-utils) overrides core binding `N_' > WARNING: (gnucash report standard-reports daily-reports): imported module > (gnucash app-utils) overrides core binding `N_' > WARNING: (gnucash report standard-reports account-summary): imported > module (gnucash app-utils) overrides core binding `N_' > WARNING: (gnucash report standard-reports general-journal): imported > module (gnucash app-utils) overrides core binding `N_' > WARNING: (gnucash report standard-reports advanced-portfolio): imported > module (gnucash app-utils) overrides core binding `N_' > WARNING: (gnucash report standard-reports advanced-portfolio): > `GNC-DENOM-AUTO' imported from both (sw_engine) and (gnucash engine) > WARNING: (gnucash report standard-reports balance-sheet): imported module > (gnucash app-utils) overrides core binding `N_' > WARNING: (gnucash report standard-reports category-barchart): imported > module (gnucash app-utils) overrides core binding `N_' > WARNING: (gnucash report standard-reports budget-barchart): imported > module (gnucash app-utils) overrides core binding `N_' > WARNING: (gnucash report standard-reports price-scatter): imported module > (gnucash app-utils) overrides core binding `N_' > WARNING: (gnucash report standard-reports sx-summary): imported module > (gnucash app-utils) overrides core binding `N_' > WARNING: (gnucash report standard-reports average-balance): imported > module (gnucash app-utils) overrides core binding `N_' > WARNING: (gnucash report standard-reports equity-statement): imported > module (gnucash app-utils) overrides core binding `N_' > WARNING: (gnucash report standard-reports transaction): imported module > (gnucash app-utils) overrides core binding `N_' > WARNING: (gnucash report standard-reports budget-flow): imported module > (gnucash app-utils) overrides core binding `N_' > WARNING: (gnucash report standard-reports account-pie
Re: Fwd: 2.4.8 git /w guile 2.0
the switch --disable-error-on-warning is required to get a make completed if not used then: wig-core-utils.c:1386:7: error: 'scm_makstr' is deprecated (declared at /usr/include/guile/2.0/libguile/deprecated.h:124) [-Werror=deprecated-declarations] swig-core-utils.c:1389:3: error: 'scm_must_free' is deprecated (declared at /usr/include/guile/2.0/libguile/gc.h:268) [-Werror=deprecated-declarations] swig-core-utils.c: In function '_wrap_gnc_scm_log_warn': swig-core-utils.c:1411:3: error: 'scm_must_free' is deprecated (declared at /usr/include/guile/2.0/libguile/gc.h:268) [-Werror=deprecated-declarations] swig-core-utils.c: In function '_wrap_gnc_scm_log_error': swig-core-utils.c:1433:3: error: 'scm_must_free' is deprecated (declared at /usr/include/guile/2.0/libguile/gc.h:268) [-Werror=deprecated-declarations] swig-core-utils.c: In function '_wrap_gnc_scm_log_msg': swig-core-utils.c:1455:3: error: 'scm_must_free' is deprecated (declared at /usr/include/guile/2.0/libguile/gc.h:268) [-Werror=deprecated-declarations] swig-core-utils.c: In function '_wrap_gnc_scm_log_debug': swig-core-utils.c:1477:3: error: 'scm_must_free' is deprecated (declared at /usr/include/guile/2.0/libguile/gc.h:268) [-Werror=deprecated-declarations] swig-core-utils.c: In function '_wrap_gnc_utf8_strip_invalid_strdup': swig-core-utils.c:1500:5: error: 'scm_makfrom0str' is deprecated (declared at /usr/include/guile/2.0/libguile/deprecated.h:724) [-Werror=deprecated-declarations] swig-core-utils.c:1502:7: error: 'scm_makstr' is deprecated (declared at /usr/include/guile/2.0/libguile/deprecated.h:124) [-Werror=deprecated-declarations] swig-core-utils.c:1505:3: error: 'scm_must_free' is deprecated (declared at /usr/include/guile/2.0/libguile/gc.h:268) [-Werror=deprecated-declarations] swig-core-utils.c: In function '_wrap_gnc_locale_from_utf8': swig-core-utils.c:1529:5: error: 'scm_makfrom0str' is deprecated (declared at /usr/include/guile/2.0/libguile/deprecated.h:724) [-Werror=deprecated-declarations] swig-core-utils.c:1531:7: error: 'scm_makstr' is deprecated (declared at /usr/include/guile/2.0/libguile/deprecated.h:124) [-Werror=deprecated-declarations] swig-core-utils.c:1534:3: error: 'scm_must_free' is deprecated (declared at /usr/include/guile/2.0/libguile/gc.h:268) [-Werror=deprecated-declarations] swig-core-utils.c: In function '_wrap_gnc_locale_to_utf8': swig-core-utils.c:1558:5: error: 'scm_makfrom0str' is deprecated (declared at /usr/include/guile/2.0/libguile/deprecated.h:724) [-Werror=deprecated-declarations] swig-core-utils.c:1560:7: error: 'scm_makstr' is deprecated (declared at /usr/include/guile/2.0/libguile/deprecated.h:124) [-Werror=deprecated-declarations] swig-core-utils.c:1563:3: error: 'scm_must_free' is deprecated (declared at /usr/include/guile/2.0/libguile/gc.h:268) [-Werror=deprecated-declarations] swig-core-utils.c: In function '_wrap_gnc_locale_default_iso_currency_code': swig-core-utils.c:1581:5: error: 'scm_makfrom0str' is deprecated (declared at /usr/include/guile/2.0/libguile/deprecated.h:724) [-Werror=deprecated-declarations] swig-core-utils.c:1583:7: error: 'scm_makstr' is deprecated (declared at /usr/include/guile/2.0/libguile/deprecated.h:124) [-Werror=deprecated-declarations] swig-core-utils.c: In function '_wrap_gncsutf8q___': swig-core-utils.c:1608:3: error: 'scm_must_free' is deprecated (declared at /usr/include/guile/2.0/libguile/gc.h:268) [-Werror=deprecated-declarations] cc1: all warnings being treated as errors make[5]: *** [swig-core-utils.lo] Error 1 make[5]: Leaving directory `/data/gnucash/src/core-utils' make[4]: *** [all-recursive] Error 1 make[4]: Leaving directory `/data/gnucash/src/core-utils' make[3]: *** [all] Error 2 make[3]: Leaving directory `/data/gnucash/src/core-utils' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/data/gnucash/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/data/gnucash' make: *** [all] Error 2 ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: [PATCH] Assorted guile-related build fixes
not finding guile 1.8 is what I've observed - I can send debug info from an strace of configure if desired i have 2 systems one guiile 1.8 & one 2.0 ted On Tue, Nov 8, 2011 at 9:04 AM, Bill Nottingham wrote: > Geert Janssens (janssens-ge...@telenet.be) said: > > On vrijdag 13 mei 2011, Bill Nottingham wrote: > > > I was doing some testing with guile-2.0 and GnuCash, and encountered > > > the need for the following fixes to make it build. > > > > > > (Note: it still doesn't *work*, but it at least builds for further > > > testing.) > > > > > > Total changes: > > > configure.ac| 14 -- > > > src/import-export/aqbanking/Makefile.am |1 + > > > src/plugins/bi_import/Makefile.am |1 + > > > 3 files changed, 10 insertions(+), 6 deletions(-) > > > > > > ___ > > > gnucash-devel mailing list > > > gnucash-devel@gnucash.org > > > https://lists.gnucash.org/mailman/listinfo/gnucash-devel > > > > Bill, > > > > I just discovered this series of your patches in my mailbox, all covered > with > > dust ;) > > > > I'm under the impression they never got applied, right ? > > AFAIK, yes, although I've only really checked on the 2.4 branch. > > > Patch 2 is obsolete by now [1]. I have made some other changes in the > source > > so aqbanking and bi_import are no longer dependent on guile. > > > > Patch 3 seems to make sense to me, I'll apply it shortly. > > > > And regarding patch 1, I'm a bit confused. While working on the bug > mentioned > > below, Petr had written a patch very similar to your patch 2, yet it did > seem > > to work without applying patch 1. So your patch series suggests > GUILE_INCS has > > to be AC_SUBST before it can be included, but Petr's patch suggests > otherwise. > > Is GUILE_INCS automatically substituted as part of the other macro's > perhaps ? > > > > I'm not that well versed in the autotools magic, so I prefer to ask > first. > > Hah, neither am I. But looking at it, GUILE_INCS is in most of the > Makefile.am files, so having an explicit substitute of it looks right. (The > problem I remember having is it not finding guile correctly in > /usr/include/guile/2.0/... which is where our test guile-2.0 packages were > putting it). > > Bill > > ___ > gnucash-devel mailing list > gnucash-devel@gnucash.org > https://lists.gnucash.org/mailman/listinfo/gnucash-devel > ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Fwd: make check failures
Derek suggested I try guile 1.8 but it breaks graphviz and configure breaks trying to find guile 1.8 what git command should I use to get the patched files? right now I'm dual booting to keep my gnucash going. tedc On Tue, Nov 8, 2011 at 12:29 AM, Geert Janssens wrote: > On dinsdag 8 november 2011, Ted Creedon wrote: > > per irc chat w/ tedc & warlord > > Ted, from the irc log I see you try to build GnuCash for OpenSuse with > guile > 2.0. > > The 2.4 branch for sure won't work with guile 2.0. I have committed a > series > of patches by guile developer Andy Wingo to the development branch which > should improve the guile 2.0 support in there. The changes are too > intrusive > to introduce in the stable 2.4 series as well unfortunately. > > But there are known problems in the development branch too with Guile 2.0. > See > for example the bug reported in our bug tracker by the Debian maintainers > [1] > which among others also reports the same make check failures. > > I believe these are due to the swig guile support. Swig continues to > generate > guile code using deprecated guile symbols. Check out the bug report and the > downstream links to learn more about it. > > Geert > > > [1] https://bugzilla.gnome.org/show_bug.cgi?id=655901 > ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
make check failures
per irc chat w/ tedc Making check in . make[1]: Entering directory `/data/gnucash-2.4.8' make[1]: Leaving directory `/data/gnucash-2.4.8' Making check in doc make[1]: Entering directory `/data/gnucash-2.4.8/doc' Making check in examples make[2]: Entering directory `/data/gnucash-2.4.8/doc/examples' make[2]: Nothing to be done for `check'. make[2]: Leaving directory `/data/gnucash-2.4.8/doc/examples' make[2]: Entering directory `/data/gnucash-2.4.8/doc' make[2]: Nothing to be done for `check-am'. make[2]: Leaving directory `/data/gnucash-2.4.8/doc' make[1]: Leaving directory `/data/gnucash-2.4.8/doc' Making check in lib make[1]: Entering directory `/data/gnucash-2.4.8/lib' Making check in libc make[2]: Entering directory `/data/gnucash-2.4.8/lib/libc' make[2]: Nothing to be done for `check'. make[2]: Leaving directory `/data/gnucash-2.4.8/lib/libc' Making check in guile-www make[2]: Entering directory `/data/gnucash-2.4.8/lib/guile-www' make[2]: Nothing to be done for `check'. make[2]: Leaving directory `/data/gnucash-2.4.8/lib/guile-www' Making check in stf make[2]: Entering directory `/data/gnucash-2.4.8/lib/stf' make[2]: Nothing to be done for `check'. make[2]: Leaving directory `/data/gnucash-2.4.8/lib/stf' make[2]: Entering directory `/data/gnucash-2.4.8/lib' make[2]: Nothing to be done for `check-am'. make[2]: Leaving directory `/data/gnucash-2.4.8/lib' make[1]: Leaving directory `/data/gnucash-2.4.8/lib' Making check in src make[1]: Entering directory `/data/gnucash-2.4.8/src' Making check in . make[2]: Entering directory `/data/gnucash-2.4.8/src' make[2]: Nothing to be done for `check-am'. make[2]: Leaving directory `/data/gnucash-2.4.8/src' Making check in libqof make[2]: Entering directory `/data/gnucash-2.4.8/src/libqof' Making check in . make[3]: Entering directory `/data/gnucash-2.4.8/src/libqof' make[3]: Nothing to be done for `check-am'. make[3]: Leaving directory `/data/gnucash-2.4.8/src/libqof' Making check in qof make[3]: Entering directory `/data/gnucash-2.4.8/src/libqof/qof' Making check in . make[4]: Entering directory `/data/gnucash-2.4.8/src/libqof/qof' make test-qofmath make[5]: Entering directory `/data/gnucash-2.4.8/src/libqof/qof' make[5]: `test-qofmath' is up to date. make[5]: Leaving directory `/data/gnucash-2.4.8/src/libqof/qof' make[4]: Leaving directory `/data/gnucash-2.4.8/src/libqof/qof' Making check in test make[4]: Entering directory `/data/gnucash-2.4.8/src/libqof/qof/test' make check-local make[5]: Entering directory `/data/gnucash-2.4.8/src/libqof/qof/test' TEST: test-qof... (pid=24264) /qof/qofbook:OK /qof/qofbook:OK /qof/qofinstance:OK /qof/qofsession: OK PASS: test-qof make[5]: Leaving directory `/data/gnucash-2.4.8/src/libqof/qof/test' make[4]: Leaving directory `/data/gnucash-2.4.8/src/libqof/qof/test' make[3]: Leaving directory `/data/gnucash-2.4.8/src/libqof/qof' make[2]: Leaving directory `/data/gnucash-2.4.8/src/libqof' Making check in debug make[2]: Entering directory `/data/gnucash-2.4.8/src/debug' Making check in valgrind make[3]: Entering directory `/data/gnucash-2.4.8/src/debug/valgrind' make[3]: Nothing to be done for `check'. make[3]: Leaving directory `/data/gnucash-2.4.8/src/debug/valgrind' make[3]: Entering directory `/data/gnucash-2.4.8/src/debug' make[3]: Nothing to be done for `check-am'. make[3]: Leaving directory `/data/gnucash-2.4.8/src/debug' make[2]: Leaving directory `/data/gnucash-2.4.8/src/debug' Making check in doc make[2]: Entering directory `/data/gnucash-2.4.8/src/doc' Making check in design make[3]: Entering directory `/data/gnucash-2.4.8/src/doc/design' make[3]: Nothing to be done for `check'. make[3]: Leaving directory `/data/gnucash-2.4.8/src/doc/design' Making check in xml make[3]: Entering directory `/data/gnucash-2.4.8/src/doc/xml' make[3]: Nothing to be done for `check'. make[3]: Leaving directory `/data/gnucash-2.4.8/src/doc/xml' make[3]: Entering directory `/data/gnucash-2.4.8/src/doc' make[3]: Nothing to be done for `check-am'. make[3]: Leaving directory `/data/gnucash-2.4.8/src/doc' make[2]: Leaving directory `/data/gnucash-2.4.8/src/doc' Making check in pixmaps make[2]: Entering directory `/data/gnucash-2.4.8/src/pixmaps' make[2]: Nothing to be done for `check'. make[2]: Leaving directory `/data/gnucash-2.4.8/src/pixmaps' Making check in test-core make[2]: Entering directory `/data/gnucash-2.4.8/src/test-core' make[2]: Nothing to be done for `check'. make[2]: Leaving directory `/data/gnucash-2.4.8/src/test-core' Making check in core-utils make[2]: Entering directory `/data/gnucash-2.4.8/src/core-utils' if [ ! -f gnc-svninfo.h ]; then cp _gnc-svninfo.h gnc-svninfo.h; fi cmp -s _gnc-svninfo.h gnc-svninfo.h || cp _gnc-svninfo.h gnc-svninfo.h rm -f _gnc-svninfo.h if [ ! -f gnc-version.h ]; then cp _gnc-ve
Fwd: make check failures
per irc chat w/ tedc & warlord Making check in . make[1]: Entering directory `/data/gnucash-2.4.8' make[1]: Leaving directory `/data/gnucash-2.4.8' Making check in doc make[1]: Entering directory `/data/gnucash-2.4.8/doc' Making check in examples make[2]: Entering directory `/data/gnucash-2.4.8/doc/examples' make[2]: Nothing to be done for `check'. make[2]: Leaving directory `/data/gnucash-2.4.8/doc/examples' make[2]: Entering directory `/data/gnucash-2.4.8/doc' make[2]: Nothing to be done for `check-am'. make[2]: Leaving directory `/data/gnucash-2.4.8/doc' make[1]: Leaving directory `/data/gnucash-2.4.8/doc' Making check in lib make[1]: Entering directory `/data/gnucash-2.4.8/lib' Making check in libc make[2]: Entering directory `/data/gnucash-2.4.8/lib/libc' make[2]: Nothing to be done for `check'. make[2]: Leaving directory `/data/gnucash-2.4.8/lib/libc' Making check in guile-www make[2]: Entering directory `/data/gnucash-2.4.8/lib/guile-www' make[2]: Nothing to be done for `check'. make[2]: Leaving directory `/data/gnucash-2.4.8/lib/guile-www' Making check in stf make[2]: Entering directory `/data/gnucash-2.4.8/lib/stf' make[2]: Nothing to be done for `check'. make[2]: Leaving directory `/data/gnucash-2.4.8/lib/stf' make[2]: Entering directory `/data/gnucash-2.4.8/lib' make[2]: Nothing to be done for `check-am'. make[2]: Leaving directory `/data/gnucash-2.4.8/lib' make[1]: Leaving directory `/data/gnucash-2.4.8/lib' Making check in src make[1]: Entering directory `/data/gnucash-2.4.8/src' Making check in . make[2]: Entering directory `/data/gnucash-2.4.8/src' make[2]: Nothing to be done for `check-am'. make[2]: Leaving directory `/data/gnucash-2.4.8/src' Making check in libqof make[2]: Entering directory `/data/gnucash-2.4.8/src/libqof' Making check in . make[3]: Entering directory `/data/gnucash-2.4.8/src/libqof' make[3]: Nothing to be done for `check-am'. make[3]: Leaving directory `/data/gnucash-2.4.8/src/libqof' Making check in qof make[3]: Entering directory `/data/gnucash-2.4.8/src/libqof/qof' Making check in . make[4]: Entering directory `/data/gnucash-2.4.8/src/libqof/qof' make test-qofmath make[5]: Entering directory `/data/gnucash-2.4.8/src/libqof/qof' make[5]: `test-qofmath' is up to date. make[5]: Leaving directory `/data/gnucash-2.4.8/src/libqof/qof' make[4]: Leaving directory `/data/gnucash-2.4.8/src/libqof/qof' Making check in test make[4]: Entering directory `/data/gnucash-2.4.8/src/libqof/qof/test' make check-local make[5]: Entering directory `/data/gnucash-2.4.8/src/libqof/qof/test' TEST: test-qof... (pid=24264) /qof/qofbook:OK /qof/qofbook:OK /qof/qofinstance:OK /qof/qofsession: OK PASS: test-qof make[5]: Leaving directory `/data/gnucash-2.4.8/src/libqof/qof/test' make[4]: Leaving directory `/data/gnucash-2.4.8/src/libqof/qof/test' make[3]: Leaving directory `/data/gnucash-2.4.8/src/libqof/qof' make[2]: Leaving directory `/data/gnucash-2.4.8/src/libqof' Making check in debug make[2]: Entering directory `/data/gnucash-2.4.8/src/debug' Making check in valgrind make[3]: Entering directory `/data/gnucash-2.4.8/src/debug/valgrind' make[3]: Nothing to be done for `check'. make[3]: Leaving directory `/data/gnucash-2.4.8/src/debug/valgrind' make[3]: Entering directory `/data/gnucash-2.4.8/src/debug' make[3]: Nothing to be done for `check-am'. make[3]: Leaving directory `/data/gnucash-2.4.8/src/debug' make[2]: Leaving directory `/data/gnucash-2.4.8/src/debug' Making check in doc make[2]: Entering directory `/data/gnucash-2.4.8/src/doc' Making check in design make[3]: Entering directory `/data/gnucash-2.4.8/src/doc/design' make[3]: Nothing to be done for `check'. make[3]: Leaving directory `/data/gnucash-2.4.8/src/doc/design' Making check in xml make[3]: Entering directory `/data/gnucash-2.4.8/src/doc/xml' make[3]: Nothing to be done for `check'. make[3]: Leaving directory `/data/gnucash-2.4.8/src/doc/xml' make[3]: Entering directory `/data/gnucash-2.4.8/src/doc' make[3]: Nothing to be done for `check-am'. make[3]: Leaving directory `/data/gnucash-2.4.8/src/doc' make[2]: Leaving directory `/data/gnucash-2.4.8/src/doc' Making check in pixmaps make[2]: Entering directory `/data/gnucash-2.4.8/src/pixmaps' make[2]: Nothing to be done for `check'. make[2]: Leaving directory `/data/gnucash-2.4.8/src/pixmaps' Making check in test-core make[2]: Entering directory `/data/gnucash-2.4.8/src/test-core' make[2]: Nothing to be done for `check'. make[2]: Leaving directory `/data/gnucash-2.4.8/src/test-core' Making check in core-utils make[2]: Entering directory `/data/gnucash-2.4.8/src/core-utils' if [ ! -f gnc-svninfo.h ]; then cp _gnc-svninfo.h gnc-svninfo.h; fi cmp -s _gnc-svninfo.h gnc-svninfo.h || cp _gnc-svninfo.h gnc-svninfo.h rm -f _gnc-svninfo.h if [ ! -f gnc-version.h ]; then