From owner-freebsd-ports@FreeBSD.ORG Wed Jan 11 15:36:06 2012 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 84DAA106566B for ; Wed, 11 Jan 2012 15:36:06 +0000 (UTC) (envelope-from cvs-src@yandex.ru) Received: from forward15.mail.yandex.net (forward15.mail.yandex.net [IPv6:2a02:6b8:0:801::5]) by mx1.freebsd.org (Postfix) with ESMTP id F0E608FC08 for ; Wed, 11 Jan 2012 15:36:05 +0000 (UTC) Received: from smtp11.mail.yandex.net (smtp11.mail.yandex.net [95.108.130.67]) by forward15.mail.yandex.net (Yandex) with ESMTP id 593EB9E0FC2; Wed, 11 Jan 2012 19:36:04 +0400 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1326296164; bh=WVHPKCyYbGB5EFH17Hn/6RUc9CEm0QFQoqCL6259KJI=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=IAgzdjBxWsMJprcIcuJh0hwacpDg+6X/tc1wtI6nxyLdbUHJUr9wwmnGQasXzmLKB pPH31sa9gp/tjl2lzMJtBSUlLo86M839UwmLMbGFmeS2S7RGe5NjwbqxJjau03lq8T m1/rQQZ3yO2tOafdEd7q8dKAw7PTODFI3ROVtZ4A= Received: from smtp11.mail.yandex.net (localhost [127.0.0.1]) by smtp11.mail.yandex.net (Yandex) with ESMTP id 324E77E033D; Wed, 11 Jan 2012 19:36:04 +0400 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1326296164; bh=WVHPKCyYbGB5EFH17Hn/6RUc9CEm0QFQoqCL6259KJI=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=IAgzdjBxWsMJprcIcuJh0hwacpDg+6X/tc1wtI6nxyLdbUHJUr9wwmnGQasXzmLKB pPH31sa9gp/tjl2lzMJtBSUlLo86M839UwmLMbGFmeS2S7RGe5NjwbqxJjau03lq8T m1/rQQZ3yO2tOafdEd7q8dKAw7PTODFI3ROVtZ4A= Received: from unknown (unknown [213.27.65.65]) by smtp11.mail.yandex.net (nwsmtp/Yandex) with ESMTP id a2V8a2vf-a3ViB2NQ; Wed, 11 Jan 2012 19:36:04 +0400 X-Yandex-Spam: 1 Message-ID: <4F0DAC40.3030109@yandex.ru> Date: Wed, 11 Jan 2012 19:35:28 +0400 From: Ruslan Mahmatkhanov User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:9.0) Gecko/20111229 Thunderbird/9.0 MIME-Version: 1.0 To: Jan Beich References: <4F0B36BD.8070202@yandex.ru> <1RkOJ1-000AFf-3x@internal.tormail.net> <4F0BAC0C.3050006@yandex.ru> <1RkdhS-00096n-DR@internal.tormail.net> In-Reply-To: <1RkdhS-00096n-DR@internal.tormail.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Ports Mailing List Subject: Re: Perl symlinks question 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: Wed, 11 Jan 2012 15:36:06 -0000 Jan Beich wrote on 10.01.2012 19:33: > Ruslan Mahmatkhanov writes: > >>> Ruslan Mahmatkhanov writes: >>> >>>> There is PR: http://bugs.freebsd.org/163687 >>>> It tries to fix port building when user built it's perl installation >>>> with USE_PERL option (creating symlinks in /usr/bin) set to off (not >>>> the default). Patch in PR just replaces static shebang with ${PERL} >>>> variable from Mk/bsd.perl.mk. But it doesn't actually fix the build, >>>> because consequent call of aclocal-1.11 will fail since it's shebang >>>> set to '/usr/bin/perl' too. >>> [...] >>> >>> Can you shed more light on the aclocal issue? Does the submitter know? >>> nss_ldap installs fine after applying ports/163687. >>> >>> $ ls -1d /usr/local/share/aclocal* >>> /usr/local/share/aclocal/ >>> /usr/local/share/aclocal-1.11/ >>> /usr/local/share/aclocal-1.4/ >>> $ fgrep -r /usr/bin/perl /usr/local/share/aclocal* >>> Exit 1 >> >> Sure. >> ===> Configuring for nss_ldap-1.265_7 >> env: /usr/local/bin/aclocal-1.11: No such file or directory >> *** Error code 127 >> >> [rm@smeshariki3 ~/learn]> head -3 `which aclocal-1.11` >> #!/usr/bin/perl -w >> # -*- perl -*- >> # Generated from aclocal.in; do not edit by hand. > > This line tells enough. aclocal used @PERL@ binary detected during > devel/automake installation. Have you tried to reinstall dependent > ports after turning off USE_PERL option? You are quite right. I just built it in clean environment and was able to reproduce the breakage, described in original PR. And the patch works as expected. I just committed this. Thanks. Since i don't saw strong objections about making this symlinks non-conditional (as we already know, it will not harm read-only LOCALBASE users), i'll come with PR's later. -- Regards, Ruslan Tinderboxing kills... the drives.