LinuxSir.cn,穿越时空的Linuxsir!

 找回密码
 注册
搜索
热搜: shell linux mysql
查看: 1261|回复: 6

无法安装gnome-light

[复制链接]
发表于 2008-5-8 16:49:02 | 显示全部楼层 |阅读模式
全新安装gentoo,先安装了gcc-4.3.0,然后emerge -upDN world,然后emerge xorg-x11,然后emerge gnome-light的过程中,安装到pygobject的时候出现错误,无法继续。
信息如下:

Calculating dependencies   ... done!
>>> Verifying ebuild Manifests...
>>> starting parallel fetching pid 25880

>>> Emerging (1 of 62) dev-python/pygobject-2.14.1 to /
* pygobject-2.14.1.tar.bz2 RMD160 SHA1 SHA256 size ;-) ...               [ ok ]
* checking ebuild checksums ;-) ...                                      [ ok ]
* checking auxfile checksums ;-) ...                                     [ ok ]
* checking miscfile checksums ;-) ...                                    [ ok ]
* checking pygobject-2.14.1.tar.bz2 ;-) ...                              [ ok ]
>>> Unpacking source...
>>> Unpacking pygobject-2.14.1.tar.bz2 to /var/tmp/portage/dev-python/pygobject-2.14.1/work
* Fixing OMF Makefiles ...
  [ ok ]
* Running elibtoolize in: pygobject-2.14.1
*   Applying install-sh-1.5.4.patch ...
*   Applying portage-1.5.10.patch ...
*   Applying sed-1.5.6.patch ...
* Applying pygobject-2.14.0-libffi-magic.patch ...
  [ ok ]
* Running eautoreconf in '/var/tmp/portage/dev-python/pygobject-2.14.1/work/pygobject-2.14.1' ...
* Running aclocal -I . ...
  [ ok ]
* Running libtoolize --copy --force --install --automake ...
  [ ok ]
* Running aclocal -I . ...
  [ ok ]
* Running autoconf ...
  [ ok ]
* Running autoheader ...
  [ ok ]
* Running automake --add-missing --copy ...
  [ ok ]
