From owner-freebsd-ports Thu Oct 10 21:47:50 1996 Return-Path: owner-ports Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA16029 for ports-outgoing; Thu, 10 Oct 1996 21:47:50 -0700 (PDT) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA16024; Thu, 10 Oct 1996 21:47:48 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by who.cdrom.com (8.7.5/8.6.11) with ESMTP id VAA13469 ; Thu, 10 Oct 1996 21:47:47 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.7.6/8.7.3) with ESMTP id VAA01680; Thu, 10 Oct 1996 21:46:16 -0700 (PDT) Message-Id: <199610110446.VAA01680@austin.polstra.com> To: James FitzGibbon cc: asami@FreeBSD.ORG, ports@FreeBSD.ORG Subject: Re: cvs commit: ports/lang/msqlperl - Imported sources In-reply-to: Your message of "Thu, 10 Oct 1996 22:56:00 EDT." Date: Thu, 10 Oct 1996 21:46:16 -0700 From: John Polstra Sender: owner-ports@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > This message is usually (probably always) caused by failing to specify > > "-fpic" when building one or more of the object files making up the > > shared library. > > Makes sense, except that at the moment, the msql port only installs the > static library. Are the symptoms the same ? The command that caused the error messages was this: LD_RUN_PATH="/usr/local/Minerva/lib" ld -o ./blib/arch/auto/Msql/Msql.so \ -Bshareable -L/usr/local/lib Msql.o -L/usr/local/Minerva/lib -lmsql You're saying that the "-lmsql" library is a static library? Oh, yes, I see that it is, since the error messages refer to "libmsql.a". So that is the problem, all right. One solution would be to modify the msql port so that it also installs a shared "msql" library. All the object files in that would have to be built with "-fpic". Or, it could just build the current libmsql.a library using object files compiled with "-fpic". But that would needlessly reduce the performance of other programs that statically link with the library. Probably the best solution is to build and install both static and shared versions of the msql library. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth