Perl symlinks question
Ruslan Mahmatkhanov
cvs-src at yandex.ru
Wed Jan 11 15:36:06 UTC 2012
Jan Beich wrote on 10.01.2012 19:33:
> Ruslan Mahmatkhanov<cvs-src at yandex.ru> writes:
>
>>> Ruslan Mahmatkhanov<cvs-src at yandex.ru> 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 at 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.
More information about the freebsd-ports
mailing list