From: George Shapovalov <georges@its.caltech.edu>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] GnuCash error...
Date: Fri, 15 Mar 2002 11:46:24 -0800 [thread overview]
Message-ID: <200203151941.LAA27032@chamber.cco.caltech.edu> (raw)
In-Reply-To: <1016206265.21104.6.camel@fightclub.culthero.info>
Please take a look at bugs.gentoo.org, bug#77:
http://bugs.gentoo.org/show_bug.cgi?id=77
There is a lengthy discussion regarding this topic with the instructions on
how to resolve this (this is a "too new tool version" issue).
Also you can try to search through user and dev mailing lists, January and
February, though that will just duplicate what you'll be able to gather from
bug#77.
George
On Friday 15 March 2002 07:31, you wrote:
> I posted this to the users list but thought it might be more appropriate
> here... (either that or if there is a more appropriate area let me
> know).
>
> I tried emerging GnuCash today. A friend of mine wanted to see if it was
> better than Quicken. I have no idea. Anyway everything seemed to go okay
> and then when I ran the actual program I got this:
>
> $ gnucash
> ERROR: In procedure dynamic-link:
> ERROR: file: "libgw-runtime", message: "file not found"
>
> Some deprecated features have been used. Set the environment
> variable GUILE_WARN_DEPRECATED to "detailed" and rerun the
> program to get more information. Set it to "no" to suppress
> this message.
>
> $ export GUILE_WARN_DEPRECATED="detailed"
> $ gnucash
> `scm_sysintern' is deprecated. Use `scm_define' instead.
> ERROR: In procedure dynamic-link:
> ERROR: file: "libgw-runtime", message: "file not found"
>
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev
prev parent reply other threads:[~2002-03-15 19:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-15 15:31 [gentoo-dev] GnuCash error Joshua Hansen
2002-03-15 19:46 ` George Shapovalov [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200203151941.LAA27032@chamber.cco.caltech.edu \
--to=georges@its.caltech.edu \
--cc=gentoo-dev@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox