From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1RKCCw-0004Up-8R for garchives@archives.gentoo.org; Sat, 29 Oct 2011 16:56:34 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id B7E7821C09F; Sat, 29 Oct 2011 16:56:18 +0000 (UTC) Received: from mail-fx0-f53.google.com (mail-fx0-f53.google.com [209.85.161.53]) by pigeon.gentoo.org (Postfix) with ESMTP id 396C921C035 for ; Sat, 29 Oct 2011 16:55:17 +0000 (UTC) Received: by faai28 with SMTP id i28so5601791faa.40 for ; Sat, 29 Oct 2011 09:55:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=7hmdLWJVfWaBy+bXtSxAT8XWfZwFMQ0fxDvaQ8qHqOk=; b=BHVWAQViQ2gHp+b9yVznHNLsQJasj00ujmTgwnj7rRYRUyWnWkqCNoMCuSCuZChajg 9JN+Ucq1QxSLwGgn0kTDQ9RAKajscP7xQwDR9tmIUt/dFtuYF9yznZXu9LNwnqdp13Ue koPgh9RqA0xz0TOZIjDS0YO6IkizMTD4Uf4WM= Received: by 10.223.5.201 with SMTP id 9mr15531659faw.5.1319907317254; Sat, 29 Oct 2011 09:55:17 -0700 (PDT) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Received: by 10.152.36.170 with HTTP; Sat, 29 Oct 2011 09:54:56 -0700 (PDT) In-Reply-To: References: From: co Date: Sun, 30 Oct 2011 00:54:56 +0800 Message-ID: Subject: Re: [gentoo-user] problem with pam To: gentoo-user@lists.gentoo.org Content-Type: multipart/alternative; boundary=000e0ce0ceaac809e504b072de6a X-Archives-Salt: X-Archives-Hash: 9fc22690a4aa27b9778df4a03e91c9c1 --000e0ce0ceaac809e504b072de6a Content-Type: text/plain; charset=ISO-8859-1 emerge --info Traceback (most recent call last): File "/usr/bin/emerge", line 43, in retval = emerge_main() File "/usr/lib64/portage/pym/_emerge/main.py", line 1879, in emerge_main return action_info(settings, trees, myopts, valid_atoms) File "/usr/lib64/portage/pym/_emerge/actions.py", line 1407, in action_info repo = vardb.aux_get(cpv, ["repository"])[0] File "/usr/lib64/portage/pym/portage/dbapi/vartree.py", line 659, in aux_get self._aux_get(mycpv, aux_keys, st=mydir_stat)): File "/usr/lib64/portage/pym/portage/dbapi/vartree.py", line 690, in _aux_get raise KeyError(mycpv) KeyError: u'dev-lang/python-3.1.4-r3' 2011/10/29 co > > > These are the packages that would be merged, in order: > > Calculating dependencies .... done! > [ebuild R ] sys-libs/pam-1.1.5 USE="berkdb cracklib nls vim-syntax > -audit -debug -nis (-selinux) -test" 0 kB > > Total: 1 package (1 reinstall), Size of downloads: 0 kB > > > >>> Verifying ebuild manifests > > >>> Emerging (1 of 1) sys-libs/pam-1.1.5 > * Linux-PAM-1.1.5.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [ > ok ] > * Linux-PAM-1.1.5-docs.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [ > ok ] > >>> Unpacking source... > >>> Unpacking Linux-PAM-1.1.5.tar.bz2 to > /var/tmp/portage/sys-libs/pam-1.1.5/work > tar: Linux-PAM-1.1.5/INSTALL: Cannot open: Invalid argument > tar: Linux-PAM-1.1.5/ABOUT-NLS: Cannot open: Invalid argument > tar: Linux-PAM-1.1.5/ChangeLog: Cannot open: Invalid argument > tar: Linux-PAM-1.1.5/COPYING: Cannot open: Invalid argument > tar: Linux-PAM-1.1.5/Make.xml.rules: Cannot open: Invalid argument > tar: Exiting with failure status due to previous errors > /usr/lib64/portage/bin/isolated-functions.sh: line 264: > /var/tmp/portage/sys-libs/pam-1.1.5/temp/logging/unpack: Invalid argument > * ERROR: sys-libs/pam-1.1.5 failed (unpack phase): > /usr/lib64/portage/bin/isolated-functions.sh: line 264: > /var/tmp/portage/sys-libs/pam-1.1.5/temp/logging/unpack: Invalid argument > * failure unpacking Linux-PAM-1.1.5.tar.bz2 > /usr/lib64/portage/bin/isolated-functions.sh: line 264: > /var/tmp/portage/sys-libs/pam-1.1.5/temp/logging/unpack: Invalid argument > * > /usr/lib64/portage/bin/isolated-functions.sh: line 264: > /var/tmp/portage/sys-libs/pam-1.1.5/temp/logging/unpack: Invalid argument > * Call stack: > /usr/lib64/portage/bin/isolated-functions.sh: line 264: > /var/tmp/portage/sys-libs/pam-1.1.5/temp/logging/unpack: Invalid argument > * ebuild.sh, line 56: Called src_unpack > /usr/lib64/portage/bin/isolated-functions.sh: line 264: > /var/tmp/portage/sys-libs/pam-1.1.5/temp/logging/unpack: Invalid argument > * environment, line 3487: Called _eapi0_src_unpack > /usr/lib64/portage/bin/isolated-functions.sh: line 264: > /var/tmp/portage/sys-libs/pam-1.1.5/temp/logging/unpack: Invalid argument > * ebuild.sh, line 622: Called unpack > 'Linux-PAM-1.1.5.tar.bz2' 'Linux-PAM-1.1.5-docs.tar.bz2' > /usr/lib64/portage/bin/isolated-functions.sh: line 264: > /var/tmp/portage/sys-libs/pam-1.1.5/temp/logging/unpack: Invalid argument > * ebuild.sh, line 401: Called _unpack_tar 'bzip2 -d' > /usr/lib64/portage/bin/isolated-functions.sh: line 264: > /var/tmp/portage/sys-libs/pam-1.1.5/temp/logging/unpack: Invalid argument > * ebuild.sh, line 371: Called assert_sigpipe_ok 'failure > unpacking Linux-PAM-1.1.5.tar.bz2' > /usr/lib64/portage/bin/isolated-functions.sh: line 264: > /var/tmp/portage/sys-libs/pam-1.1.5/temp/logging/unpack: Invalid argument > * isolated-functions.sh, line 37: Called die > /usr/lib64/portage/bin/isolated-functions.sh: line 264: > /var/tmp/portage/sys-libs/pam-1.1.5/temp/logging/unpack: Invalid argument > * The specific snippet of code: > /usr/lib64/portage/bin/isolated-functions.sh: line 264: > /var/tmp/portage/sys-libs/pam-1.1.5/temp/logging/unpack: Invalid argument > * [[ $x -ne 0 && $x -ne ${PORTAGE_SIGPIPE_STATUS:-141} ]] && die "$@" > /usr/lib64/portage/bin/isolated-functions.sh: line 264: > /var/tmp/portage/sys-libs/pam-1.1.5/temp/logging/unpack: Invalid argument > * > /usr/lib64/portage/bin/isolated-functions.sh: line 264: > /var/tmp/portage/sys-libs/pam-1.1.5/temp/logging/unpack: Invalid argument > * If you need support, post the output of 'emerge --info > =sys-libs/pam-1.1.5', > /usr/lib64/portage/bin/isolated-functions.sh: line 264: > /var/tmp/portage/sys-libs/pam-1.1.5/temp/logging/unpack: Invalid argument > * the complete build log and the output of 'emerge -pqv > =sys-libs/pam-1.1.5'. > /usr/lib64/portage/bin/isolated-functions.sh: line 211: > /var/tmp/portage/sys-libs/pam-1.1.5/.die_hooks: Invalid argument > /usr/lib64/portage/bin/isolated-functions.sh: line 264: > /var/tmp/portage/sys-libs/pam-1.1.5/temp/logging/unpack: Invalid argument > * The complete build log is located at > '/var/tmp/portage/sys-libs/pam-1.1.5/temp/build.log'. > /usr/lib64/portage/bin/isolated-functions.sh: line 264: > /var/tmp/portage/sys-libs/pam-1.1.5/temp/logging/unpack: Invalid argument > * The ebuild environment file is located at > '/var/tmp/portage/sys-libs/pam-1.1.5/temp/environment'. > /usr/lib64/portage/bin/isolated-functions.sh: line 264: > /var/tmp/portage/sys-libs/pam-1.1.5/temp/logging/unpack: Invalid argument > * S: '/var/tmp/portage/sys-libs/pam-1.1.5/work/Linux-PAM-1.1.5' > Traceback (most recent call last): > File "/usr/lib64/portage/bin/ebuild-ipc.py", line 276, in > sys.exit(ebuild_ipc_main(sys.argv[1:])) > File "/usr/lib64/portage/bin/ebuild-ipc.py", line 273, in ebuild_ipc_main > return ebuild_ipc.communicate(args) > File "/usr/lib64/portage/bin/ebuild-ipc.py", line 63, in communicate > lock_obj = portage.locks.lockfile(self.ipc_lock_file, unlinkfile=True) > File "/usr/lib64/portage/pym/portage/locks.py", line 73, in lockfile > myfd = os.open(lockfilename, os.O_CREAT|os.O_RDWR, 0o660) > File "/usr/lib64/portage/pym/portage/__init__.py", line 215, in __call__ > rval = self._func(*wrapped_args, **wrapped_kwargs) > OSError: [Errno 22] Invalid argument: > '/var/tmp/portage/sys-libs/pam-1.1.5/.ipc_lock' > * The ebuild phase 'unpack' has exited unexpectedly. This type of behavior > * is known to be triggered by things such as failed variable assignments > * (bug #190128) or bad substitution errors (bug #200313). Normally, before > * exiting, bash should have displayed an error message above. If bash did > * not produce an error message above, it's possible that the ebuild has > * called `exit` when it should have called `die` instead. This behavior > * may also be triggered by a corrupt bash binary or a hardware problem > * such as memory or cpu malfunction. If the problem is not reproducible or > * it appears to occur randomly, then it is likely to be triggered by a > * hardware problem. If you suspect a hardware problem then you should try > * some basic hardware diagnostics such as memtest. Please do not report > * this as a bug unless it is consistently reproducible and you are sure > * that your bash binary and hardware are functioning properly. > /usr/lib64/portage/bin/misc-functions.sh: line 978: > /var/tmp/portage/sys-libs/pam-1.1.5/.die_hooks: Invalid argument > Traceback (most recent call last): > File "/usr/lib64/portage/bin/ebuild-ipc.py", line 276, in > sys.exit(ebuild_ipc_main(sys.argv[1:])) > File "/usr/lib64/portage/bin/ebuild-ipc.py", line 273, in ebuild_ipc_main > return ebuild_ipc.communicate(args) > File "/usr/lib64/portage/bin/ebuild-ipc.py", line 63, in communicate > lock_obj = portage.locks.lockfile(self.ipc_lock_file, unlinkfile=True) > File "/usr/lib64/portage/pym/portage/locks.py", line 73, in lockfile > myfd = os.open(lockfilename, os.O_CREAT|os.O_RDWR, 0o660) > File "/usr/lib64/portage/pym/portage/__init__.py", line 215, in __call__ > rval = self._func(*wrapped_args, **wrapped_kwargs) > OSError: [Errno 22] Invalid argument: > '/var/tmp/portage/sys-libs/pam-1.1.5/.ipc_lock' > * The ebuild phase 'die_hooks' has exited unexpectedly. This type of > * behavior is known to be triggered by things such as failed variable > * assignments (bug #190128) or bad substitution errors (bug #200313). > * Normally, before exiting, bash should have displayed an error message > * above. If bash did not produce an error message above, it's possible > * that the ebuild has called `exit` when it should have called `die` > * instead. This behavior may also be triggered by a corrupt bash binary or > * a hardware problem such as memory or cpu malfunction. If the problem is > * not reproducible or it appears to occur randomly, then it is likely to > * be triggered by a hardware problem. If you suspect a hardware problem > * then you should try some basic hardware diagnostics such as memtest. > * Please do not report this as a bug unless it is consistently > * reproducible and you are sure that your bash binary and hardware are > * functioning properly. > > >>> Failed to emerge sys-libs/pam-1.1.5, Log file: > > >>> '/var/tmp/portage/sys-libs/pam-1.1.5/temp/build.log' > > * Messages for package sys-libs/pam-1.1.5: > > 2011/10/29 co > >> #ldd /sbin/rc >> linux-vdso.so.1 => (0x00007fff69fff000) >> libutil.so.1 => /lib64/libutil.so.1 (0x00007f617f00d000) >> librc.so.1 => /lib64/librc.so.1 (0x00007f617ee01000) >> libeinfo.so.1 => /lib64/libeinfo.so.1 (0x00007f617ebfb000) >> libdl.so.2 => /lib64/libdl.so.2 (0x00007f617e9f7000) >> libpam.so.0 => not found >> libc.so.6 => /lib64/libc.so.6 (0x00007f617e691000) >> libncurses.so.5 => /lib64/libncurses.so.5 (0x00007f617e440000) >> /lib64/ld-linux-x86-64.so.2 (0x00007f617f210000) >> thank you ahead. >> >> >> 2011/10/29 Adam Carter >> >>> > And i try to re-emerge pam,but i can't >>> >>> With the old file and links there I don't understand why your system >>> doesn't work, but re-emerging pam it definitely worth trying. What >>> fails when you try to re-emerge? >>> >>> Also, what about >>> # ldd /sbin/rc >>> >>> >> > --000e0ce0ceaac809e504b072de6a Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable emerge --info
Traceback (most recent call last):=A0
=A0 File "/usr/bin/emerge", line 43, in <module>=A0=
=A0 =A0 retval =3D emerge_main()=A0
=A0 File "/usr/lib64/portage/pym/_emerge/main.py", line 1879, in= emerge_main=A0
=A0 =A0 return action_info(settings, trees, myopts, valid_atoms)=A0=
=A0 File "/usr/lib64/portage/pym/_emerge/actions.py", line 1407,= in action_info=A0
=A0 =A0 repo =3D vardb.aux_get(cpv, ["repository"])[0]=A0=
=A0 File "/usr/lib64/portage/pym/portage/dbapi/vartree.py", line= 659, in aux_get=A0
=A0 =A0 self._aux_get(mycpv, aux_keys, st=3Dmydir_stat)):=A0
=A0 File "/usr/lib64/portage/pym/portage/dbapi/vartree.py", line= 690, in _aux_get=A0
=A0 =A0 raise KeyError(mycpv)=A0
KeyError: u'dev-lang/python-3.1.4-r3'

