Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id CB7AF476CF7 for ; Thu, 2 Jan 2003 15:36:31 -0500 (EST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id 1A91A476DFD for ; Thu, 2 Jan 2003 15:27:38 -0500 (EST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.6/8.12.6) with ESMTP id h02KRW0U003598; Thu, 2 Jan 2003 15:27:32 -0500 (EST) To: Palle Girgensohn Cc: pgsql-interfaces@postgresql.org Subject: Re: Building PL/Perl without libperl.so fails In-reply-to: <94260000.1041257007@palle.girgensohn.se> References: <94260000.1041257007@palle.girgensohn.se> Comments: In-reply-to Palle Girgensohn message dated "Mon, 30 Dec 2002 15:03:27 +0100" Date: Thu, 02 Jan 2003 15:27:31 -0500 Message-ID: <3597.1041539251@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200301/12 X-Sequence-Number: 3512 Palle Girgensohn writes: > I'd rather link libplperl with a static libperl.a than adding a shared > libperl.so to the perl port. Can this be done, or will something break? It will not work unless your platform is one where PIC code generation is the default, so that the contents of libperl.a are amenable to inclusion into a .so library. regards, tom lane