Date: Thu, 27 Dec 2007 21:46:43 +0000 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: Giorgos Keramidas <keramida@ceid.upatras.gr> Cc: Gary Kline <kline@tao.thought.org>, freebsd-questions@freebsd.org Subject: Re: mutt?? Message-ID: <47741D43.4010603@infracaninophile.co.uk> In-Reply-To: <20071227204900.GD11961@kobe.laptop> References: <200712271902.lBRJ20FN003473@tao.thought.org> <20071227204900.GD11961@kobe.laptop>
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Giorgos Keramidas wrote: > On 2007-12-27 11:02, Gary Kline <kline@tao.thought.org> wrote: >> I've been trtryinng to rebuild everything on tao to get my i810 >> graphics working. Somehow, mutt bbroke. It seems to break with >> something undefined in perl5.8. >> >> Anybody know what this is: >> Undefined symbol "__sbmaskrune" ? > > That's odd. The mutt-devel port (which I am using to type and post this > message) does not seem to depend on Perl: > > % $ pkg_info -r mutt\* > % Information for mutt-devel-... > % > % Depends on: > % Dependency: ispell-3.2.06_18 > % Dependency: mime-support-3.39.1 > % Dependency: libiconv-1.11_1 > % Dependency: gettext-0.16.1_3 > % > % $ This is caused by a change to various ctype functions to do with improved UTF8 support recently, which inadvertently broke ABI compatability on RELENG_6. The change has since been reverted, but it seems that you were unlucky enough to install or upgrade some software during the month or so that it was in place, so that it is referring to symbols that do not exist in libc.so. Perl is just one of the places where __sbmaskrune can show up. There's been quite a lot of discussion of it on various lists recently: http://www.google.co.uk/search?hl=en&q=site%3Alists.freebsd.org+__sbmaskrune&btnG=Google+Search&meta= This, precisely, is the commit message where the ABI breakage you've seen was created: http://lists.freebsd.org/pipermail/cvs-src/2007-October/082836.html and here is where it was fixed: http://lists.freebsd.org/pipermail/cvs-src/2007-November/084046.html To sort out your system, basically make sure you're running a RELENG_6 version from after the fix was committed, and then I'm afraid you've just got to reinstall any software that shows the symptoms. Anything installed before the original commit that broke things will be fine -- it's just software that was recompiled using a RELENG_6 system from between 24 October and 20 November. It's only RELENG_6 that was affected -- the change went into RELENG_7 (and HEAD) where ABI changes are permitted with the new major version number, but RELENG_6_2, RELENG_6_3 and other release branches never had this patch applied. Cheers, Matthew - -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHdB1D8Mjk52CukIwRCMNSAJ0XiL1xfFz925+P+WVpmqRmG7AJTgCdGNkG APZBRHJq66NqxUScOJrjd8k= =JqqZ -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?47741D43.4010603>