[gentoo-user] problem with pam
I upgrade pad to 1.1.5 ,then openrc can't work,and can't login to system. libpam.so.0 can't open shared object file. please help!
Re: [gentoo-user] problem with pam
lrwxrwxrwx 1 root root11 Oct 21 23:47 /lib32/libpam.so - libpam.so.0 lrwxrwxrwx 1 root root16 Oct 21 23:48 /lib32/libpam.so.0 - libpam.so.0.83.0 -rwxr-xr-x 1 root root 46520 Sep 28 19:37 /lib32/libpam.so.0.83.0 2011/10/29 Adam Carter adamcart...@gmail.com On Sat, Oct 29, 2011 at 8:55 PM, co cui...@gmail.com wrote: I upgrade pad to 1.1.5 ,then openrc can't work,and can't login to system. libpam.so.0 can't open shared object file. please help! I always run revdep-rebuild any time libs are updated, but in this case the lib name stays the same. What do you see if you run this command? # ls -l /lib/libpam.so* lrwxrwxrwx 1 root root11 Oct 29 17:49 /lib/libpam.so - libpam.so.0 lrwxrwxrwx 1 root root16 Oct 29 17:49 /lib/libpam.so.0 - libpam.so.0.83.1 -rwxr-xr-x 1 root root 55712 Oct 29 17:49 /lib/libpam.so.0.83.1
Re: [gentoo-user] problem with pam
And when i revdep-rebuild ,it still warning libpam.so.0,when finished ,it still can't work. And i try to re-emerge pam,but i can't 2011/10/29 co cui...@gmail.com lrwxrwxrwx 1 root root11 Oct 21 23:47 /lib32/libpam.so - libpam.so.0 lrwxrwxrwx 1 root root16 Oct 21 23:48 /lib32/libpam.so.0 - libpam.so.0.83.0 -rwxr-xr-x 1 root root 46520 Sep 28 19:37 /lib32/libpam.so.0.83.0 2011/10/29 Adam Carter adamcart...@gmail.com On Sat, Oct 29, 2011 at 8:55 PM, co cui...@gmail.com wrote: I upgrade pad to 1.1.5 ,then openrc can't work,and can't login to system. libpam.so.0 can't open shared object file. please help! I always run revdep-rebuild any time libs are updated, but in this case the lib name stays the same. What do you see if you run this command? # ls -l /lib/libpam.so* lrwxrwxrwx 1 root root11 Oct 29 17:49 /lib/libpam.so - libpam.so.0 lrwxrwxrwx 1 root root16 Oct 29 17:49 /lib/libpam.so.0 - libpam.so.0.83.1 -rwxr-xr-x 1 root root 55712 Oct 29 17:49 /lib/libpam.so.0.83.1
Re: [gentoo-user] problem with pam
#ldd /sbin/rc linux-vdso.so.1 = (0x7fff69fff000) libutil.so.1 = /lib64/libutil.so.1 (0x7f617f00d000) librc.so.1 = /lib64/librc.so.1 (0x7f617ee01000) libeinfo.so.1 = /lib64/libeinfo.so.1 (0x7f617ebfb000) libdl.so.2 = /lib64/libdl.so.2 (0x7f617e9f7000) libpam.so.0 = not found libc.so.6 = /lib64/libc.so.6 (0x7f617e691000) libncurses.so.5 = /lib64/libncurses.so.5 (0x7f617e44) /lib64/ld-linux-x86-64.so.2 (0x7f617f21) thank you ahead. 2011/10/29 Adam Carter adamcart...@gmail.com 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
Re: [gentoo-user] problem with pam
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 module 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 cui...@gmail.com #ldd /sbin/rc linux-vdso.so.1 = (0x7fff69fff000) libutil.so.1 = /lib64/libutil.so.1 (0x7f617f00d000) librc.so.1 = /lib64/librc.so.1 (0x7f617ee01000) libeinfo.so.1 = /lib64/libeinfo.so.1 (0x7f617ebfb000) libdl.so.2 = /lib64/libdl.so.2 (0x7f617e9f7000) libpam.so.0 = not found libc.so.6 = /lib64/libc.so.6 (0x7f617e691000) libncurses.so.5 = /lib64/libncurses.so.5 (0x7f617e44) /lib64/ld-linux-x86-64.so.2 (0x7f617f21) thank you ahead. 2011/10/29 Adam Carter adamcart...@gmail.com 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
Re: [gentoo-user] problem with pam
emerge --info
Traceback (most recent call last):
File /usr/bin/emerge, line 43, in module
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 cui...@gmail.com
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
Re: [gentoo-user] problem with pam
My system is amd64,and livecd is amd64 too. I always chroot.And it's exf4. Wait a second,I will try it now.Thank you so much. 2011/10/30 Andrea Conti a...@alyf.net On 29/10/11 13.10, co wrote: # ls -l /lib/libpam.so* lrwxrwxrwx 1 root root11 Oct 21 23:47 /lib32/libpam.so - libpam.so.0 lrwxrwxrwx 1 root root16 Oct 21 23:48 /lib32/libpam.so.0 - libpam.so.0.83.0 -rwxr-xr-x 1 root root 46520 Sep 28 19:37 /lib32/libpam.so.0.83.0 That's not what you were asked for (ie /lib32 != /lib, as you seem to be on amd64). Are you by any chance trying to rescue your system by booting from an install cd? If so, make sure you use an amd64 ISO, and don't forget to chroot to your system installation. 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 I think this is the real problem. Whatever is causing this also has probably something to do with your openrc issues. What kind of filesystem is your /var/tmp/portage directory on? Is it free of errors? Is there any free space left? Can you create a new file on it? Try # echo test /var/tmp/portage/test andrea
Re: [gentoo-user] problem with pam
After I run e2fsck -c on /var partition.I have re-emerged pam. So I think there is something wrong with my hard disc. And there is still something Error and Warning on boot time,and after startx mouse can't move. So how to fix the hard disc now? Forgive my poor EnglishThank you again 2011/10/30 Andrea Conti a...@alyf.net On 29/10/11 13.10, co wrote: # ls -l /lib/libpam.so* lrwxrwxrwx 1 root root11 Oct 21 23:47 /lib32/libpam.so - libpam.so.0 lrwxrwxrwx 1 root root16 Oct 21 23:48 /lib32/libpam.so.0 - libpam.so.0.83.0 -rwxr-xr-x 1 root root 46520 Sep 28 19:37 /lib32/libpam.so.0.83.0 That's not what you were asked for (ie /lib32 != /lib, as you seem to be on amd64). Are you by any chance trying to rescue your system by booting from an install cd? If so, make sure you use an amd64 ISO, and don't forget to chroot to your system installation. 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 I think this is the real problem. Whatever is causing this also has probably something to do with your openrc issues. What kind of filesystem is your /var/tmp/portage directory on? Is it free of errors? Is there any free space left? Can you create a new file on it? Try # echo test /var/tmp/portage/test andrea
[gentoo-user] Gtk-Message: Failed to load module gnomesegvhandler
# gvim Gtk-Message: Failed to load module gnomesegvhandler # chromium Gtk-Message: Failed to load module gnomesegvhandler Both of them can work properly,but what's the problem with the warning?
[gentoo-user] Fwd: gnome-applets-python 装不上
can't emerge gnome-applets-python
what's the problem?
* ERROR: dev-python/gnome-applets-python-2.32.0 failed (compile phase):
* Building failed with CPython 2.7 in python_default_function() function
*
* Call stack:
* ebuild.sh, line 56: Called src_compile
* environment, line 6045: Called gnome-python-common_src_compile
* environment, line 3099: Called python_src_compile
* environment, line 5899: Called python_execute_function '-d' '-s' '--'
* environment, line 4352: Called die
* The specific snippet of code:
* die ${failure_message};
*
* If you need support, post the output of 'emerge --info
=dev-python/gnome-applets-python-2.32.0',
* the complete build log and the output of 'emerge -pqv
=dev-python/gnome-applets-python-2.32.0'.
* The complete build log is located at
'/var/tmp/portage/dev-python/gnome-applets-python-2.32.0/temp/build.log'.
* The ebuild environment file is located at
'/var/tmp/portage/dev-python/gnome-applets-python-2.32.0/temp/environment'.
* S:
'/var/tmp/portage/dev-python/gnome-applets-python-2.32.0/work/gnome-python-desktop-2.32.0'
Failed to emerge dev-python/gnome-applets-python-2.32.0, Log file:
'/var/tmp/portage/dev-python/gnome-applets-python-2.32.0/temp/build.log'
* Messages for package dev-python/gnome-applets-python-2.32.0:
* ERROR: dev-python/gnome-applets-python-2.32.0 failed (compile phase):
* Building failed with CPython 2.7 in python_default_function() function
*
* Call stack:
* ebuild.sh, line 56: Called src_compile
* environment, line 6045: Called gnome-python-common_src_compile
* environment, line 3099: Called python_src_compile
* environment, line 5899: Called python_execute_function '-d' '-s' '--'
* environment, line 4352: Called die
* The specific snippet of code:
* die ${failure_message};
*
* If you need support, post the output of 'emerge --info
=dev-python/gnome-applets-python-2.32.0',
* the complete build log and the output of 'emerge -pqv
=dev-python/gnome-applets-python-2.32.0'.
* The complete build log is located at
'/var/tmp/portage/dev-python/gnome-applets-python-2.32.0/temp/build.log'.
* The ebuild environment file is located at
'/var/tmp/portage/dev-python/gnome-applets-python-2.32.0/temp/environment'.
* S:
'/var/tmp/portage/dev-python/gnome-applets-python-2.32.0/work/gnome-python-desktop-2.32.0'
#emerge --info =dev-python/gnome-applets-python-2.32.0
Portage 2.1.10.11 (default/linux/amd64/10.0, gcc-4.4.5, glibc-2.12.2-r0,
2.6.39-gentoo-r3 x86_64)
=
System Settings
=
System uname: Linux-2.6.39-gentoo-r3-x86_64-Intel-R-_Core-TM-_i5_CPU_M_430_@
_2.27GHz-with-gentoo-2.0.3
Timestamp of tree: Fri, 21 Oct 2011 03:30:01 +
ccache version 2.4 [enabled]
app-shells/bash: 4.1_p9
dev-lang/python: 2.6.6-r2, 2.7.1-r1, 3.1.3-r1
dev-util/ccache: 2.4-r9
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, 2.68
sys-devel/automake: 1.11.1
sys-devel/binutils: 2.21.1-r1
sys-devel/gcc:4.4.5, 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
ACCEPT_KEYWORDS=amd64
ACCEPT_LICENSE=* -@EULA
CBUILD=x86_64-pc-linux-gnu
CFLAGS=-march=core2 -O2 -pipe
CHOST=x86_64-pc-linux-gnu
CONFIG_PROTECT=/etc
CONFIG_PROTECT_MASK=/etc/ca-certificates.conf /etc/dconf /etc/env.d
/etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/revdep-rebuild
/etc/sandbox.d /etc/terminfo
CXXFLAGS=-march=core2 -O2 -pipe
DISTDIR=/usr/portage/distfiles
EMERGE_DEFAULT_OPTS=--autounmask=n
FEATURES=assume-digests binpkg-logs ccache distlocks ebuild-locks
fixlafiles fixpackages news parallel-fetch protect-owned sandbox sfperms
strict unknown-features-warn unmerge-logs unmerge-orphans userfetch
FFLAGS=
GENTOO_MIRRORS=http://mirror.the-best-hosting.net/;
LANG=en_US.utf8
LDFLAGS=-Wl,-O1 -Wl,--as-needed
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=
SYNC=rsync://rsync.gentoo.org/gentoo-portage
USE=(mutilib) 64bit X acl amd64 berkdb bzip2 cairo cdda cli community
consolekit cracklib crypt cups cxx dbus device-mapper dri extras fontconfig
fortran gdbm gdu gnome gpm gtk hal iconv icu ipv6 jpeg mmx modules mudflap
multilib ncurses nls nptl nptlonly openmp pam pcre png policykit pppd python
qt readline session sqlite sqlite:3 sse sse2 ssl
[gentoo-user] Re: [gentoo-user] Fwd: gnome-applets-python 装不上
Thankyou, I found this
note: pygtk-codegen-2.0 is deprecated, use pygobject-codegen-2.0 instead
note: I will now try to invoke pygobject-codegen-2.0 in the same directory
Could not write function factory_main: No ArgType for
PanelAppletFactoryCallback
Could not write function panel_applet_shlib_factory: No ArgType for gpointer
Could not write function panel_applet_shlib_factory_closure: No ArgType for
gpointer
Could not write function main: No ArgType for char*-argv
Warning: Constructor for PanelApplet needs to be updated to new API
See http://live.gnome.org/PyGTK_2fWhatsNew28#update-constructors
***INFO*** The coverage of global functions is 33.33% (2/6)
***INFO*** The coverage of methods is 100.00% (13/13)
***INFO*** There are no declared virtual proxies.
***INFO*** There are no declared virtual accessors.
***INFO*** There are no declared interface proxies.
2011/10/21 Dale rdalek1...@gmail.com
co wrote:
can't emerge gnome-applets-python
what's the problem?
* ERROR: dev-python/gnome-applets-**python-2.32.0 failed (compile
phase):
* Building failed with CPython 2.7 in python_default_function()
function
*
* Call stack:
* ebuild.sh, line 56: Called src_compile
* environment, line 6045: Called gnome-python-common_src_**compile
* environment, line 3099: Called python_src_compile
* environment, line 5899: Called python_execute_function '-d' '-s'
'--'
* environment, line 4352: Called die
* The specific snippet of code:
* die ${failure_message};
*
* If you need support, post the output of 'emerge --info
=dev-python/gnome-applets-**python-2.32.0',
* the complete build log and the output of 'emerge -pqv
=dev-python/gnome-applets-**python-2.32.0'.
* The complete build log is located at '/var/tmp/portage/dev-python/**
gnome-applets-python-2.32.0/**temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/dev-python/
**gnome-applets-python-2.32.0/**temp/environment'.
* S: '/var/tmp/portage/dev-python/**gnome-applets-python-2.32.0/**
work/gnome-python-desktop-2.**32.0'
Failed to emerge dev-python/gnome-applets-**python-2.32.0, Log file:
'/var/tmp/portage/dev-python/**gnome-applets-python-2.32.0/**
temp/build.log'
* Messages for package dev-python/gnome-applets-**python-2.32.0:
* ERROR: dev-python/gnome-applets-**python-2.32.0 failed (compile
phase):
* Building failed with CPython 2.7 in python_default_function()
function
*
* Call stack:
* ebuild.sh, line 56: Called src_compile
* environment, line 6045: Called gnome-python-common_src_**compile
* environment, line 3099: Called python_src_compile
* environment, line 5899: Called python_execute_function '-d' '-s'
'--'
* environment, line 4352: Called die
* The specific snippet of code:
* die ${failure_message};
*
* If you need support, post the output of 'emerge --info
=dev-python/gnome-applets-**python-2.32.0',
* the complete build log and the output of 'emerge -pqv
=dev-python/gnome-applets-**python-2.32.0'.
* The complete build log is located at '/var/tmp/portage/dev-python/**
gnome-applets-python-2.32.0/**temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/dev-python/
**gnome-applets-python-2.32.0/**temp/environment'.
* S: '/var/tmp/portage/dev-python/**gnome-applets-python-2.32.0/**
work/gnome-python-desktop-2.**32.0'
You need to post farther back than this. Sometimes it fails farther back
than expected. See if you can find Error 1 and then go back at least a
couple dozen lines. That *usually* is far enough.
Dale
:-) :-)
[gentoo-user] Re: [gentoo-user] Re: [gentoo-user] Re: [gentoo-user] Fwd: gnome-applets-python 装不上
-lgobject-2.0 -lgthread-2.0 -lrt -lglib-2.0 -pthread
-march=core2 -Wl,-O1 -pthread -pthread -Wl,-soname -Wl,gnomeapplet.so
-Wl,-version-script -Wl,.libs/gnomeapplet.ver -o .libs/gnomeapplet.so
/usr/lib/gcc/x86_64-pc-linux-gnu/4.4.5/../../../../x86_64-pc-linux-gnu/bin/ld:
cannot find -lpng14
collect2: ld returned 1 exit status
make[2]: *** [gnomeapplet.la] Error 1
make[2]: Leaving directory
`/var/tmp/portage/dev-python/gnome-applets-python-2.32.0/work/gnome-python-desktop-2.32.0-2.7/gnomeapplet'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory
`/var/tmp/portage/dev-python/gnome-applets-python-2.32.0/work/gnome-python-desktop-2.32.0-2.7'
make: *** [all] Error 2
emake failed
[31;01m* [0m ERROR: dev-python/gnome-applets-python-2.32.0 failed (compile
phase):
[31;01m* [0m Building failed with CPython 2.7 in
python_default_function() function
[31;01m* [0m
[31;01m* [0m Call stack:
[31;01m* [0m ebuild.sh, line 56: Called src_compile
[31;01m* [0m environment, line 6045: Called
gnome-python-common_src_compile
[31;01m* [0m environment, line 3099: Called python_src_compile
[31;01m* [0m environment, line 5899: Called python_execute_function
'-d' '-s' '--'
[31;01m* [0m environment, line 4352: Called die
[31;01m* [0m The specific snippet of code:
[31;01m* [0m die ${failure_message};
[31;01m* [0m
[31;01m* [0m If you need support, post the output of 'emerge --info
=dev-python/gnome-applets-python-2.32.0',
[31;01m* [0m the complete build log and the output of 'emerge -pqv
=dev-python/gnome-applets-python-2.32.0'.
[31;01m* [0m The complete build log is located at
'/var/tmp/portage/dev-python/gnome-applets-python-2.32.0/temp/build.log'.
[31;01m* [0m The ebuild environment file is located at
'/var/tmp/portage/dev-python/gnome-applets-python-2.32.0/temp/environment'.
[31;01m* [0m S:
'/var/tmp/portage/dev-python/gnome-applets-python-2.32.0/work/gnome-python-desktop-2.32.0'
2011/10/21 Jonas de Buhr jonas.de.b...@gmx.net
just give the *full* output of the emerge command you ran.
Am 21.10.2011 10:03, schrieb co:
Thankyou, I found this
[SNIP]
[gentoo-user] Re: [gentoo-user] Re: [gentoo-user] Re: [gentoo-user] Re: [gentoo-user] Re: [gentoo-user] Fwd: gnome-applets-python 装不上
Thank you so muck!
2011/10/21 Jonas de Buhr jonas.de.b...@gmx.net
Am 21.10.2011 11:15, schrieb co:
[SNIP]
libtool: link: mv -f .libs/gnomeapplet.expT .libs/gnomeapplet.exp
libtool: link: echo { global: .libs/gnomeapplet.ver
libtool: link: cat .libs/gnomeapplet.exp | sed -e s/\(.*\)/\1;/
.libs/gnomeapplet.ver
libtool: link: echo local: *; }; .libs/gnomeapplet.ver
libtool: link: x86_64-pc-linux-gnu-gcc -shared
.libs/gnomeapplet_la-**appletmodule.o .libs/gnomeapplet_la-applet.o
-Wl,--as-needed -lpanel-applet-2 /usr/lib64/libgnomeui-2.so -L/usr/lib64
-lpng14 /usr/lib64/libgnome-keyring.so /usr/lib64/libgcrypt.so
/usr/lib64/libgpg-error.so -lX11 -lSM -lICE -lbonoboui-2
/usr/lib64/libgnomevfs-2.so -lxml2 -ldbus-glib-1 -ldbus-1 -lpthread -lssl
-lcrypto -ldl -lresolv -lutil -lgnomecanvas-2 -lgnome-2 -lpopt
/usr/lib64/libbonobo-2.so /usr/lib64/libbonobo-**activation.so
/usr/lib64/libORBitCosNaming-**2.so /usr/lib64/libORBit-2.so
/usr/lib64/libart_lgpl_2.so -lm /usr/lib64/libgtk-x11-2.0.so /usr/lib64/
libgdk-x11-2.0.so /usr/lib64/libatk-1.0.so -lgio-2.0 -lpangoft2-1.0
-lpangocairo-1.0 -lgdk_pixbuf-2.0 -lcairo -lpango-1.0
/usr/lib64/libfontconfig.so -lfreetype -lz -lbz2 -lexpat -lgconf-2
-lgmodule-2.0 -lgobject-2.0 -lgthread-2.0 -lrt -lglib-2.0 -pthread
-march=core2 -Wl,-O1 -pthread -pthread -Wl,-soname -Wl,gnomeapplet.so
-Wl,-version-script -Wl,.libs/gnomeapplet.ver -o .libs/gnomeapplet.so
/usr/lib/gcc/x86_64-pc-linux-**gnu/4.4.5/../../../../x86_64-**
pc-linux-gnu/bin/ld:
cannot find -lpng14
libpng14 doesn't exist. probably because it was updated and broken .la
files are still present.
eselect news list
and read the item about libpng15.
everything you neeed to do is described there. short version: delete all
.la files under /usr/ which contain png14 then do revdep-rebuild.
collect2: ld returned 1 exit status
[SNIP]
2011/10/21 Jonas de Buhrjonas.de.b...@gmx.net
just give the *full* output of the emerge command you ran.
Am 21.10.2011 10:03, schrieb co:
Thankyou, I found this
[SNIP]
[gentoo-user] Re: [gentoo-user] Re: [gentoo-user] Re: [gentoo-user] Re: [gentoo-user] Re: [gentoo-user] Fwd: gnome-applets-python 装不上
Thanks for you too
2011/10/21 Dale rdalek1...@gmail.com
co wrote:
build.log
[32;01m * [39;49;00mPackage:dev-python/gnome-applets-python-2.32.0
SNIP
libtool: link: x86_64-pc-linux-gnu-gcc -shared
.libs/gnomeapplet_la-appletmodule.o .libs/gnomeapplet_la-applet.o
-Wl,--as-needed -lpanel-applet-2 /usr/lib64/libgnomeui-2.so -L/usr/lib64
-lpng14 /usr/lib64/libgnome-keyring.so /usr/lib64/libgcrypt.so
/usr/lib64/libgpg-error.so -lX11 -lSM -lICE -lbonoboui-2
/usr/lib64/libgnomevfs-2.so -lxml2 -ldbus-glib-1 -ldbus-1 -lpthread -lssl
-lcrypto -ldl -lresolv -lutil -lgnomecanvas-2 -lgnome-2 -lpopt
/usr/lib64/libbonobo-2.so /usr/lib64/libbonobo-activation.so
/usr/lib64/libORBitCosNaming-2.so /usr/lib64/libORBit-2.so
/usr/lib64/libart_lgpl_2.so -lm /usr/lib64/libgtk-x11-2.0.so /usr/lib64/
libgdk-x11-2.0.so /usr/lib64/libatk-1.0.so -lgio-2.0 -lpangoft2-1.0
-lpangocairo-1.0 -lgdk_pixbuf-2.0 -lcairo -lpango-1.0
/usr/lib64/libfontconfig.so -lfreetype -lz -lbz2 -lexpat -lgconf-2
-lgmodule-2.0 -lgobject-2.0 -lgthread-2.0 -lrt -lglib-2.0 -pthread
-march=core2 -Wl,-O1 -pthread -pthread -Wl,-soname -Wl,gnomeapplet.so
-Wl,-version-script -Wl,.libs/gnomeapplet.ver -o .libs/gnomeapplet.so
/usr/lib/gcc/x86_64-pc-linux-gnu/4.4.5/../../../../x86_64-pc-linux-gnu/bin/ld:
cannot find -lpng14
collect2: ld returned 1 exit status
make[2]: *** [gnomeapplet.la] Error 1
make[2]: Leaving directory
`/var/tmp/portage/dev-python/gnome-applets-python-2.32.0/work/gnome-python-desktop-2.32.0-2.7/gnomeapplet'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory
`/var/tmp/portage/dev-python/gnome-applets-python-2.32.0/work/gnome-python-desktop-2.32.0-2.7'
make: *** [all] Error 2
emake failed
[31;01m* [0m ERROR: dev-python/gnome-applets-python-2.32.0 failed
(compile phase):
[31;01m* [0m Building failed with CPython 2.7 in
python_default_function() function
[31;01m* [0m
[31;01m* [0m Call stack:
[31;01m* [0m ebuild.sh, line 56: Called src_compile
[31;01m* [0m environment, line 6045: Called
gnome-python-common_src_compile
[31;01m* [0m environment, line 3099: Called python_src_compile
[31;01m* [0m environment, line 5899: Called python_execute_function
'-d' '-s' '--'
[31;01m* [0m environment, line 4352: Called die
[31;01m* [0m The specific snippet of code:
[31;01m* [0m die ${failure_message};
[31;01m* [0m
[31;01m* [0m If you need support, post the output of 'emerge --info
=dev-python/gnome-applets-python-2.32.0',
[31;01m* [0m the complete build log and the output of 'emerge -pqv
=dev-python/gnome-applets-python-2.32.0'.
[31;01m* [0m The complete build log is located at
'/var/tmp/portage/dev-python/gnome-applets-python-2.32.0/temp/build.log'.
[31;01m* [0m The ebuild environment file is located at
'/var/tmp/portage/dev-python/gnome-applets-python-2.32.0/temp/environment'.
[31;01m* [0m S:
'/var/tmp/portage/dev-python/gnome-applets-python-2.32.0/work/gnome-python-desktop-2.32.0'
Try this command:
revdep-rebuild --library libpng14.so.14 -- --keep-going
There is a news item about this error. This should help:
eselect news list
then
eselect news read number here
The news item is Upgrade to libpng15.
Hope that helps.
Dale
:-) :-)
