Perl symlinks question

Ruslan Mahmatkhanov cvs-src at
Tue Jan 10 03:10:45 UTC 2012

Jan Beich wrote on 10.01.2012 03:06:
> Ruslan Mahmatkhanov<cvs-src at>  writes:
>> There is PR:
>> 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/ 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

===>  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; do not edit by hand.

Submitter doesn't seems know about (or didn't faced this).


Tinderboxing kills... the drives.

More information about the freebsd-ports mailing list