From: jh@chabran.fr (Jean-Hadrien CHABRAN)
Subject: [sup-talk] startup crash
Date: Sun, 9 Mar 2008 15:45:34 +0100 [thread overview]
Message-ID: <345330030803090745p1f0c6a14if40f95da893c07c0@mail.gmail.com> (raw)
In-Reply-To: <345330030803090628u2ac33bfcn3b8ab30da6b16be3@mail.gmail.com>
I just solved the problem on my FreeBSD 6.3, by installing
ruby18-iconv-1.8.6.111,1.
On my gentoo boxes, iconv seems to be correctly installed
/usr/lib64/ruby/1.8/x86_64-linux/iconv.so, but this is now a
distribution issue.
But I'm still curious, why this dependency problem is showing itself
in a such odd way ?
On 3/9/08, Jean-Hadrien CHABRAN <jh at chabran.fr> wrote:
> Hello,
>
> I just discovered sup, and I wanted to give it a try, but sup-config /
> sup crash on startup, without any useful informations ( for me ) to
> discover why.
---- 8< --- 8< -------------------------------------------------------------------
>
--
Jean-Hadrien Chabran
Maitre-Oeuvre SEP EFREI
Reponsable Tutorat-L
next prev parent reply other threads:[~2008-03-09 14:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-09 13:28 Jean-Hadrien CHABRAN
2008-03-09 14:45 ` Jean-Hadrien CHABRAN [this message]
2008-03-09 17:44 ` William Morgan
[not found] <20080310134823.GA24401@lenin>
2008-03-10 14:01 ` Mack, Daemian
2008-03-10 17:12 ` William Morgan
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=345330030803090745p1f0c6a14if40f95da893c07c0@mail.gmail.com \
--to=jh@chabran.fr \
/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