>>> Source unpacked.
>>> Compiling source in /var/tmp/portage/dev-python/pygobject-2.14.1/work/pygobject-2.14.1 ...
* econf: updating pygobject-2.14.1/config.guess with /usr/share/gnuconfig/config.guess
* econf: updating pygobject-2.14.1/config.sub with /usr/share/gnuconfig/config.sub
./configure --prefix=/usr --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --disable-docs --without-libffi --disable-gtk-doc --build=i686-pc-linux-gnu
configure: WARNING: Unrecognized options: --disable-gtk-doc
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for some Win32 platform... no
checking for native Win32... no
checking for style of include used by make... GNU
checking for i686-pc-linux-gnu-gcc... i686-pc-linux-gnu-gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether i686-pc-linux-gnu-gcc accepts -g... yes
checking for i686-pc-linux-gnu-gcc option to accept ISO C89... none needed
checking dependency style of i686-pc-linux-gnu-gcc... gcc3
checking for a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ld used by i686-pc-linux-gnu-gcc... /usr/i686-pc-linux-gnu/bin/ld
checking if the linker (/usr/i686-pc-linux-gnu/bin/ld) is GNU ld... yes
checking for /usr/i686-pc-linux-gnu/bin/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
checking how to recognize dependent libraries... pass_all
checking how to run the C preprocessor... i686-pc-linux-gnu-gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking the maximum length of command line arguments... 98304
checking command to parse /usr/bin/nm -B output from i686-pc-linux-gnu-gcc object... ok
checking for objdir... .libs
checking for i686-pc-linux-gnu-ar... i686-pc-linux-gnu-ar
checking for i686-pc-linux-gnu-ranlib... i686-pc-linux-gnu-ranlib
checking for i686-pc-linux-gnu-strip... i686-pc-linux-gnu-strip
checking if i686-pc-linux-gnu-gcc supports -fno-rtti -fno-exceptions... no
checking for i686-pc-linux-gnu-gcc option to produce PIC... -fPIC
checking if i686-pc-linux-gnu-gcc PIC flag -fPIC works... yes
checking if i686-pc-linux-gnu-gcc static flag -static works... yes
checking if i686-pc-linux-gnu-gcc supports -c -o file.o... yes
checking whether the i686-pc-linux-gnu-gcc linker (/usr/i686-pc-linux-gnu/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
configure: creating libtool
checking for a Python interpreter with version >= 2.3.5... python
checking for python... /usr/bin/python
checking for python version... 2.5
checking for python platform... linux2
checking for python script directory... ${prefix}/lib/python2.5/site-packages
checking for python extension module directory... ${exec_prefix}/lib/python2.5/site-packages
checking for headers required to compile python extensions... found
checking for PySignal_SetWakeupFd in Python.h... yes
checking for python module thread... yes
checking whether to enable threading in pygobject... yes
./libtool: line 463: CDPATH: command not found
checking for i686-pc-linux-gnu-pkg-config... no
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.16... yes
checking for GLIB - version >= 2.8.0... yes (version 2.16.3)
checking for ffi.h... disabled
checking whether i686-pc-linux-gnu-gcc understands -Wall... yes
checking whether i686-pc-linux-gnu-gcc understands -fno-strict-aliasing... yes
checking whether i686-pc-linux-gnu-gcc understands -std=c9x... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating pygobject-2.0.pc
config.status: creating pygobject-2.0-uninstalled.pc
config.status: creating docs/Makefile
config.status: creating docs/reference/entities.docbook
config.status: creating docs/xsl/fixxref.py
config.status: creating gobject/Makefile
config.status: creating examples/Makefile
config.status: creating tests/Makefile
config.status: creating PKG-INFO
config.status: creating config.h
config.status: executing depfiles commands
configure: WARNING: Unrecognized options: --disable-gtk-doc

libffi support: disabled

cd . && /bin/sh /var/tmp/portage/dev-python/pygobject-2.14.1/work/pygobject-2.14.1/missing --run autoheader
autoheader-2.62: cannot create `pwd`/pygobject-2.14.1/ah9333.28979: No such file or directory
at /usr/bin/autoheader-2.62 line 129
WARNING: `autoheader' is missing on your system.  You should only need it if
         you modified `acconfig.h' or `configure.ac'.  You might want
         to install the `Autoconf' and `GNU m4' packages.  Grab them
         from any GNU archive site.
rm -f stamp-h1
touch config.h.in
cd . && /bin/sh ./config.status config.h
config.status: creating config.h
config.status: config.h is unchanged
make  all-recursive
make[1]: Entering directory `/var/tmp/portage/dev-python/pygobject-2.14.1/work/pygobject-2.14.1'
Making all in docs
make[2]: Entering directory `/var/tmp/portage/dev-python/pygobject-2.14.1/work/pygobject-2.14.1/docs'
make  all-am
make[3]: Entering directory `/var/tmp/portage/dev-python/pygobject-2.14.1/work/pygobject-2.14.1/docs'
make[3]: Nothing to be done for `all-am'.
make[3]: Leaving directory `/var/tmp/portage/dev-python/pygobject-2.14.1/work/pygobject-2.14.1/docs'
make[2]: Leaving directory `/var/tmp/portage/dev-python/pygobject-2.14.1/work/pygobject-2.14.1/docs'
Making all in gobject
make[2]: Entering directory `/var/tmp/portage/dev-python/pygobject-2.14.1/work/pygobject-2.14.1/gobject'
if /bin/sh ../libtool --tag=CC --mode=compile i686-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/include/python2.5 -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include   -DPY_SSIZE_T_CLEAN   -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include    -march=i686 -O2 -pipe -fomit-frame-pointer -Wall -fno-strict-aliasing -std=c9x -MT _gobject_la-gobjectmodule.lo -MD -MP -MF ".deps/_gobject_la-gobjectmodule.Tpo" -c -o _gobject_la-gobjectmodule.lo `test -f 'gobjectmodule.c' || echo './'`gobjectmodule.c; \
        then mv -f ".deps/_gobject_la-gobjectmodule.Tpo" ".deps/_gobject_la-gobjectmodule.Plo"; else rm -f ".deps/_gobject_la-gobjectmodule.Tpo"; exit 1; fi
if /bin/sh ../libtool --tag=CC --mode=compile i686-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/include/python2.5 -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include   -DPY_SSIZE_T_CLEAN   -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include    -march=i686 -O2 -pipe -fomit-frame-pointer -Wall -fno-strict-aliasing -std=c9x -MT _gobject_la-pygboxed.lo -MD -MP -MF ".deps/_gobject_la-pygboxed.Tpo" -c -o _gobject_la-pygboxed.lo `test -f 'pygboxed.c' || echo './'`pygboxed.c; \
        then mv -f ".deps/_gobject_la-pygboxed.Tpo" ".deps/_gobject_la-pygboxed.Plo"; else rm -f ".deps/_gobject_la-pygboxed.Tpo"; exit 1; fi
../libtool: line 463: CDPATH: command not found
../libtool: line 463: CDPATH: command not found
../libtool: line 1148: func_opt_split: command not found
../libtool: line 1148: func_opt_split: command not found
libtool: Version mismatch error.  This is libtool 2.2.4, but the
libtool: definition of this LT_INIT comes from an older release.
libtool: You should recreate aclocal.m4 with macros from libtool 2.2.4
libtool: and run autoconf again.
libtool: Version mismatch error.  This is libtool 2.2.4, but the
libtool: definition of this LT_INIT comes from an older release.
libtool: You should recreate aclocal.m4 with macros from libtool 2.2.4
libtool: and run autoconf again.
make[2]: *** [_gobject_la-gobjectmodule.lo] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: *** [_gobject_la-pygboxed.lo] Error 1
make[2]: Leaving directory `/var/tmp/portage/dev-python/pygobject-2.14.1/work/pygobject-2.14.1/gobject'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/dev-python/pygobject-2.14.1/work/pygobject-2.14.1'
make: *** [all] Error 2
*
* ERROR: dev-python/pygobject-2.14.1 failed.
* Call stack:
*               ebuild.sh, line   49:  Called src_compile
*             environment, line 2922:  Called gnome2_src_compile
*             environment, line 2198:  Called die
* The specific snippet of code:
*       emake || die "compile failure"
*  The die message:
*   compile failure
*
* If you need support, post the topmost build error, and the call stack if relevant.
* A complete build log is located at '/var/tmp/portage/dev-python/pygobject-2.14.1/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/dev-python/pygobject-2.14.1/temp/environment'.




我用的profile是2008beta2默认的,我的make.conf如下:
# These settings were set by the catalyst build script that automatically
# built this stage.
# Please consult /etc/make.conf.example for a more detailed example.
# CFLAGS="-O2 -march=i686 -pipe"
# CXXFLAGS="${CFLAGS}"
# This should not be changed unless you know exactly what you are doing.  You
# should probably be using a different stage, instead.
# CHOST="i686-pc-linux-gnu"

  CFLAGS="-march=i686 -O2 -pipe -fomit-frame-pointer"
  CXXFLAGS="${CFLAGS}"
  CHOST="i686-pc-linux-gnu"
  MAKEOPTS="-j2"
  ACCEPT_KEYWORDS="~x86"
  FEATURES="ccache parallel-fetch"
  CCACHE_SIZE="2G"
  CCACHE_DIR="/var/tmp/ccache"
  ALSA_CARDS="intel8x0"
  VIDEO_CARDS="i810"
  LINGUAS="zh_CN"
  INPUT_DEVICES="keyboard mouse"
# CONFIG_PROTECT="-*"
  
  USE="X gtk gnome gif alsa midi -cups -evo -ldap -ipv6 -gstreamer -ieee1394 -xine -joystick -pcmcia -wifi -doc -bluetooth -apm -cdr -dvd -dvdr -dvdread -ppds -tiff -pam "
  
  GENTOO_MIRRORS="http://61.135.158.199"
  SYNC="rsync://61.135.158.199/gentoo-portage"
# GENTOO_MIRRORS="http://adelie.polymtl.ca"
# SYNC="rsync://rsync.gentoo.org/gentoo-portage"
# source /usr/portage/local/layman/make.conf


查了很久google也没找到原因,请大家帮忙看看
发表于 2008-5-8 19:45:36 | 显示全部楼层
应该是libtool的问题,你把libtool降至1.5*的看看,
参见:
http://bugs.gentoo.org/show_bug.cgi?id=212718
回复 支持 反对

使用道具 举报

发表于 2008-5-9 14:42:41 | 显示全部楼层
这里有与你相同的问题。
  我最近换 Gnome 也出了这个问题。我英文不太好。从上面这个 Bug 的讨论,我感觉可能是一系列用 Python 的 Gnome 软件包安装都受到了影响。6 楼指出下一版 Gnome 会修复这个问题。最后有一个 Patch,作者说可以用于 2.2 版 libtool。
  总之,我这两天先用 Windows 忍受一下,过两天再看看安装。

PS:这一段 Linux 操作系统处于变革期?大进步?
回复 支持 反对

使用道具 举报

 楼主| 发表于 2008-5-10 08:35:57 | 显示全部楼层
亚利艾尔,谢谢你,每次我遇到困难的时候你都挺身而出,呵呵,谢谢
看来这是现在的普遍情况了,也就是说现在所有人都没有emerge gnome-light吗?
为什么这么严重的情况开发者不快点解决呢?
回复 支持 反对

使用道具 举报

发表于 2008-5-10 10:21:36 | 显示全部楼层
你用的不是稳定版吧
这样不是什么大问题
建议没事的时候到http://planet.gentoo.org/或者z ... gentoo的情况。
应该是libtool 2.2 gcc 4.3 等工具要进portage导致的问题,耐心等吧。

A very good example of this is the current state of Gentoo’s ~arch tree. At the moment there are quite a few things that might lead to build-failure because different projects are interleaved:

GCC 4.3 changes will cause a lot of build failures in C++ software because the headers dependencies were cleaned up; similar changes happen every GCC minor release;
autoconf 2.62 started catching bad errors in configure scripts, especially related to variable names; similar changes happen every autoconf release;
libtool 2.2 stopped calling C++ and Fortran compilers check by default, so packages have to take care of what they do use;
curl 7.18 is now stricter in the way options are set in its easy interface, requiring boolean options to be explicitly provided;
Qt 4.4 is being split in multiple packages, and dependencies has thus to be fixed.
回复 支持 反对

使用道具 举报

发表于 2008-5-10 14:06:28 | 显示全部楼层
没事,我现在有时间就看看论坛。我也有这个问题而已。
  关于我的问题,好像楼上作了解答。果然是在“变革期”,所以我打算等到 6 月初才安装。我还是坚定不移的使用 ~x86 软件。
  楼主这两天没什么要紧的就用 x86 吧!然后在 6 月初之类的时候改为 ~x86。
回复 支持 反对

使用道具 举报

 楼主| 发表于 2008-5-10 16:04:34 | 显示全部楼层
呵呵,我也喜欢用~x86,本来用的是KDE,想全新安装一个gnome,既然安装不成,我就暂时先不装了,用着KDE吧,呵呵,我认为KDE下的软件功能强大,而gnome漂亮,呵呵
回复 支持 反对

使用道具 举报

您需要登录后才可以回帖 登录 | 注册

本版积分规则

快速回复 返回顶部 返回列表