Date: Fri, 24 Apr 2015 10:24:55 +0200 From: Andrea Venturoli <ml@netfence.it> To: Michael Schuster <michaelsprivate@gmail.com> Cc: questions <questions@freebsd.org> Subject: Re: Bacula and perl 5.20 Message-ID: <5539FDD7.8000604@netfence.it> In-Reply-To: <CADqw_gLNQ%2Brm3zRNJEROE260SN8Tb6MuzfaOsaZoQkyn=oiU_Q@mail.gmail.com> References: <5538919D.8060507@netfence.it> <CADqw_g%2BryZrFG7JFEKLHkDsOWY-ZOy5wKRba%2Bb6e9AcgebuEig@mail.gmail.com> <553893FE.8090601@netfence.it> <CADqw_gLNQ%2Brm3zRNJEROE260SN8Tb6MuzfaOsaZoQkyn=oiU_Q@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 04/24/15 07:00, Michael Schuster wrote: > Running "env perl" from the command line seems to work however. > > > what does that mean in detail? It means that "perl" is run. > what does "which perl" print out? On system with perl 5.16/5.18 and USE_PERL=YES, it will print "/usr/bin/perl". On system with perl 5.20 or 5.16/5.18 with USE_PERL=NO, it will print "/usr/local/bin/perl". Bacula, as most ports, starts with no /usr/local/bin in PATH, so "env perl" (from its scripts) won't work. bye & Thanks av.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5539FDD7.8000604>