Irssi

stephenw10

Are you running 64bit?

Steve

rizzler

@stephenw10:

Are you running 64bit?

Steve

ye, running AMD64 om a Dual core processor.

ptt

Then you need to install:


pkg_add -r ftp://ftp-archive.freebsd.org/pub/FreeBSD-Archive/ports/amd64/packages-8.1-release/All/irssi-0.8.15_2.tbz

stephenw10

You probably want to remove the wrong version first.

pkg_delete irssi

Not 100% on the syntax there! ::)

Steve

ptt

Yes, first remove the non working package, then install the Good one ;)

If im not wrong, must bee something like:


pkg_delete irssi-0.8.15_2

rizzler

now i got the following error :/

/libexec/ld-elf.so.1: /usr/local/lib/perl5/5.10.1/mach/CORE/libperl.so: unsupported file layout

stephenw10

Has it correctly installed that perl library?
If it has I'd say there's a good chance that it didn't uninstall the 64bit version of perl correctly.

What do you have listed if you run: pkg_info

Steve

marcelloc

you may need to uninstall all irssi depenecies that was installed i386 verson on x64

this is dependecies listed in freebsd ports:

A modular IRC client with many features
Long description : Sources : Changes : Download
Maintained by: vanilla@FreeBSD.org
Requires: gettext-0.18.1.1, glib-2.28.8_3, gmake-3.82, libiconv-1.13.1_1, pcre-8.21, perl-5.12.4_3, pkg-config-0.25_1, python27-2.7.2_3

rizzler

I tryed to remove both python and glib then irssi and reinstalled it, irssi installed python and glib now but i still get this error :/

/libexec/ld-elf.so.1: /usr/local/lib/perl5/5.10.1/mach/CORE/libperl.so: unsupported file layout

pkg_info
glib-2.24.1_1 Some useful routines of C programming (current stable versi
irssi-0.8.15_2 A modular IRC client with many features
python26-2.6.5 An interpreted object-oriented programming language

marcelloc

try with 8.2 packages, maybe it will work.

but please, test on a non production server.

rizzler

after reinstalling glib-2.28.8_3, gmake-3.82 it now works, thank you guys so very much for the help, it's really appriciated :)

stephenw10

Nice one!
Could have saved some time if I'd thought you may have been running 64bit in the first place! ::)
Actually I'm quite surprised it doesn't have some checks in the package sysetem to stop this happening. Lesson learned.

Steve