From: George Shapovalov <georges@its.caltech.edu>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] gnucash not running
Date: Thu, 28 Feb 2002 11:06:42 -0800 [thread overview]
Message-ID: <200202281855.KAA15449@chamber.cco.caltech.edu> (raw)
In-Reply-To: <1014899640.17756.1.camel@loki.rdrtech.net>
This issue came up on both gentoo-dev and gentoo-user lists about a month
ago. I has been resolved, you can find resolution reports in both mailing
lists and also on a bugzilla, bug 77, as I remember (or just search for
gnucash). Apparently this is a "too new utility version" syndrom. I just
chacked, bugzilla contains a good discussion of what changes to a few ebuild
files helped people.
George
On Thursday 28 February 2002 04:33, you wrote:
> I just tried to install GNUCash on my gentoo box, and I'm getting this
> message...
>
> rreich@loki:~$ 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.
> rreich@loki:~$ export GUILE_WARN_DEPRECATED="detailed"
> rreich@loki:~$ gnucash
> `scm_sysintern' is deprecated. Use `scm_define' instead.
> ERROR: In procedure dynamic-link:
> ERROR: file: "libgw-runtime", message: "file not found"
> rreich@loki:~$
>
>
> Has anybody run into this? Is there a way to fix it?
>
> Thanks
> Richard Reich
>
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev
next prev parent reply other threads:[~2002-02-28 18:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-28 12:33 [gentoo-dev] gnucash not running Richard Reich
2002-02-28 19:06 ` George Shapovalov [this message]
2002-03-04 16:30 ` Richard Reich
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=200202281855.KAA15449@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