All dependencies are installed, but 'emerge ethereal' failed, evidently because of a 'permission denied' error on editcap.pod. This happened after doing an 'emerge rsync' and ensuring that portage was up to date. Following is taken from the output of 'emerge ethereal': make[3]: Entering directory `/var/tmp/portage/ethereal-0.9.7/work/ethereal-0.9.7/doc' ./editcap.pod \ --center="The Ethereal Network Analyzer" \ --release=0.9.7 \ > ../editcap.1 /bin/sh: ./editcap.pod: Permission denied make[3]: *** [../editcap.1] Error 126 editcap.pod appears to have the same permissions as the other files in that directory: 664. Thanks.
Followup: I manually downloaded, compiled and installed ethereal-0.9.8 on the same machine. The only argument I passed to configure was -- sysconfdir=/etc/ethereal. Following is a snippet of the make output that I think corresponds to the part of the ebuild's output that failed: make ../editcap.1 ) make[3]: Entering directory `/home/wesley/src/ethereal-0.9.8/doc' /opt/perl/bin/pod2man ./editcap.pod \ --center="The Ethereal Network Analyzer" \ --release=0.9.8 \ > ../editcap.1 make[3]: Leaving directory `/home/wesley/src/ethereal-0.9.8/doc Note that it's trying to execute pod2man with ./editcap.pod as an argument, whereas the ebuild had it trying to execute ./editcap.pod. The permissions problem may just be that editcap.pod doesn't have execute permission. Might be able to resolve this just by updating the ebuild to 0.9.8.
please paste #emerge info
# emerge info Portage 2.0.45-r5 (default-1.0, gcc-2.95.3, glibc-2.2.5-r2,2.2.5-r7) ================================================================= System uname: 2.4.19-gentoo-r5 i686 Pentium III (Coppermine) USE="x86 oss apm arts avi crypt encode jpeg libg++ libwww mikmod mmx mpeg ncurses pdflib qt qtmt sdl spell truetype xml2 xv berkdb bonobo esd gdbm gif gnome-libs gpm gtk gtkhtml guile imlib ldap nls opengl pam perl png postgres python readline slang ssl svga tcltk tcpd tiff X -3dnow -cups -java -kde -motif -oggvorbis -quicktime -xmms" ARCH="x86" COMPILER="" CHOST="i686-pc-linux-gnu" CFLAGS="-march=i686 -O3 -pipe" CXXFLAGS="-march=i686 -O3 -pipe" ACCEPT_KEYWORDS="x86" CONFIG_PROTECT="/etc /var/qmail/control /usr/share/config /usr/kde/2/share/config /usr/kde/3/share/config" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" MAKEOPTS="-j2" JDK_HOME="/opt/blackdown-jdk-1.3.1" JAVA_HOME="/opt/blackdown-jdk-1.3.1" AUTOCLEAN="yes" SYNC="rsync://rsync.gentoo.org/gentoo-portage" GENTOO_MIRRORS="http://www.ibiblio.org/gentoo ftp.surfnet.nl/pub/os/Linux/distr/gentoo"
Why is perl in /opt/perl? More then likely the ebuild is confused because it cannot find pod2man, thus it substitues nothing for the variable which holds the name and location of pod2man. Pay careful attention as the configure script runs when you do emerge, this will note if it successfully located [checking for pod2man]. This is why you get the permission denied. First, try the new 0.9.8 ebuild and see if that works for you. If it doesn't do it, you might want to install perl the gentoo way (5.8.0 is fairly stable and merely requires you to add ~x86 to your ACCEPT_KEYWORDS in make.conf).
You're right, it's not finding pod2man, even when /opt/perl/bin is in PATH and `which pod2man` returns /opt/perl/bin/pod2man as it should. This is true with both versions 0.9.7 and 0.9.8 ebuilds. Perl is in /opt/perl because I like it there, I'm used to building perl by hand, and I couldn't figure out how to unmask perl-5.8.0. Incidentally, I also greatly prefer to install perl modules via CPAN. Do the ebuild's have perl's location hardcoded, or is there another environment variable I should be setting to tell it where to find perlish things? I don't want to add ~x86 to ACCEPT_KEYWORDS in make.conf because as I understand it, that would cause me to start using not only perl 5.8.x but also unstable versions of who knows what other packages. There ought to be a way to use a hand-compiled perl without breaking every package that uses perl; apparently running emerge --inject isn't sufficient. At any rate, this may have more to do with how I installed perl than with the ethereal ebuild. Though I'm not sure why ethereal's configure can't find pod2man if it's in the PATH; perhaps the bug is that its expected location is hardcoded??
Issue identified; closing bug.
