intool for owncloud

[Kevin Oberman]

On Tue, Mar 19, 2013 at 3:21 AM, Javier Cepa Iglesias <
javier_cepa at optenet.com> wrote:

> ===>   owncloud-4.5.7 depends on executable: mp3info - not found
> ===>    Verifying install for mp3info in /usr/ports/audio/mp3info
> ===>   mp3info-gtk-0.8.5 depends on file: /usr/local/bin/intltool-**extract
> - not found
> ===>    Verifying install for /usr/local/bin/intltool-**extract in
> /usr/ports/textproc/intltool
> ===>   intltool-0.41.1 depends on package: p5-XML-Parser>=0 - found
> ===>   intltool-0.41.1 depends on executable: gmake - found
> ===>   intltool-0.41.1 depends on file: /usr/local/bin/perl5.8.9 - found
> ===>   intltool-0.41.1 depends on shared library: iconv.3 - found
> ===>  Configuring for intltool-0.41.1
> checking for a BSD-compatible install... /usr/bin/install -c -o root -g
> wheel
> checking whether build environment is sane... yes
> checking for a thread-safe mkdir -p... ./install-sh -c -d
> checking for gawk... no
> checking for mawk... no
> checking for nawk... nawk
> checking whether gmake sets $(MAKE)... yes
> checking for perl... /usr/bin/perl
> checking for perl >= 5.8.1... configure: error: perl 5.8.1 is required for
> intltool
> ===>  Script "configure" failed unexpectedly.
> Please report the problem to gnome at FreeBSD.org [maintainer] and attach the
> "/usr/ports/textproc/intltool/**work/intltool-0.41.1/config.**log"
> including the
> output of the failure of your make command. Also, it might be a good idea
> to
> provide an overview of all packages installed on your system (e.g. a
> /usr/sbin/pkg_info -Ea).
> *** [do-configure] Error code 1
>
> Stop in /usr/ports/textproc/intltool.
> *** [build-depends] Error code 1
>
> Stop in /usr/ports/audio/mp3info.
> *** [install] Error code 1
>
> Stop in /usr/ports/audio/mp3info.
> *** [build-depends] Error code 1
>

Is it safe to assume that you DO have perl (of at least 5.8.1) installed?

Also, you need to follow the instructions included in the message you sent
for anyone to make much of a guess as to what went wrong. The config.log is
especially important for this sort of error.
-- 
R. Kevin Oberman, Network Engineer
E-mail: rkoberman at gmail.com