Date: Sat, 17 Nov 2012 21:18:03 +0100 From: Koop Mast <kwm@rainbow-runner.nl> To: Kevin Oberman <kob6558@gmail.com> Cc: gnome@freebsd.org, martymac@freebsd.org, lr101fc@yahoo.co.uk Subject: Re: grsync and intltool after cvsup port build error an FreeBSD-8.2-releng-p10 Message-ID: <50A7F0FB.5080108@rainbow-runner.nl> In-Reply-To: <CAN6yY1vvXbO2HOPNuAWR5y2pDPvUX23tNUqNz0OLzZ_mcVR1Vw@mail.gmail.com> References: <20121117161013.41caeb25@smtp.mail.yahoo.co.uk> <CAN6yY1vvXbO2HOPNuAWR5y2pDPvUX23tNUqNz0OLzZ_mcVR1Vw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 17-11-2012 21:01, Kevin Oberman wrote: > On Sat, Nov 17, 2012 at 7:10 AM, Hanno K <lr101fc@yahoo.co.uk> wrote: >> Hi there, >> >> grsync and intltool - after cvsup port build error an FreeBSD-8.2-releng-p10 >> by the way the port coreutils is running a similar link error, but I don't know if it is in any way related to the >> other two ports. >> >> my pkg_info.txt is attached. >> >> ----------------------- >> >> env UPGRADE_TOOL=portupgrade UPGRADE_PORT=intltool-0.41.1 UPGRADE_PORT_VER=0.41.1 make clean >> ===> Cleaning for intltool-0.41.1 >> env UPGRADE_TOOL=portupgrade UPGRADE_PORT=intltool-0.41.1 UPGRADE_PORT_VER=0.41.1 make >> ===> intltool-0.41.1 depends on file: /usr/local/sbin/pkg - found >> ===> Extracting for intltool-0.41.1 >> => SHA256 Checksum OK for gnome/intltool-0.41.1.tar.gz. >> ===> intltool-0.41.1 depends on file: /usr/local/bin/perl5.16.2 - found >> ===> Patching for intltool-0.41.1 >> ===> intltool-0.41.1 depends on file: /usr/local/bin/perl5.16.2 - found >> ===> 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.16.2 - 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... /usr/local/bin/gmkdir -p >> checking for gawk... gawk >> checking whether gmake sets $(MAKE)... yes >> checking for perl... /usr/local/bin/perl >> checking for perl >= 5.8.1... 5.16.2 >> checking for XML::Parser... configure: error: XML::Parser perl module is required for intltool >> ===> Script "configure" failed unexpectedly. >> Please report the problem to gnome@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/local/sbin/pkg info -g -Ea). >> *** Error code 1 >> >> Stop in /usr/ports/textproc/intltool. >> >> -------------------------------------------------------------------- >> >> env UPGRADE_TOOL=portupgrade UPGRADE_PORT=grsync-1.2.1_1 UPGRADE_PORT_VER=1.2.1_1 make clean >> ===> Cleaning for grsync-1.2.2 >> env UPGRADE_TOOL=portupgrade UPGRADE_PORT=grsync-1.2.1_1 UPGRADE_PORT_VER=1.2.1_1 make >> ===> License GPLv2 accepted by the user >> ===> grsync-1.2.2 depends on file: /usr/local/sbin/pkg - found >> ===> Extracting for grsync-1.2.2 >> => SHA256 Checksum OK for grsync-1.2.2.tar.gz. >> ===> Patching for grsync-1.2.2 >> ===> Applying FreeBSD patches for grsync-1.2.2 >> ===> grsync-1.2.2 depends on executable: gmake - found >> ===> grsync-1.2.2 depends on file: /usr/local/bin/intltool-extract - found >> ===> grsync-1.2.2 depends on executable: pkgconf - found >> ===> grsync-1.2.2 depends on executable: update-desktop-database - found >> ===> grsync-1.2.2 depends on executable: gtk-update-icon-cache - found >> ===> grsync-1.2.2 depends on shared library: atk-1.0.0 - found >> ===> grsync-1.2.2 depends on shared library: gdk_pixbuf-2.0.0 - found >> ===> grsync-1.2.2 depends on shared library: glib-2.0.0 - found >> ===> grsync-1.2.2 depends on shared library: gtk-x11-2.0.0 - found >> ===> grsync-1.2.2 depends on shared library: pango-1.0.0 - found >> ===> Configuring for grsync-1.2.2 >> 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... /usr/local/bin/gmkdir -p >> checking for gawk... gawk >> checking whether gmake sets $(MAKE)... yes >> checking whether to enable maintainer-specific portions of Makefiles... no >> checking for style of include used by gmake... GNU >> checking for gcc... cc >> checking whether the C compiler works... yes >> checking for C compiler default output file name... a.out >> checking for suffix of executables... >> checking whether we are cross compiling... no >> checking for suffix of object files... o >> checking whether we are using the GNU C compiler... yes >> checking whether cc accepts -g... yes >> checking for cc option to accept ISO C89... none needed >> checking dependency style of cc... gcc3 >> checking how to run the C preprocessor... cpp >> checking for grep that handles long lines and -e... /usr/bin/grep >> checking for egrep... /usr/bin/grep -E >> checking for ANSI C header files... yes >> checking for sys/types.h... yes >> checking for sys/stat.h... yes >> checking for stdlib.h... yes >> checking for string.h... yes >> checking for memory.h... yes >> checking for strings.h... yes >> checking for inttypes.h... yes >> checking for stdint.h... yes >> checking for unistd.h... yes >> checking minix/config.h usability... no >> checking minix/config.h presence... no >> checking for minix/config.h... no >> checking whether it is safe to define __EXTENSIONS__... yes >> checking for library containing strerror... none required >> checking for gcc... (cached) cc >> checking whether we are using the GNU C compiler... (cached) yes >> checking whether cc accepts -g... (cached) yes >> checking for cc option to accept ISO C89... (cached) none needed >> checking dependency style of cc... (cached) gcc3 >> checking for gcc... (cached) cc >> checking whether we are using the GNU C compiler... (cached) yes >> checking whether cc accepts -g... (cached) yes >> checking for cc option to accept ISO C89... (cached) none needed >> checking dependency style of cc... (cached) gcc3 >> checking for ANSI C header files... (cached) yes >> checking for pkg-config... /usr/local/bin/pkg-config >> checking pkg-config is at least version 0.9.0... yes >> configure: Configuring for plain GTK+ >> checking for PACKAGE... yes >> checking whether NLS is requested... no >> checking for intltool-update... /usr/local/bin/intltool-update >> checking for intltool-merge... /usr/local/bin/intltool-merge >> checking for intltool-extract... /usr/local/bin/intltool-extract >> checking for xgettext... /usr/local/bin/xgettext >> checking for msgmerge... /usr/local/bin/msgmerge >> checking for msgfmt... /usr/local/bin/msgfmt >> checking for gmsgfmt... /usr/local/bin/msgfmt >> checking for perl... /usr/local/bin/perl >> checking for perl >= 5.8.1... 5.16.2 >> checking for XML::Parser... configure: error: XML::Parser perl module is required for intltool >> ===> Script "configure" failed unexpectedly. >> Please report the problem to martymac@FreeBSD.org [maintainer] and attach the >> "/usr/ports/net/grsync/work/grsync-1.2.2/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/local/sbin/pkg info -g -Ea). >> *** Error code 1 >> >> Stop in /usr/ports/net/grsync. >> >> >> hope that helps to solve the issue >> thanks >> -- > I have hit this more than once. Try re-installing p5-XML-Parser. That > has always fixed it for me > > Also, cvsup is deprecated and will be going away soon. Please switch > to portsnap or svn to update your ports tree. Also, read the security > bulletin that was posted to freebsd-announce@. It explains a bit of > why csup and cvs are likely to go away sooner than was expected. This normally shows up if the users has done a perl upgrade, since I see perl5.16 mentioned in the configure output I assume this is the case. Instructions how to deal with this are mentioned in the 20121104 entry of ports/UPDATING. -Koop
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?50A7F0FB.5080108>