2011/10/29 co <cui= cle@gmail.com>

These are the packages that would be merged, in order:

<= /div>
Calculating dependencies =A0.... done!
[ebuild =A0 R = =A0 =A0] sys-libs/pam-1.1.5 =A0USE=3D"berkdb cracklib nls vim-syntax -= audit -debug -nis (-selinux) -test" 0 kB

Total: 1 package (1 reinstall), Size of downloads: 0 kB=


>>> Verifying ebuild mani= fests

>>> Emerging (1 of 1) sys-libs/pam-= 1.1.5
=A0* Linux-PAM-1.1.5.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... =A0 =A0 = =A0 =A0 =A0 =A0 =A0 [ ok ]
=A0* Linux-PAM-1.1.5-docs.tar.bz2 RMD1= 60 SHA1 SHA256 size ;-) ... =A0 =A0 =A0 =A0 =A0[ ok ]
>>>= ; Unpacking source...
>>> Unpacking Linux-PAM-1.1.5.tar.bz2 to /var/tmp/portage/sys= -libs/pam-1.1.5/work
tar: Linux-PAM-1.1.5/INSTALL: Cannot open: I= nvalid argument
tar: Linux-PAM-1.1.5/ABOUT-NLS: Cannot open: Inva= lid argument
tar: Linux-PAM-1.1.5/ChangeLog: Cannot open: Invalid argument
tar: Linux-PAM-1.1.5/COPYING: Cannot open: Invalid argument
tar= : Linux-PAM-1.1.5/Make.xml.rules: Cannot open: Invalid argument
tar: Exiting with failure status due to previous errors
/usr/lib6= 4/portage/bin/isolated-functions.sh: line 264: /var/tmp/portage/sys-libs/pa= m-1.1.5/temp/logging/unpack: Invalid argument
=A0* ERROR: sys-lib= s/pam-1.1.5 failed (unpack phase):
/usr/lib64/portage/bin/isolated-functions.sh: line 264: /var/tmp/porta= ge/sys-libs/pam-1.1.5/temp/logging/unpack: Invalid argument
=A0* = =A0 failure unpacking Linux-PAM-1.1.5.tar.bz2
/usr/lib64/portage/= bin/isolated-functions.sh: line 264: /var/tmp/portage/sys-libs/pam-1.1.5/te= mp/logging/unpack: Invalid argument
=A0*=A0
/usr/lib64/portage/bin/isolated-functions.sh: line 2= 64: /var/tmp/portage/sys-libs/pam-1.1.5/temp/logging/unpack: Invalid argume= nt
=A0* Call stack:
/usr/lib64/portage/bin/isolated-fun= ctions.sh: line 264: /var/tmp/portage/sys-libs/pam-1.1.5/temp/logging/unpac= k: Invalid argument
=A0* =A0 =A0 =A0 =A0 =A0 =A0 =A0 ebuild.sh, line =A0 56: =A0Called src= _unpack
/usr/lib64/portage/bin/isolated-functions.sh: line 264: /= var/tmp/portage/sys-libs/pam-1.1.5/temp/logging/unpack: Invalid argument
=A0* =A0 =A0 =A0 =A0 =A0 =A0 environment, line 3487: =A0Called _eap= i0_src_unpack
/usr/lib64/portage/bin/isolated-functions.sh: line 264: /var/tmp/porta= ge/sys-libs/pam-1.1.5/temp/logging/unpack: Invalid argument
=A0* = =A0 =A0 =A0 =A0 =A0 =A0 =A0 ebuild.sh, line =A0622: =A0Called unpack 'L= inux-PAM-1.1.5.tar.bz2' 'Linux-PAM-1.1.5-docs.tar.bz2'
/usr/lib64/portage/bin/isolated-functions.sh: line 264: /var/tmp/porta= ge/sys-libs/pam-1.1.5/temp/logging/unpack: Invalid argument
=A0* = =A0 =A0 =A0 =A0 =A0 =A0 =A0 ebuild.sh, line =A0401: =A0Called _unpack_tar &= #39;bzip2 -d'
/usr/lib64/portage/bin/isolated-functions.sh: line 264: /var/tmp/porta= ge/sys-libs/pam-1.1.5/temp/logging/unpack: Invalid argument
=A0* = =A0 =A0 =A0 =A0 =A0 =A0 =A0 ebuild.sh, line =A0371: =A0Called assert_sigpip= e_ok 'failure unpacking Linux-PAM-1.1.5.tar.bz2'
/usr/lib64/portage/bin/isolated-functions.sh: line 264: /var/tmp/porta= ge/sys-libs/pam-1.1.5/temp/logging/unpack: Invalid argument
=A0* = =A0 isolated-functions.sh, line =A0 37: =A0Called die
/usr/lib64/= portage/bin/isolated-functions.sh: line 264: /var/tmp/portage/sys-libs/pam-= 1.1.5/temp/logging/unpack: Invalid argument
=A0* The specific snippet of code:
/usr/lib64/portage/bin/is= olated-functions.sh: line 264: /var/tmp/portage/sys-libs/pam-1.1.5/temp/log= ging/unpack: Invalid argument
=A0* =A0 [[ $x -ne 0 && $x -ne ${PORTAGE_SIGPIPE_STATUS:= -141} ]] && die "$@"
/usr/lib64/portage/bin/isolated-functions.sh: line 264: /var/tmp/porta= ge/sys-libs/pam-1.1.5/temp/logging/unpack: Invalid argument
=A0*= =A0
/usr/lib64/portage/bin/isolated-functions.sh: line 264: /var/= tmp/portage/sys-libs/pam-1.1.5/temp/logging/unpack: Invalid argument
=A0* If you need support, post the output of 'emerge --info =3Dsys= -libs/pam-1.1.5',
/usr/lib64/portage/bin/isolated-functions.s= h: line 264: /var/tmp/portage/sys-libs/pam-1.1.5/temp/logging/unpack: Inval= id argument
=A0* the complete build log and the output of 'emerge -pqv =3Dsys-= libs/pam-1.1.5'.
/usr/lib64/portage/bin/isolated-functions.sh= : line 211: /var/tmp/portage/sys-libs/pam-1.1.5/.die_hooks: Invalid argumen= t
/usr/lib64/portage/bin/isolated-functions.sh: line 264: /var/tmp/porta= ge/sys-libs/pam-1.1.5/temp/logging/unpack: Invalid argument
=A0* = The complete build log is located at '/var/tmp/portage/sys-libs/pam-1.1= .5/temp/build.log'.
/usr/lib64/portage/bin/isolated-functions.sh: line 264: /var/tmp/porta= ge/sys-libs/pam-1.1.5/temp/logging/unpack: Invalid argument
=A0* = The ebuild environment file is located at '/var/tmp/portage/sys-libs/pa= m-1.1.5/temp/environment'.
/usr/lib64/portage/bin/isolated-functions.sh: line 264: /var/tmp/porta= ge/sys-libs/pam-1.1.5/temp/logging/unpack: Invalid argument
=A0* = S: '/var/tmp/portage/sys-libs/pam-1.1.5/work/Linux-PAM-1.1.5'
Traceback (most recent call last):
=A0 File "/usr/lib64= /portage/bin/ebuild-ipc.py", line 276, in <module>
=A0= =A0 sys.exit(ebuild_ipc_main(sys.argv[1:]))
=A0 File "/usr/= lib64/portage/bin/ebuild-ipc.py", line 273, in ebuild_ipc_main
=A0 =A0 return ebuild_ipc.communicate(args)
=A0 File "/= usr/lib64/portage/bin/ebuild-ipc.py", line 63, in communicate
=A0 =A0 lock_obj =3D portage.locks.lockfile(self.ipc_lock_file, unlinkfil= e=3DTrue)
=A0 File "/usr/lib64/portage/pym/portage/locks.py", line 73,= in lockfile
=A0 =A0 myfd =3D os.open(lockfilename, os.O_CREAT|os= .O_RDWR, 0o660)
=A0 File "/usr/lib64/portage/pym/portage/__i= nit__.py", line 215, in __call__
=A0 =A0 rval =3D self._func(*wrapped_args, **wrapped_kwargs)
OSError: [Errno 22] Invalid argument: '/var/tmp/portage/sys-libs/pam-1= .1.5/.ipc_lock'
=A0* The ebuild phase 'unpack' has ex= ited unexpectedly. This type of behavior
=A0* is known to be triggered by things such as failed variable assign= ments
=A0* (bug #190128) or bad substitution errors (bug #200313)= . Normally, before
=A0* exiting, bash should have displayed an er= ror message above. If bash did
=A0* not produce an error message above, it's possible that the eb= uild has
=A0* called `exit` when it should have called `die` inst= ead. This behavior
=A0* may also be triggered by a corrupt bash b= inary or a hardware problem
=A0* such as memory or cpu malfunction. If the problem is not reproduc= ible or
=A0* it appears to occur randomly, then it is likely to b= e triggered by a
=A0* hardware problem. If you suspect a hardware= problem then you should try
=A0* some basic hardware diagnostics such as memtest. Please do not re= port
=A0* this as a bug unless it is consistently reproducible an= d you are sure
=A0* that your bash binary and hardware are functi= oning properly.
/usr/lib64/portage/bin/misc-functions.sh: line 978: /var/tmp/portage/s= ys-libs/pam-1.1.5/.die_hooks: Invalid argument
Traceback (most re= cent call last):
=A0 File "/usr/lib64/portage/bin/ebuild-ipc= .py", line 276, in <module>
=A0 =A0 sys.exit(ebuild_ipc_main(sys.argv[1:]))
=A0 File &qu= ot;/usr/lib64/portage/bin/ebuild-ipc.py", line 273, in ebuild_ipc_main=
=A0 =A0 return ebuild_ipc.communicate(args)
=A0 File &= quot;/usr/lib64/portage/bin/ebuild-ipc.py", line 63, in communicate
=A0 =A0 lock_obj =3D portage.locks.lockfile(self.ipc_lock_file, unlink= file=3DTrue)
=A0 File "/usr/lib64/portage/pym/portage/locks.= py", line 73, in lockfile
=A0 =A0 myfd =3D os.open(lockfilen= ame, os.O_CREAT|os.O_RDWR, 0o660)
=A0 File "/usr/lib64/portage/pym/portage/__init__.py", line = 215, in __call__
=A0 =A0 rval =3D self._func(*wrapped_args, **wra= pped_kwargs)
OSError: [Errno 22] Invalid argument: '/var/tmp/= portage/sys-libs/pam-1.1.5/.ipc_lock'
=A0* The ebuild phase 'die_hooks' has exited unexpectedly. Thi= s type of
=A0* behavior is known to be triggered by things such a= s failed variable
=A0* assignments (bug #190128) or bad substitut= ion errors (bug #200313).
=A0* Normally, before exiting, bash should have displayed an error mes= sage
=A0* above. If bash did not produce an error message above, = it's possible
=A0* that the ebuild has called `exit` when it = should have called `die`
=A0* instead. This behavior may also be triggered by a corrupt bash bi= nary or
=A0* a hardware problem such as memory or cpu malfunction= . If the problem is
=A0* not reproducible or it appears to occur = randomly, then it is likely to
=A0* be triggered by a hardware problem. If you suspect a hardware pro= blem
=A0* then you should try some basic hardware diagnostics suc= h as memtest.
=A0* Please do not report this as a bug unless it i= s consistently
=A0* reproducible and you are sure that your bash binary and hardware = are
=A0* functioning properly.

>>&= gt; Failed to emerge sys-libs/pam-1.1.5, Log file:

>>> =A0'/var/tmp/portage/sys-libs/pam-1.1.5/temp/build.log'= ;

=A0* Messages for package sys-libs/pam-1.1.5:

2011/10/29 co <cuicle@gmail.com>
#ldd /sbin/rc
linux-vdso.so.1 =3D> =A0(0x00007fff69fff00= 0)
libutil.so.1 =3D> /lib= 64/libutil.so.1 (0x00007f617f00d000)
librc.so.1 =3D> /lib64= /librc.so.1 (0x00007f617ee01000)
libeinfo.so.1 =3D> /lib64/libeinfo.so.1 (0x00007f617ebfb000= )
libdl.so.2 =3D> /lib64= /libdl.so.2 (0x00007f617e9f7000)
libpam.so.0 =3D> not found
libc.so.6 =3D> /lib64/= libc.so.6 (0x00007f617e691000)
libncurses.so.5 =3D> /lib64/libncurses.so.5 (0x00007f617e4400= 00)
/lib64/ld-linux-x86-64.so= .2 (0x00007f617f210000)
thank you ahead.


2011/10/29 Adam Carter <adamcarter3@gmail.com>
> And i try to re-emerge pam,but i c= an't

With the old file and links there I don't understand why your sys= tem
doesn't work, but re-emerging pam it definitely worth trying. What
fails when you try to re-emerge?

Also, what about
# ldd /sbin/rc




--000e0ce0ceaac809e504b072de6a--