* [gentoo-user] pam-1.1.4 emerge error on x86
@ 2011-10-14 23:01 Mick
2011-10-14 23:20 ` Jonas de Buhr
0 siblings, 1 reply; 8+ messages in thread
From: Mick @ 2011-10-14 23:01 UTC (permalink / raw
To: Gentoo-User
[-- Attachment #1: Type: text/plain, Size: 7822 bytes --]
Have you seen this before?
====================================
/var/tmp/portage/sys-libs/pam-1.1.4/image//usr/share/doc/pam-1.1.4/
make[3]: Leaving directory `/var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1
.1.4/doc/sag'
make[2]: Leaving directory `/var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1
.1.4/doc/sag'
Making install in adg
make[2]: Entering directory `/var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-
1.1.4/doc/adg'
make[3]: Entering directory `/var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-
1.1.4/doc/adg'
make[3]: Nothing to be done for `install-exec-am'.
/bin/sh ../../mkinstalldirs
/var/tmp/portage/sys-libs/pam-1.1.4/image//usr/share/doc/pam-1.1.4
/bin/sh ../../mkinstalldirs
/var/tmp/portage/sys-libs/pam-1.1.4/image//usr/share/doc/pam-1.1.4
/bin/sh ../../mkinstalldirs
/var/tmp/portage/sys-libs/pam-1.1.4/image//usr/share/doc/pam-1.1.4/html
test -f html/Linux-PAM_ADG.html || exit 0; \
/bin/sh /var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4/install-sh
-c -m 644 html/Linux-PAM_ADG.html html/adg-*.html \
/var/tmp/portage/sys-libs/pam-1.1.4/image//usr/share/doc/pam-1.1.4/html/
|| \
/bin/sh /var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4/install-sh
-c -m 644 ./html/Linux-PAM_ADG.html \
./html/sag-*.html \
/var/tmp/portage/sys-libs/pam-1.1.4/image//usr/share/doc/pam-1.1.4/html/
test -f Linux-PAM_ADG.txt || exit 0; \
/bin/sh /var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4/install-sh
-c -m 644 Linux-PAM_ADG.txt
/var/tmp/portage/sys-libs/pam-1.1.4/image//usr/share/doc/pam-1.1.4/ ||
\
/bin/sh /var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4/install-sh
-c -m 644 ./Linux-PAM_ADG.txt \
/var/tmp/portage/sys-libs/pam-1.1.4/image//usr/share/doc/pam-1.1.4/
test -f Linux-PAM_ADG.pdf || exit 0; \
/bin/sh /var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4/install-sh
-c -m 644 Linux-PAM_ADG.pdf
/var/tmp/portage/sys-libs/pam-1.1.4/image//usr/share/doc/pam-1.1.4/ ||
\
/bin/sh /var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4/install-sh
-c -m 644 ./Linux-PAM_ADG.pdf \
/var/tmp/portage/sys-libs/pam-1.1.4/image//usr/share/doc/pam-1.1.4/
make[3]: Leaving directory
`/var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4/doc/adg'
make[2]: Leaving directory
`/var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4/doc/adg'
Making install in mwg
make[2]: Entering directory
`/var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4/doc/mwg'
make[3]: Entering directory
`/var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4/doc/mwg'
make[3]: Nothing to be done for `install-exec-am'.
/bin/sh ../../mkinstalldirs
/var/tmp/portage/sys-libs/pam-1.1.4/image//usr/share/doc/pam-1.1.4
/bin/sh ../../mkinstalldirs
/var/tmp/portage/sys-libs/pam-1.1.4/image//usr/share/doc/pam-1.1.4
/bin/sh ../../mkinstalldirs
/var/tmp/portage/sys-libs/pam-1.1.4/image//usr/share/doc/pam-1.1.4/html
test -f html/Linux-PAM_MWG.html || exit 0; \
/bin/sh /var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4/install-sh
-c -m 644 html/Linux-PAM_MWG.html html/mwg-*.html \
/var/tmp/portage/sys-libs/pam-1.1.4/image//usr/share/doc/pam-1.1.4/html/
|| \
/bin/sh /var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4/install-sh
-c -m 644 ./html/Linux-PAM_MWG.html \
./html/sag-*.html \
/var/tmp/portage/sys-libs/pam-1.1.4/image//usr/share/doc/pam-1.1.4/html/
test -f Linux-PAM_MWG.txt || exit 0; \
/bin/sh /var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4/install-sh
-c -m 644 Linux-PAM_MWG.txt
/var/tmp/portage/sys-libs/pam-1.1.4/image//usr/share/doc/pam-1.1.4/ ||
\
/bin/sh /var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4/install-sh
-c -m 644 ./Linux-PAM_MWG.txt \
/var/tmp/portage/sys-libs/pam-1.1.4/image//usr/share/doc/pam-1.1.4/
test -f Linux-PAM_MWG.pdf || exit 0; \
/bin/sh /var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4/install-sh
-c -m 644 Linux-PAM_MWG.pdf
/var/tmp/portage/sys-libs/pam-1.1.4/image//usr/share/doc/pam-1.1.4/ ||
\
/bin/sh /var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4/install-sh
-c -m 644 ./Linux-PAM_MWG.pdf \
/var/tmp/portage/sys-libs/pam-1.1.4/image//usr/share/doc/pam-1.1.4/
make[3]: Leaving directory
`/var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4/doc/mwg'
make[2]: Leaving directory
`/var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4/doc/mwg'
make[2]: Entering directory
`/var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4/doc'
make[3]: Entering directory
`/var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4/doc'
make[3]: Nothing to be done for `install-exec-am'.
test -z "/usr/share/doc/pam-1.1.4/html" || /bin/mkdir -p
"/var/tmp/portage/sys-libs/pam-1.1.4/image//usr/share/doc/pam-1.1.4/html"
/usr/bin/install -c -m 644 'index.html'
'/var/tmp/portage/sys-libs/pam-1.1.4/image//usr/share/doc/pam-1.1.4/html/index.html'
make[3]: Leaving directory
`/var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4/doc'
make[2]: Leaving directory
`/var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4/doc'
make[1]: Leaving directory
`/var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4/doc'
Making install in examples
make[1]: Entering directory
`/var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4/examples'
make[2]: Entering directory
`/var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4/examples'
make[2]: Nothing to be done for `install-exec-am'.
make[2]: Nothing to be done for `install-data-am'.
make[2]: Leaving directory
`/var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4/examples'
make[1]: Leaving directory
`/var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4/examples'
Making install in xtests
make[1]: Entering directory
`/var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4/xtests'
make[2]: Entering directory
`/var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4/xtests'
make[2]: Nothing to be done for `install-exec-am'.
make[2]: Nothing to be done for `install-data-am'.
make[2]: Leaving directory
`/var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4/xtests'
make[1]: Leaving directory
`/var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4/xtests'
make[1]: Entering directory
`/var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4'
make[2]: Entering directory
`/var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4'
make[2]: Nothing to be done for `install-exec-am'.
make[2]: Nothing to be done for `install-data-am'.
make[2]: Leaving directory
`/var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4'
make[1]: Leaving directory
`/var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4'
/var/tmp/portage/sys-libs/pam-1.1.4/temp/environment: line 2226:
scanelf: command not found
* ERROR: sys-libs/pam-1.1.4 failed (install phase):
* unable to read SONAME from libpam.so
*
* Call stack:
* ebuild.sh, line 56: Called src_install
* environment, line 3509: Called gen_usr_ldscript '-a' 'pam'
'pamc' 'pam_misc'
* environment, line 2227: Called die
* The specific snippet of code:
* [[ -z ${tlib} ]] && die "unable to read
SONAME from ${lib}";
*
* If you need support, post the output of 'emerge --info =sys-libs/pam-1.1.4',
* the complete build log and the output of 'emerge -pqv =sys-libs/pam-1.1.4'.
* The complete build log is located at
'/var/log/portage/sys-libs:pam-1.1.4:20111014-213620.log'.
* The ebuild environment file is located at
'/var/tmp/portage/sys-libs/pam-1.1.4/temp/environment'.
* S: '/var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4'
* QA Notice: command not found:
*
* /var/tmp/portage/sys-libs/pam-1.1.4/temp/environment: line
2226: scanelf: command not found
====================================
Another x86 machine installs fine. emerge --info attached.
--
Regards,
Mick
[-- Attachment #2: emerge.info --]
[-- Type: application/octet-stream, Size: 5134 bytes --]
Portage 2.1.10.11 (default/linux/x86/10.0/desktop, gcc-4.5.3, glibc-2.12.2-r0, 2.6.39-gentoo-r3 i686)
=================================================================
System uname: Linux-2.6.39-gentoo-r3-i686-Intel-R-_Pentium-R-_III_Mobile_CPU_1066MHz-with-gentoo-2.0.3
Timestamp of tree: Fri, 14 Oct 2011 18:15:01 +0000
app-shells/bash: 4.1_p9
dev-lang/python: 2.7.1-r1, 3.1.3-r1
dev-util/cmake: 2.8.4-r1
dev-util/pkgconfig: 0.26
sys-apps/baselayout: 2.0.3
sys-apps/openrc: 0.8.3-r1
sys-apps/sandbox: 2.4
sys-devel/autoconf: 2.13::<unknown repository>, 2.68
sys-devel/automake: 1.9.6-r2::<unknown repository>, 1.10.3, 1.11.1
sys-devel/binutils: 2.20.1-r1
sys-devel/gcc: 4.5.3-r1
sys-devel/gcc-config: 1.4.1-r1
sys-devel/libtool: 2.4-r1
sys-devel/make: 3.82-r1
sys-kernel/linux-headers: 2.6.36.1 (virtual/os-headers)
sys-libs/glibc: 2.12.2
Repositories: gentoo enlightenment x-portage
ACCEPT_KEYWORDS="x86"
ACCEPT_LICENSE="* -@EULA AdobeFlash-10.1"
CBUILD="i686-pc-linux-gnu"
CFLAGS="-O2 -march=pentium3 -fomit-frame-pointer -msse -mmmx -pipe"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/share/config /usr/share/gnupg/qualified.txt /usr/share/openvpn/easy-rsa"
CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/revdep-rebuild /etc/sandbox.d /etc/splash /etc/terminfo"
CXXFLAGS="-O2 -march=pentium3 -fomit-frame-pointer -msse -mmmx -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="assume-digests binpkg-logs distlocks ebuild-locks fail-clean fixlafiles fixpackages news parallel-fetch protect-owned sandbox sfperms strict unknown-features-warn unmerge-logs unmerge-orphans userfetch usersandbox"
FFLAGS=""
GENTOO_MIRRORS="http://gentoo.virginmedia.com/ http://gentoo.tiscali.nl/ http://de-mirror.org/distro/gentoo/ http://gentoo.mneisen.org/ http://gentoo.wheel.sk/ http://gentoo.mirror.pw.edu.pl/ http://gentoo.supp.name/"
LANG="en_GB.UTF-8"
LDFLAGS="-Wl,-O1 -Wl,--as-needed"
LINGUAS="en en_GB el"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_CONFIGROOT="/"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/var/lib/layman/enlightenment /usr/local/portage"
SYNC="rsync://rsync.uk.gentoo.org/gentoo-portage"
USE="X a52 aac aalib acl acpi alsa asf atm berkdb bluetooth branding bzip2 cairo cdda cdparanoia cdr cli consolekit cracklib crypt css cups curl cxx dbus divx dri dts dvd dvdr dvdread emboss encode exif fam ffmpeg flac fontconfig fortran gdbm gdu gif glitz gmedia gnutls gpm gtalk hpijs hpn hybrid hybrid-auth iconv idea imagemagick imlib injection ipv6 irda irmc jabber jpeg kde laptop lcms ldap libnotify live lm_sensors logrotate mad madwifi matroska md5sum mjpeg mmx mng modplug modules mp3 mp4 mpeg mplayer mudflap nat ncurses nls npp nptl nptlonly nsplugin ntfs ogg opengl openmp pam pango pcmcia pcre pda pdf pmu png policykit ppds pppd qt3support qt4 rc5 rdesktop readline realmedia reiserfs rfc3779 rt2500usb rtmp rtsp scanner sdl semantic-desktop session smime speex spell sqlite sse ssl startup-notification svg svga sysfs tcpd theora tidy tiff truetype udev unicode usb vcd vidix vnc vorbis vram win32codecs wmf wmp x264 x86 xcb xcomposite xine xml xmp xorg xulrunner xv xvid xvmc yv12 zlib" ALSA_CARDS="maestro3" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mmap_emul mulaw multi null plug rate route share shm softvol" APACHE2_MODULES="actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache cgi cgid dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" CALLIGRA_FEATURES="kexi words flow plan stage tables krita karbon braindump" CAMERAS="fuji topfield" COLLECTD_PLUGINS="df interface irq load memory rrdtool swap syslog" ELIBC="glibc" GPSD_PROTOCOLS="ashtech aivdm earthmate evermore fv18 garmin garmintxt gpsclock itrax mtk3301 nmea ntrip navcom oceanserver oldstyle oncore rtcm104v2 rtcm104v3 sirf superstar2 timing tsip tripmate tnt ubx" INPUT_DEVICES="keyboard mouse synaptics evdev" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LINGUAS="en en_GB el" PHP_TARGETS="php5-3" RUBY_TARGETS="ruby18" USERLAND="GNU" VIDEO_CARDS="radeon" XTABLES_ADDONS="quota2 psd pknock lscan length2 ipv4options ipset ipp2p iface geoip fuzzy condition tee tarpit sysrq steal rawnat logmark ipmark dhcpmac delude chaos account"
Unset: CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LC_ALL, PORTAGE_BUNZIP2_COMMAND, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: [gentoo-user] pam-1.1.4 emerge error on x86
2011-10-14 23:01 [gentoo-user] pam-1.1.4 emerge error on x86 Mick
@ 2011-10-14 23:20 ` Jonas de Buhr
2011-10-15 12:24 ` Mick
0 siblings, 1 reply; 8+ messages in thread
From: Jonas de Buhr @ 2011-10-14 23:20 UTC (permalink / raw
To: gentoo-user
Am Sat, 15 Oct 2011 00:01:04 +0100
schrieb Mick <michaelkintzios@gmail.com>:
> Have you seen this before?
> ====================================
> /var/tmp/portage/sys-libs/pam-1.1.4/image//usr/share/doc/pam-1.1.4/
> make[3]: Leaving directory
> `/var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1 .1.4/doc/sag'
> make[2]: Leaving directory
> `/var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1 .1.4/doc/sag'
> Making install in adg
> make[2]: Entering directory
> `/var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM- 1.1.4/doc/adg'
> make[3]: Entering directory
> `/var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM- 1.1.4/doc/adg'
> make[3]: Nothing to be done for `install-exec-am'.
> /bin/sh ../../mkinstalldirs
> /var/tmp/portage/sys-libs/pam-1.1.4/image//usr/share/doc/pam-1.1.4
> /bin/sh ../../mkinstalldirs
> /var/tmp/portage/sys-libs/pam-1.1.4/image//usr/share/doc/pam-1.1.4
> /bin/sh ../../mkinstalldirs
> /var/tmp/portage/sys-libs/pam-1.1.4/image//usr/share/doc/pam-1.1.4/html
> test -f html/Linux-PAM_ADG.html || exit 0; \
> /bin/sh /var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4/install-sh
> -c -m 644 html/Linux-PAM_ADG.html html/adg-*.html \
> /var/tmp/portage/sys-libs/pam-1.1.4/image//usr/share/doc/pam-1.1.4/html/
> || \
> /bin/sh /var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4/install-sh
> -c -m 644 ./html/Linux-PAM_ADG.html \
> ./html/sag-*.html \
> /var/tmp/portage/sys-libs/pam-1.1.4/image//usr/share/doc/pam-1.1.4/html/
> test -f Linux-PAM_ADG.txt || exit 0; \
> /bin/sh /var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4/install-sh
> -c -m 644 Linux-PAM_ADG.txt
> /var/tmp/portage/sys-libs/pam-1.1.4/image//usr/share/doc/pam-1.1.4/ ||
> \
> /bin/sh /var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4/install-sh
> -c -m 644 ./Linux-PAM_ADG.txt \
> /var/tmp/portage/sys-libs/pam-1.1.4/image//usr/share/doc/pam-1.1.4/
> test -f Linux-PAM_ADG.pdf || exit 0; \
> /bin/sh /var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4/install-sh
> -c -m 644 Linux-PAM_ADG.pdf
> /var/tmp/portage/sys-libs/pam-1.1.4/image//usr/share/doc/pam-1.1.4/ ||
> \
> /bin/sh /var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4/install-sh
> -c -m 644 ./Linux-PAM_ADG.pdf \
> /var/tmp/portage/sys-libs/pam-1.1.4/image//usr/share/doc/pam-1.1.4/
> make[3]: Leaving directory
> `/var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4/doc/adg'
> make[2]: Leaving directory
> `/var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4/doc/adg'
> Making install in mwg
> make[2]: Entering directory
> `/var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4/doc/mwg'
> make[3]: Entering directory
> `/var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4/doc/mwg'
> make[3]: Nothing to be done for `install-exec-am'.
> /bin/sh ../../mkinstalldirs
> /var/tmp/portage/sys-libs/pam-1.1.4/image//usr/share/doc/pam-1.1.4
> /bin/sh ../../mkinstalldirs
> /var/tmp/portage/sys-libs/pam-1.1.4/image//usr/share/doc/pam-1.1.4
> /bin/sh ../../mkinstalldirs
> /var/tmp/portage/sys-libs/pam-1.1.4/image//usr/share/doc/pam-1.1.4/html
> test -f html/Linux-PAM_MWG.html || exit 0; \
> /bin/sh /var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4/install-sh
> -c -m 644 html/Linux-PAM_MWG.html html/mwg-*.html \
> /var/tmp/portage/sys-libs/pam-1.1.4/image//usr/share/doc/pam-1.1.4/html/
> || \
> /bin/sh /var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4/install-sh
> -c -m 644 ./html/Linux-PAM_MWG.html \
> ./html/sag-*.html \
> /var/tmp/portage/sys-libs/pam-1.1.4/image//usr/share/doc/pam-1.1.4/html/
> test -f Linux-PAM_MWG.txt || exit 0; \
> /bin/sh /var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4/install-sh
> -c -m 644 Linux-PAM_MWG.txt
> /var/tmp/portage/sys-libs/pam-1.1.4/image//usr/share/doc/pam-1.1.4/ ||
> \
> /bin/sh /var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4/install-sh
> -c -m 644 ./Linux-PAM_MWG.txt \
> /var/tmp/portage/sys-libs/pam-1.1.4/image//usr/share/doc/pam-1.1.4/
> test -f Linux-PAM_MWG.pdf || exit 0; \
> /bin/sh /var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4/install-sh
> -c -m 644 Linux-PAM_MWG.pdf
> /var/tmp/portage/sys-libs/pam-1.1.4/image//usr/share/doc/pam-1.1.4/ ||
> \
> /bin/sh /var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4/install-sh
> -c -m 644 ./Linux-PAM_MWG.pdf \
> /var/tmp/portage/sys-libs/pam-1.1.4/image//usr/share/doc/pam-1.1.4/
> make[3]: Leaving directory
> `/var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4/doc/mwg'
> make[2]: Leaving directory
> `/var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4/doc/mwg'
> make[2]: Entering directory
> `/var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4/doc'
> make[3]: Entering directory
> `/var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4/doc'
> make[3]: Nothing to be done for `install-exec-am'.
> test -z "/usr/share/doc/pam-1.1.4/html" || /bin/mkdir -p
> "/var/tmp/portage/sys-libs/pam-1.1.4/image//usr/share/doc/pam-1.1.4/html"
> /usr/bin/install -c -m 644 'index.html'
> '/var/tmp/portage/sys-libs/pam-1.1.4/image//usr/share/doc/pam-1.1.4/html/index.html'
> make[3]: Leaving directory
> `/var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4/doc'
> make[2]: Leaving directory
> `/var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4/doc'
> make[1]: Leaving directory
> `/var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4/doc'
> Making install in examples
> make[1]: Entering directory
> `/var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4/examples'
> make[2]: Entering directory
> `/var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4/examples'
> make[2]: Nothing to be done for `install-exec-am'.
> make[2]: Nothing to be done for `install-data-am'.
> make[2]: Leaving directory
> `/var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4/examples'
> make[1]: Leaving directory
> `/var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4/examples'
> Making install in xtests
> make[1]: Entering directory
> `/var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4/xtests'
> make[2]: Entering directory
> `/var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4/xtests'
> make[2]: Nothing to be done for `install-exec-am'.
> make[2]: Nothing to be done for `install-data-am'.
> make[2]: Leaving directory
> `/var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4/xtests'
> make[1]: Leaving directory
> `/var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4/xtests'
> make[1]: Entering directory
> `/var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4'
> make[2]: Entering directory
> `/var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4'
> make[2]: Nothing to be done for `install-exec-am'.
> make[2]: Nothing to be done for `install-data-am'.
> make[2]: Leaving directory
> `/var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4'
> make[1]: Leaving directory
> `/var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4'
> /var/tmp/portage/sys-libs/pam-1.1.4/temp/environment: line 2226:
> scanelf: command not found
you could try reinstalling app-misc/pax-utils.
this is either a missing dependency or for some reason your pax-utils
install is broken.
> * ERROR: sys-libs/pam-1.1.4 failed (install phase):
> * unable to read SONAME from libpam.so
> *
> * Call stack:
> * ebuild.sh, line 56: Called src_install
> * environment, line 3509: Called gen_usr_ldscript '-a' 'pam'
> 'pamc' 'pam_misc'
> * environment, line 2227: Called die
> * The specific snippet of code:
> * [[ -z ${tlib} ]] && die "unable to read
> SONAME from ${lib}";
> *
> * If you need support, post the output of 'emerge --info
> =sys-libs/pam-1.1.4',
> * the complete build log and the output of 'emerge -pqv
> =sys-libs/pam-1.1.4'.
> * The complete build log is located at
> '/var/log/portage/sys-libs:pam-1.1.4:20111014-213620.log'.
> * The ebuild environment file is located at
> '/var/tmp/portage/sys-libs/pam-1.1.4/temp/environment'.
> * S: '/var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4'
> * QA Notice: command not found:
> *
> * /var/tmp/portage/sys-libs/pam-1.1.4/temp/environment: line
> 2226: scanelf: command not found
> ====================================
>
> Another x86 machine installs fine. emerge --info attached.
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: [gentoo-user] pam-1.1.4 emerge error on x86
2011-10-14 23:20 ` Jonas de Buhr
@ 2011-10-15 12:24 ` Mick
2011-10-15 13:09 ` Jonas de Buhr
0 siblings, 1 reply; 8+ messages in thread
From: Mick @ 2011-10-15 12:24 UTC (permalink / raw
To: gentoo-user
[-- Attachment #1: Type: Text/Plain, Size: 1620 bytes --]
On Saturday 15 Oct 2011 00:20:14 Jonas de Buhr wrote:
> Am Sat, 15 Oct 2011 00:01:04 +0100
>
> schrieb Mick <michaelkintzios@gmail.com>:
> > Have you seen this before?
> > `/var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4'
> > make[1]: Leaving directory
> > `/var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4'
> > /var/tmp/portage/sys-libs/pam-1.1.4/temp/environment: line 2226:
> > scanelf: command not found
>
> you could try reinstalling app-misc/pax-utils.
>
> this is either a missing dependency or for some reason your pax-utils
> install is broken.
Thank you! I've remerged pax-utils. This is an old laptop and both the main
battery and CMOS battery have run out of juice. I noticed that the clock was
out by more than 100 years - but I think that I had sync'ed portage in the
meanwhile.
I have not been able to proceed with pam, because world now wants to emerge
ruby. However, it comes up with this error:
>>> Verifying ebuild manifests
!!! Digest verification failed:
!!! /usr/portage/dev-lang/ruby/ruby-1.8.7_p352.ebuild
!!! Reason: Filesize does not match recorded size
!!! Got: 5574
!!! Expected: 5569
I've deleted the ebuild, then resync'ed twice with different mirrors and the
error persists. Another box I have (which does not come up with this error)
shows:
$ ls -la /usr/portage/dev-lang/ruby/ruby-1.8.7_p352.ebuild
-rw-r--r-- 1 root root 5574 Oct 14 09:31 /usr/portage/dev-
lang/ruby/ruby-1.8.7_p352.ebuild
So, is 5574 the wrong size, or is the ebuild file in the latest sync'ing of
portage wrong?
--
Regards,
Mick
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [gentoo-user] pam-1.1.4 emerge error on x86
2011-10-15 12:24 ` Mick
@ 2011-10-15 13:09 ` Jonas de Buhr
2011-10-15 17:17 ` Mick
0 siblings, 1 reply; 8+ messages in thread
From: Jonas de Buhr @ 2011-10-15 13:09 UTC (permalink / raw
To: gentoo-user
Am Sat, 15 Oct 2011 13:24:02 +0100
schrieb Mick <michaelkintzios@gmail.com>:
> On Saturday 15 Oct 2011 00:20:14 Jonas de Buhr wrote:
> > Am Sat, 15 Oct 2011 00:01:04 +0100
> >
> > schrieb Mick <michaelkintzios@gmail.com>:
> > > Have you seen this before?
>
> > > `/var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4'
> > > make[1]: Leaving directory
> > > `/var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4'
> > > /var/tmp/portage/sys-libs/pam-1.1.4/temp/environment: line 2226:
> > > scanelf: command not found
> >
> > you could try reinstalling app-misc/pax-utils.
> >
> > this is either a missing dependency or for some reason your
> > pax-utils install is broken.
>
> Thank you! I've remerged pax-utils. This is an old laptop and both
> the main battery and CMOS battery have run out of juice. I noticed
> that the clock was out by more than 100 years - but I think that I
> had sync'ed portage in the meanwhile.
>
> I have not been able to proceed with pam, because world now wants to
> emerge ruby. However, it comes up with this error:
>
> >>> Verifying ebuild manifests
>
> !!! Digest verification failed:
> !!! /usr/portage/dev-lang/ruby/ruby-1.8.7_p352.ebuild
> !!! Reason: Filesize does not match recorded size
> !!! Got: 5574
> !!! Expected: 5569
>
> I've deleted the ebuild, then resync'ed twice with different mirrors
> and the error persists. Another box I have (which does not come up
> with this error) shows:
>
> $ ls -la /usr/portage/dev-lang/ruby/ruby-1.8.7_p352.ebuild
> -rw-r--r-- 1 root root 5574 Oct 14 09:31 /usr/portage/dev-
> lang/ruby/ruby-1.8.7_p352.ebuild
>
> So, is 5574 the wrong size, or is the ebuild file in the latest
> sync'ing of portage wrong?
did you delete just the ebuild or the Manifest too? i suspect that due
to wrong date setting portage did not update the Manifest file which
contains the filesize.
rm -rf /usr/portage/dev-lang/ruby && emerge --sync
should help in that case. but you might run into more date related
update problems later. maybe you should correct your date and extract a
portage snapshot and sync to get rid of those problems once and for all.
my
/usr/portage/dev-lang/ruby/Manifest
says
EBUILD ruby-1.8.7_p352.ebuild 5574 RMD160
e822545306c9e2b2a17767895b851f72c772a149 SHA1
0117f543aa6d7ae064af74af7199deefe6e0dc9d SHA256
79d0f2b28b0b39bf23b9208071f7d50f04a6d76254f42073b2b3e9cc612955a7
so 5574 should be the correct filesize. what does
grep ruby-1.8.7_p352 /usr/portage/dev-lang/ruby/Manifest
say?
if resyncing absolutely does not work, you can compare the SHA256 of
the ebuild on your two computers and if they are the same it should be
relatively safe to do
ebuild /usr/portage/dev-lang/ruby/ruby-1.8.7_p352.ebuild manifest
which will rebuild the Manifest file containing the filesize and the
checksums and after that you can emerge.
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [gentoo-user] pam-1.1.4 emerge error on x86
2011-10-15 13:09 ` Jonas de Buhr
@ 2011-10-15 17:17 ` Mick
2011-10-15 17:27 ` Jonas de Buhr
0 siblings, 1 reply; 8+ messages in thread
From: Mick @ 2011-10-15 17:17 UTC (permalink / raw
To: gentoo-user
[-- Attachment #1: Type: Text/Plain, Size: 3254 bytes --]
On Saturday 15 Oct 2011 14:09:46 Jonas de Buhr wrote:
> Am Sat, 15 Oct 2011 13:24:02 +0100
>
> schrieb Mick <michaelkintzios@gmail.com>:
> > On Saturday 15 Oct 2011 00:20:14 Jonas de Buhr wrote:
> > > Am Sat, 15 Oct 2011 00:01:04 +0100
> > >
> > > schrieb Mick <michaelkintzios@gmail.com>:
> > > > Have you seen this before?
> > > >
> > > > `/var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4'
> > > > make[1]: Leaving directory
> > > > `/var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4'
> > > > /var/tmp/portage/sys-libs/pam-1.1.4/temp/environment: line 2226:
> > > > scanelf: command not found
> > >
> > > you could try reinstalling app-misc/pax-utils.
> > >
> > > this is either a missing dependency or for some reason your
> > > pax-utils install is broken.
> >
> > Thank you! I've remerged pax-utils. This is an old laptop and both
> > the main battery and CMOS battery have run out of juice. I noticed
> > that the clock was out by more than 100 years - but I think that I
> > had sync'ed portage in the meanwhile.
> >
> > I have not been able to proceed with pam, because world now wants to
> >
> > emerge ruby. However, it comes up with this error:
> > >>> Verifying ebuild manifests
> >
> > !!! Digest verification failed:
> > !!! /usr/portage/dev-lang/ruby/ruby-1.8.7_p352.ebuild
> > !!! Reason: Filesize does not match recorded size
> > !!! Got: 5574
> > !!! Expected: 5569
> >
> > I've deleted the ebuild, then resync'ed twice with different mirrors
> > and the error persists. Another box I have (which does not come up
> > with this error) shows:
> >
> > $ ls -la /usr/portage/dev-lang/ruby/ruby-1.8.7_p352.ebuild
> > -rw-r--r-- 1 root root 5574 Oct 14 09:31 /usr/portage/dev-
> > lang/ruby/ruby-1.8.7_p352.ebuild
> >
> > So, is 5574 the wrong size, or is the ebuild file in the latest
> > sync'ing of portage wrong?
>
> did you delete just the ebuild or the Manifest too? i suspect that due
> to wrong date setting portage did not update the Manifest file which
> contains the filesize.
>
> rm -rf /usr/portage/dev-lang/ruby && emerge --sync
>
> should help in that case. but you might run into more date related
> update problems later. maybe you should correct your date and extract a
> portage snapshot and sync to get rid of those problems once and for all.
>
> my
> /usr/portage/dev-lang/ruby/Manifest
> says
>
> EBUILD ruby-1.8.7_p352.ebuild 5574 RMD160
> e822545306c9e2b2a17767895b851f72c772a149 SHA1
> 0117f543aa6d7ae064af74af7199deefe6e0dc9d SHA256
> 79d0f2b28b0b39bf23b9208071f7d50f04a6d76254f42073b2b3e9cc612955a7
>
> so 5574 should be the correct filesize. what does
>
> grep ruby-1.8.7_p352 /usr/portage/dev-lang/ruby/Manifest
>
> say?
>
> if resyncing absolutely does not work, you can compare the SHA256 of
> the ebuild on your two computers and if they are the same it should be
> relatively safe to do
>
> ebuild /usr/portage/dev-lang/ruby/ruby-1.8.7_p352.ebuild manifest
>
> which will rebuild the Manifest file containing the filesize and the
> checksums and after that you can emerge.
I removed the manifest resync'ed and it emerged without any errors.
Thank you! :-)
--
Regards,
Mick
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [gentoo-user] pam-1.1.4 emerge error on x86
2011-10-15 17:17 ` Mick
@ 2011-10-15 17:27 ` Jonas de Buhr
2011-10-15 18:50 ` Mick
0 siblings, 1 reply; 8+ messages in thread
From: Jonas de Buhr @ 2011-10-15 17:27 UTC (permalink / raw
To: gentoo-user
Am Sat, 15 Oct 2011 18:17:41 +0100
schrieb Mick <michaelkintzios@gmail.com>:
> On Saturday 15 Oct 2011 14:09:46 Jonas de Buhr wrote:
> > Am Sat, 15 Oct 2011 13:24:02 +0100
> >
> > schrieb Mick <michaelkintzios@gmail.com>:
> > > On Saturday 15 Oct 2011 00:20:14 Jonas de Buhr wrote:
> > > > Am Sat, 15 Oct 2011 00:01:04 +0100
> > > >
> > > > schrieb Mick <michaelkintzios@gmail.com>:
> > > > > Have you seen this before?
> > > > >
> > > > > `/var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4'
> > > > > make[1]: Leaving directory
> > > > > `/var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4'
> > > > > /var/tmp/portage/sys-libs/pam-1.1.4/temp/environment: line
> > > > > 2226: scanelf: command not found
> > > >
> > > > you could try reinstalling app-misc/pax-utils.
> > > >
> > > > this is either a missing dependency or for some reason your
> > > > pax-utils install is broken.
> > >
> > > Thank you! I've remerged pax-utils. This is an old laptop and
> > > both the main battery and CMOS battery have run out of juice. I
> > > noticed that the clock was out by more than 100 years - but I
> > > think that I had sync'ed portage in the meanwhile.
> > >
> > > I have not been able to proceed with pam, because world now wants
> > > to
> > >
> > > emerge ruby. However, it comes up with this error:
> > > >>> Verifying ebuild manifests
> > >
> > > !!! Digest verification failed:
> > > !!! /usr/portage/dev-lang/ruby/ruby-1.8.7_p352.ebuild
> > > !!! Reason: Filesize does not match recorded size
> > > !!! Got: 5574
> > > !!! Expected: 5569
> > >
> > > I've deleted the ebuild, then resync'ed twice with different
> > > mirrors and the error persists. Another box I have (which does
> > > not come up with this error) shows:
> > >
> > > $ ls -la /usr/portage/dev-lang/ruby/ruby-1.8.7_p352.ebuild
> > > -rw-r--r-- 1 root root 5574 Oct 14 09:31 /usr/portage/dev-
> > > lang/ruby/ruby-1.8.7_p352.ebuild
> > >
> > > So, is 5574 the wrong size, or is the ebuild file in the latest
> > > sync'ing of portage wrong?
> >
> > did you delete just the ebuild or the Manifest too? i suspect that
> > due to wrong date setting portage did not update the Manifest file
> > which contains the filesize.
> >
> > rm -rf /usr/portage/dev-lang/ruby && emerge --sync
> >
> > should help in that case. but you might run into more date related
> > update problems later. maybe you should correct your date and
> > extract a portage snapshot and sync to get rid of those problems
> > once and for all.
> >
> > my
> > /usr/portage/dev-lang/ruby/Manifest
> > says
> >
> > EBUILD ruby-1.8.7_p352.ebuild 5574 RMD160
> > e822545306c9e2b2a17767895b851f72c772a149 SHA1
> > 0117f543aa6d7ae064af74af7199deefe6e0dc9d SHA256
> > 79d0f2b28b0b39bf23b9208071f7d50f04a6d76254f42073b2b3e9cc612955a7
> >
> > so 5574 should be the correct filesize. what does
> >
> > grep ruby-1.8.7_p352 /usr/portage/dev-lang/ruby/Manifest
> >
> > say?
> >
> > if resyncing absolutely does not work, you can compare the SHA256 of
> > the ebuild on your two computers and if they are the same it should
> > be relatively safe to do
> >
> > ebuild /usr/portage/dev-lang/ruby/ruby-1.8.7_p352.ebuild manifest
> >
> > which will rebuild the Manifest file containing the filesize and the
> > checksums and after that you can emerge.
>
> I removed the manifest resync'ed and it emerged without any errors.
>
> Thank you! :-)
you're welcome ;)
its really easy to help you because you provide the right information =)
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [gentoo-user] pam-1.1.4 emerge error on x86
2011-10-15 17:27 ` Jonas de Buhr
@ 2011-10-15 18:50 ` Mick
2011-10-16 12:56 ` Jonas de Buhr
0 siblings, 1 reply; 8+ messages in thread
From: Mick @ 2011-10-15 18:50 UTC (permalink / raw
To: gentoo-user
[-- Attachment #1: Type: Text/Plain, Size: 1548 bytes --]
On Saturday 15 Oct 2011 18:27:50 Jonas de Buhr wrote:
> Am Sat, 15 Oct 2011 18:17:41 +0100
>
> schrieb Mick <michaelkintzios@gmail.com>:
> > On Saturday 15 Oct 2011 14:09:46 Jonas de Buhr wrote:
> > > Am Sat, 15 Oct 2011 13:24:02 +0100
> > >
> > > schrieb Mick <michaelkintzios@gmail.com>:
> > > > On Saturday 15 Oct 2011 00:20:14 Jonas de Buhr wrote:
> > > > > Am Sat, 15 Oct 2011 00:01:04 +0100
> > > > >
> > > > > schrieb Mick <michaelkintzios@gmail.com>:
> > > > > > Have you seen this before?
> > > > > >
> > > > > > `/var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4'
> > > > > > make[1]: Leaving directory
> > > > > > `/var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4'
> > > > > > /var/tmp/portage/sys-libs/pam-1.1.4/temp/environment: line
> > > > > > 2226: scanelf: command not found
> > > > >
> > > > > you could try reinstalling app-misc/pax-utils.
> > > > >
> > > > > this is either a missing dependency or for some reason your
> > > > > pax-utils install is broken.
> > > >
> > > > Thank you! I've remerged pax-utils. This is an old laptop and
> > > > both the main battery and CMOS battery have run out of juice. I
> > > > noticed that the clock was out by more than 100 years - but I
> > > > think that I had sync'ed portage in the meanwhile.
[snip...]
> > Thank you! :-)
>
> you're welcome ;)
> its really easy to help you because you provide the right information =)
To save me asking next time ... how did you know that pax-utils was to blame?
--
Regards,
Mick
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [gentoo-user] pam-1.1.4 emerge error on x86
2011-10-15 18:50 ` Mick
@ 2011-10-16 12:56 ` Jonas de Buhr
0 siblings, 0 replies; 8+ messages in thread
From: Jonas de Buhr @ 2011-10-16 12:56 UTC (permalink / raw
To: gentoo-user
Am Sat, 15 Oct 2011 19:50:23 +0100
schrieb Mick <michaelkintzios@gmail.com>:
>[snip snip]
> [snip...]
>
> > > Thank you! :-)
> >
> > you're welcome ;)
> > its really easy to help you because you provide the right
> > information =)
>
> To save me asking next time ... how did you know that pax-utils was
> to blame?
i saw this error:
> /var/tmp/portage/sys-libs/pam-1.1.4/temp/environment: line 2226:
> scanelf: command not found
> * ERROR: sys-libs/pam-1.1.4 failed (install phase):
and with
% equery b scanelf
* Searching for scanelf ...
app-misc/pax-utils-0.2.2 (/usr/bin/scanelf)
i knew that it belonged to pax-utils. that only works, if a package
owning that binary is installed. if there wasn't, i would have used a
web search engine. the results normally contain man pages saying which
package the command belongs to.
that means either /usr/bin/scanelf is missing or /usr/bin is not in the
path (at least not in the environment of portage). i thought the latter
would be unlikely :)
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2011-10-16 12:57 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-10-14 23:01 [gentoo-user] pam-1.1.4 emerge error on x86 Mick
2011-10-14 23:20 ` Jonas de Buhr
2011-10-15 12:24 ` Mick
2011-10-15 13:09 ` Jonas de Buhr
2011-10-15 17:17 ` Mick
2011-10-15 17:27 ` Jonas de Buhr
2011-10-15 18:50 ` Mick
2011-10-16 12:56 ` Jonas de Buhr
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox