From owner-freebsd-ports@FreeBSD.ORG Fri Feb 11 23:35:57 2005 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1E45716A4CE for ; Fri, 11 Feb 2005 23:35:57 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id ACF9043D45 for ; Fri, 11 Feb 2005 23:35:56 +0000 (GMT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id j1BNZjFp016125; Fri, 11 Feb 2005 18:35:45 -0500 (EST) To: Sven Willenberger In-reply-to: <1108163489.10860.49.camel@lanshark.dmv.com> References: <1108135462.10866.12.camel@lanshark.dmv.com> <510442EEF15A0237A0138D49@rambutan.pingpong.net> <1108138215.10866.20.camel@lanshark.dmv.com> <20050211203503.GA79170@heechee.tobez.org> <1108158115.10863.40.camel@lanshark.dmv.com> <20050211220935.GB79170@heechee.tobez.org> <20050211222002.GC79170@heechee.tobez.org> <1108163489.10860.49.camel@lanshark.dmv.com> Comments: In-reply-to Sven Willenberger message dated "Fri, 11 Feb 2005 18:11:29 -0500" Date: Fri, 11 Feb 2005 18:35:45 -0500 Message-ID: <16124.1108164945@sss.pgh.pa.us> From: Tom Lane cc: Palle Girgensohn cc: pgsql-general@postgresql.org cc: freebsd-ports@freebsd.org cc: Anton Berezin Subject: Re: [GENERAL] databases/p5-postgresql-plperl links to wrong libperl.so X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Feb 2005 23:35:57 -0000 Sven Willenberger writes: > it looks like the sed line is stripping out pgac_tmp2 from the pgac_tmp1 > leaving the system to use the default perl libperl.so. > when I modified perl_embed_ldflags to not remove the -R line, the > compile works and links to the proper libperl.so It worked for you, but not necessarily for other people. This thread may be instructive: http://archives.postgresql.org/pgsql-bugs/2004-11/msg00181.php regards, tom lane