From owner-freebsd-stable Sat May 12 14:20:48 2001 Delivered-To: freebsd-stable@freebsd.org Received: from vimfuego.saarinen.org (saarinen.org [203.79.82.14]) by hub.freebsd.org (Postfix) with ESMTP id EFFA537B446 for ; Sat, 12 May 2001 14:20:45 -0700 (PDT) (envelope-from juha@saarinen.org) Received: from vimfuego.saarinen.org ([192.168.1.1]) by vimfuego.saarinen.org with esmtp (Exim 3.22 #1 (Red Hack)) id 14ygfO-0000nv-00; Sun, 13 May 2001 09:11:10 +1200 Date: Sun, 13 May 2001 09:11:10 +1200 (NZST) From: Juha Saarinen To: Sheldon Hearn Cc: Eriya Akasaka , "freebsd-stable@freebsd.org" Subject: Re: Exim stops working in 4.3-STABLE because of Perl problems? In-Reply-To: <89456.989676346@axl.fw.uunet.co.za> Message-ID: X-S: Always MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 12 May 2001, Sheldon Hearn wrote: > I've had horrible luck with Perl threads, but I've never lookde into it > seriously. > > By the way, ports are generally supposed to survive an upgrade, as long > as you don't blow away old libraries. However, applications that link > against Perl should, in my opinion, always be rebuilt and linked against > the new Perl libraries after an upgrade. > > For example, I had similar nasties with nvi linked against Perl in an > upgrade from 4.2-STABLE to 5.0-CURRENT recently. > I tried building some of the ports Eriya mentioned (im and inn) on a 4.3-STABLE box with Perl threads enabled, and of course they work fine. Exim's the only port (well, I tried compiling Exim from source as well -- same result) that breaks. Not at all sure that this is because of Perl threads. -- Regards, Juha PGP fingerprint: B7E1 CC52 5FCA 9756 B502 10C8 4CD8 B066 12F3 9544 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message