Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#1615 - totem build-depends on perlxml

Attached to Project: Arch Linux
Opened by Xavier de Labouret (zezaz) - Tuesday, 12 October 2004, 16:46 GMT
Last edited by Dale Blount (dale) - Tuesday, 12 October 2004, 18:00 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To arjan timmerman (blaasvis)
Architecture not specified
Severity Medium
Priority Normal
Reported Version 0.7 Wombat
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

I failed to build totem with abs, because the perlxml package is not installed on my system. Thank you for adding it to (at least) the build-depends!

------------8<----------------

# pacman -Q | grep perlxml
# grep ^pkgver PKGBUILD
pkgver=0.99.17
# makepkg -i
==> Making package: totem (Tue Oct 12 18:31:35 CEST 2004)
==> Checking Runtime Dependencies...
==> Missing Dependencies:
==>
requires: hal
requires: nautilus-cd-burner
==>
[root@xdelabouret totem]# makepkg -i -s
==> Making package: totem (Tue Oct 12 18:31:44 CEST 2004)
==> Checking Runtime Dependencies...
==> Missing Dependencies:
==>
requires: hal
requires: nautilus-cd-burner
==>
==> Installing missing dependencies...

Targets: dbus-0.22-2 hal-0.2.97-1 nautilus-cd-burner-2.8.1-1

Total Package Size: 0.9 MB

:: Retrieving packages from extra...
dbus-0.22-2 [################################] 100% 532K 29.6K/s 00:00:17
hal-0.2.97-1 [################################] 100% 179K 41.3K/s 00:00:04
nautilus-cd-burner-2.8.1 [################################] 100% 211K 25.1K/s 00:00:08

checking package integrity... done.
loading package data... done.
checking for file conflicts... done.
installing dbus... done.
installing hal... done.
installing nautilus-cd-burner... done.

==> Checking Buildtime Dependencies...
==> Retrieving Sources...
==> Downloading totem-0.99.17.tar.gz
--18:32:18-- http://ftp.gnome.org/pub/gnome/sources/totem/0.99/totem-0.99.17.tar.gz
=> `totem-0.99.17.tar.gz'
Resolving ftp.gnome.org... 130.239.18.165, 130.239.18.142
Connecting to ftp.gnome.org[130.239.18.165]:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1,517,666 [application/x-tar]

100%[====================================================>] 1,517,666 23.19K/s ETA 00:00

18:33:13 (27.26 KB/s) - `totem-0.99.17.tar.gz' saved [1517666/1517666]

==> Found totem.install in build dir
==> Found Makefile in build dir
==> WARNING: MD5sums are missing or incomplete. Cannot verify source integrity.
==> Extracting Sources...
==> tar --use-compress-program=gzip -xf totem-0.99.17.tar.gz
==> Starting build()...
checking for a BSD-compatible install... /bin/install -c
checking whether build environment is sane... yes
checking whether make sets $(MAKE)... yes
checking for working aclocal-1.4... missing
checking for working autoconf... found
checking for working automake-1.4... missing
checking for working autoheader... found
checking for working makeinfo... found
checking for g++... g++
checking for C++ compiler default output file name... a.out
checking whether the C++ compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for gcc... gcc
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking for a sed that does not truncate output... /bin/sed
checking for egrep... grep -E
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for /usr/bin/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
checking how to recognise dependent libraries... pass_all
checking how to run the C preprocessor... gcc -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 dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking how to run the C++ preprocessor... g++ -E
checking for g77... no
checking for f77... no
checking for xlf... no
checking for frt... no
checking for pgf77... no
checking for fort77... no
checking for fl32... no
checking for af77... no
checking for f90... no
checking for xlf90... no
checking for pgf90... no
checking for epcf90... no
checking for f95... no
checking for fort... no
checking for xlf95... no
checking for ifc... no
checking for efc... no
checking for pgf95... no
checking for lf95... no
checking for gfortran... no
checking whether we are using the GNU Fortran 77 compiler... no
checking whether accepts -g... no
checking the maximum length of command line arguments... 32768
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for objdir... .libs
checking for ar... ar
checking for ranlib... ranlib
checking for strip... strip
checking if gcc static flag works... yes
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC
checking if gcc PIC flag -fPIC works... yes
checking if gcc supports -c -o file.o... yes
checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
configure: creating libtool
appending configuration tag "CXX" to libtool
checking for ld used by g++... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking for g++ option to produce PIC... -fPIC
checking if g++ PIC flag -fPIC works... yes
checking if g++ supports -c -o file.o... yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
appending configuration tag "F77" to libtool
checking for intltool >= 0.20... 0.30 found
checking for perl... /usr/bin/perl
configure: error: XML::Parser perl module is required for intltool
make: *** No targets specified and no makefile found. Stop.
==> ERROR: Build Failed. Aborting...
#

This task depends upon

Closed by  arjan timmerman (blaasvis)
Thursday, 14 October 2004, 14:44 GMT
Reason for closing:  Fixed
Comment by Jan de Groot (JGC) - Thursday, 14 October 2004, 07:28 GMT
checking for intltool >= 0.20... 0.30 found
checking for perl... /usr/bin/perl
configure: error: XML::Parser perl module is required for intltool

It seems you have intltool on your system, which has a dependency on the xml-parser perl module. I think it got lost on a perl upgrade, or you forced intltool without the xml-parser module.
Comment by Xavier de Labouret (zezaz) - Thursday, 14 October 2004, 08:26 GMT

Yes, intltool was found, but no, it is not installed on my system :)
The configure framework of the source package installed it in the totem build directory. I believe that it it this local version that was found by configure.

This is why intltool is present (in the build dir) without xml-parser being installed (globally) on my setup. So, i still thing xml-parser is a build dependency for totem. I could not say however if the best should be a direct dependency, or an indirect dependency.

Having intltool (itself depending on xml-parser) as a makedepends for totem should solve however.

Details follow. Thanks for helping though.

--------------8<---------------

# pacman -Qi intltool
Package "intltool" was not found.

# pwd
/var/abs/extra/gnome/totem/src/totem-0.99.17
# ls intltool-*
intltool-extract intltool-merge intltool-update
intltool-extract.in intltool-merge.in intltool-update.in
Comment by arjan timmerman (blaasvis) - Thursday, 14 October 2004, 14:44 GMT
added it as makedepend ;)

Loading...