From owner-freebsd-ports@FreeBSD.ORG Sat Mar 1 19:46:33 2008 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C1AC01065670; Sat, 1 Mar 2008 19:46:33 +0000 (UTC) (envelope-from shurd@sasktel.net) Received: from misav09.sasknet.sk.ca (misav09.sasknet.sk.ca [142.165.20.173]) by mx1.freebsd.org (Postfix) with ESMTP id 4DE038FC2C; Sat, 1 Mar 2008 19:46:33 +0000 (UTC) (envelope-from shurd@sasktel.net) Received: from bgmpomr2.sasknet.sk.ca ([142.165.72.23]) by misav09 with InterScan Messaging Security Suite; Sat, 01 Mar 2008 13:16:31 -0600 Received: from server.hurd.local (adsl-76-202-204-46.dsl.lsan03.sbcglobal.net [76.202.204.46]) by bgmpomr2.sasknet.sk.ca (SaskTel eMessaging Service) with ESMTPA id <0JX200ELEG7IHB40@bgmpomr2.sasknet.sk.ca>; Sat, 01 Mar 2008 13:16:31 -0600 (CST) Date: Sat, 01 Mar 2008 11:16:29 -0800 From: Stephen Hurd In-reply-to: <47C95FBC.1030907@FreeBSD.org> To: Kris Kennaway Message-id: <47C9AB8D.3020608@sasktel.net> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT References: <00ab01c87b64$29c7b8c0$b6db87d4@multiplay.co.uk> <47C95FBC.1030907@FreeBSD.org> User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8.1.9) Gecko/20071123 SeaMonkey/1.1.6 Cc: ports@freebsd.org, stable@FreeBSD.org, Steven Hartland Subject: Re: portupgrade, recommended by 7 release notes, breaks perl X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Mar 2008 19:46:33 -0000 Kris Kennaway wrote: > I think something is not quite right in your analysis, because perl > does not depend on any external perl modules (it cannot, by definition). I ran into something like this when I was switching from a threaded perl to an unthreaded perl. It wasn't possible to just use a portupgrade to rebuild and reinstall all the packages, I needed to uninstall a large number of them. Basically, every time the port build fell over, I would need to pkg_which the shared object mentioned in the error message, uninstall that package and take note of the name then reinstall them all after everything else worked. I've never encountered this as a result of a version upgrade though. Reproducing the problem is pretty simple... build a threaded perl, then build a bunch of modules that use shared objects, then reconfigure perl to be unthreaded and force upgrade it. The shared objects will fail to load and portupgrade of the modules will fall over. I never reported this as a problem though since it was pretty obvious why it happened and how to fix it. It was my own fault for playing with a threaded perl then wanting to change back.