From owner-freebsd-ports@FreeBSD.ORG Tue Jul 24 17:03:50 2007 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1FC1916A417 for ; Tue, 24 Jul 2007 17:03:50 +0000 (UTC) (envelope-from pauls@utdallas.edu) Received: from smtp3.utdallas.edu (smtp3.utdallas.edu [129.110.10.49]) by mx1.freebsd.org (Postfix) with ESMTP id E5AA513C46C for ; Tue, 24 Jul 2007 17:03:49 +0000 (UTC) (envelope-from pauls@utdallas.edu) Received: from utd59514.utdallas.edu (utd59514.utdallas.edu [129.110.3.28]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp3.utdallas.edu (Postfix) with ESMTP id 36250654F2; Tue, 24 Jul 2007 12:03:49 -0500 (CDT) Date: Tue, 24 Jul 2007 12:03:48 -0500 From: Paul Schmehl To: Anton Berezin Message-ID: <94D0B4C06F1B6E62AF90AEED@utd59514.utdallas.edu> In-Reply-To: <20070724161616.GA42493@heechee.tobez.org> References: <20070724095718.GB68140@heechee.tobez.org> <1B50EA71ECD75693D12CE9D3@utd59514.utdallas.edu> <20070724142514.GA4315@heechee.tobez.org> <69DD0E3AC68E2AEC7C876B4C@utd59514.utdallas.edu> <20070724161616.GA42493@heechee.tobez.org> X-Mailer: Mulberry/4.0.6 (Linux/x86) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=sha1; protocol="application/pkcs7-signature"; boundary="==========DDC53026EEA6D5CAA34F==========" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: FreeBSD Ports Subject: Re: How to include new dirs in @INC 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: Tue, 24 Jul 2007 17:03:50 -0000 --==========DDC53026EEA6D5CAA34F========== Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline --On Tuesday, July 24, 2007 18:16:16 +0200 Anton Berezin =20 wrote: > > Right. I assume that the port you are creating uses "normal" Makefile.PL > for a part of the configuration process, while not being the main > configuration mechanism (that is, the port does not define PERL_CONFIGURE > in its skeleton). > Yes, but it also uses GNU_CONFIGURE for the main parts of the port. So, in = the Makefile, I have: GNU_CONFIGURE=3D Yes USE_PERL=3D Yes Is it possible to use both GNU_CONFIGURE *and* PERL_CONFIGURE? Because the = port needs to compile not just the perl scripts but a great deal of C code=20 as well. > In bsd.port.mk, there is a special handling of the ports that do define > PERL_CONFIGURE to make them PREFIX-clean. Unfortunately, this handling = is > not kicking in for special cases such as yours. > > The relevant lines from bsd.port.mk: > > .if defined(PERL_CONFIGURE) > CONFIGURE_ARGS+=3D CC=3D"${CC}" CCFLAGS=3D"${CFLAGS}" = PREFIX=3D"${TARGETDIR}" \ > INSTALLPRIVLIB=3D"${TARGETDIR}/lib" = INSTALLARCHLIB=3D"${TARGETDIR}/lib" > ..... > > So, if you can duplicate the setting of INSTALLPRIVLIB and INSTALLARCHLIB > wherever "perl Makefile.PL" is run during configuration process of your > port, this should make Perl modules installed by the port PREFIX-clean. > > If Build.PL is used instead, there is a similar way which you can look up > in bsd.port.mk yourself. > I'll poke around. I was unsure if I could use both GNU_CONFIGURE *and*=20 PERL_CONFIGURE in the same port. That's why I didn't use PERL_CONFIGURE.=20 Maybe I could pre-build the perl parts? This is a very complex port. I've = spent untold hours getting it working. If I can get the perl part working=20 right, then I can eliminate the pkg-deinstall script, but I'm not sure it's = worth the effort. --=20 Paul Schmehl (pauls@utdallas.edu) Senior Information Security Analyst The University of Texas at Dallas http://www.utdallas.edu/ir/security/ --==========DDC53026EEA6D5CAA34F==========--