[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: UPDATE: net/irssi-0.8.10
- To: ports_(_at_)_openbsd_(_dot_)_org
- Subject: Re: UPDATE: net/irssi-0.8.10
- From: viq <viq_(_at_)_poczta_(_dot_)_fm>
- Date: Sun, 12 Mar 2006 21:12:54 +0100
On Sunday 12 March 2006 10:11, steven mestdagh wrote:
> viq [2006-03-12, 07:15:13]:
> > > configure spits some warning about grep usage here.
> >
> > Yeah, I saw those too, no clue yet though as to why they happen and what
> > to do about it...
> >
> > > maybe you want to install the irssi.conf file?
> >
> > Ah, yes, will have to look into that.
>
> install it under share/examples/irssi and then add a @sample line below
> in PLIST. there already are a few @sample lines there.
I think that is already done, will look into that now though, expect a new
patch soon, incorporating also other suggestions.
As for that error, that's when "checking if we can link dynamic libraries with
modules", that's between tests for GLIB2 and ncurses in config file. So most
likely that would be grep in line 25381 - but I have no idea how to deal with
that.
> > > on startup i see
> > > (process:16536): GLib-CRITICAL **: g_strcasecmp: assertion `s2 != NULL'
> > > failed
> >
> > Argh, again? That was the main thing i was trying to get rid of, that's
> > why patch-src_fe-common_core_fe-common-core_c is there.
> > And strange, I wipe my ~/.irssi and start it, and don't get that error...
> > When you get that error, what does "/set term_charset" tell you?
>
> I see, yes apparently I had an old .irssi directory, I removed it and
> the error is gone. term_charset was 646, now it is ISO8859-1.
Yes, that's what we were fighting with before. Though, hmm, if you have a
config, I would assume you should have a correct charset in there... Strange.
> steven
--
viq
-------------------------------------------------------------------
Wzial udzial w zawodach balonowych i... niezle wypadl!
KIM JEST STEFAN?!? | http://www.stefan.pl/
Visit your host, monkey.org