GentooThis forum is for the discussion of Gentoo Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Can you please post here yours USE flag because every time i merged something i used to delete the old USE flag and write a new one with the USE flags that the new package needed.
My USE flags will be irrelevant for you, I have many huge files in /etc/portage/package.use/ to define them per-package, and they have been very finely grained during almost a decade and are suited to my tastes.
All you need to do is to edit your /make.conf, look for a line starting with USE="....." and add "consolekit to the list of USE flags. If USE is not there then add it.
Also, please, read the handbook and use Gentoo in a smart way. You are doing something very wrong if you set and unset USE flags that way. That way, the USE settings are not stored, and the next time you do "emerge -auDvN world" everything related to USE flags will be lost. To live statically USE flags need to be stored either in your profile, or in your /etc/make.conf or /etc/portage/package.use/* files. Otherwise, functionalities will come and go and you will be wondering why feature X is working today, not tomorrow, and maybe the next years. Randomness like that is not funny.
(dev-python/sphinx-1.0.5, ebuild scheduled for merge) depends on
(dev-python/jinja-2.5.5, ebuild scheduled for merge) (buildtime)
(dev-python/sphinx-1.0.5, ebuild scheduled for merge) (buildtime)
It might be possible to break this cycle
by applying the following change:
- dev-python/jinja-2.5.5 (Change USE: -doc)
Note that this change can be reverted, once the package has been installed.
Note that the dependency graph contains a lot of cycles.
Several changes might be required to resolve all cycles.
Temporarily changing some use flag for all packages might be the better option.
I just add a "-" infront of doc and test. Run again the emerge -auDvN world and now it tells me
this "Total: 235 packages (57 new, 1 in new slot, 177 reinstalls), Size of downloads: 220,225 kB"
# switch between notail / tail freely.
#
# The root filesystem should have a pass number of either 0 or 1.
# All other filesystems should have a pass number of 0 or greater than 1.
#
# See the manpage fstab(5) for more information.
#
# <fs> <mountpoint> <type> <opts> <dump/pass>
# NOTE: If your BOOT partition is ReiserFS, add the notail option to opts.
/dev/sda1 /boot ext2 noauto 1 2
/dev/sda2 none swap sw 0 0
/dev/sda3 / ext4 noatime 0 1
/dev/sdb1 /mnt/disk ext3 auto,user 0 0
/dev/cdrom /mnt/cdrom auto noauto,user 0 0
proc /proc proc defaults 0 0
# glibc 2.2 and above expects tmpfs to be mounted at /dev/shm for
# POSIX shared memory (shm_open, shm_unlink).
# (tmpfs is a dynamically expandable/shrinkable ramdisk, and will
# use almost no memory if not populated with files)
shm /dev/shm tmpfs nodev,nosuid,noexec 0 0
The result of ck-list-sessions i ll post it when update end..cause im not now in X enviroment
Is /dev/sdb1 a real disk? Maybe that line is interfering somehow. You can try one thing: run "dmesg", look at the last few lines, then plug your pen drive into the usb bay and run "dmesg" again. There should be some more output, look at it and see which device node is the usb stick attached to. Then try to mount it manually as a regular user.
If in doubt, paste that new output from "dmesg" here as well.
!!! Please attach the following file when seeking support:
!!! /var/tmp/portage/gnome-base/libgtop-2.28.2/work/libgtop-2.28.2/config.log
* ERROR: gnome-base/libgtop-2.28.2 failed:
* econf failed
*
* Call stack:
* ebuild.sh, line 56: Called src_configure
* environment, line 1505: Called gnome2_src_configure
* environment, line 1248: Called econf '--disable-static' '--enable-debug=yes' '--disable-gtk-doc'
* ebuild.sh, line 552: Called die
* The specific snippet of code:
* die "econf failed"
*
* If you need support, post the output of 'emerge --info =gnome-base/libgtop-2.28.2',
* the complete build log and the output of 'emerge -pqv =gnome-base/libgtop-2.28.2'.
* The complete build log is located at '/var/tmp/portage/gnome-base/libgtop-2.28.2/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/gnome-base/libgtop-2.28.2/temp/environment'.
* S: '/var/tmp/portage/gnome-base/libgtop-2.28.2/work/libgtop-2.28.2'
>>> Failed to emerge gnome-base/libgtop-2.28.2, Log file:
* Please remember to run revdep-rebuild when upgrading
* from libupnp 1.4.x to libupnp 1.6.x , so packages
* gets linked with the new library.
*
* The revdep-rebuild script is part of the
* app-portage/gentoolkit package.
* Messages for package gnome-base/libgtop-2.28.2:
* ERROR: gnome-base/libgtop-2.28.2 failed:
* econf failed
*
* Call stack:
* ebuild.sh, line 56: Called src_configure
* environment, line 1505: Called gnome2_src_configure
* environment, line 1248: Called econf '--disable-static' '--enable-debug=yes' '--disable-gtk-doc'
* ebuild.sh, line 552: Called die
* The specific snippet of code:
* die "econf failed"
*
* If you need support, post the output of 'emerge --info =gnome-base/libgtop-2.28.2',
* the complete build log and the output of 'emerge -pqv =gnome-base/libgtop-2.28.2'.
* The complete build log is located at '/var/tmp/portage/gnome-base/libgtop-2.28.2/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/gnome-base/libgtop-2.28.2/temp/environment'.
* S: '/var/tmp/portage/gnome-base/libgtop-2.28.2/work/libgtop-2.28.2'
* GNU info directory index is up-to-date.
* IMPORTANT: 1 config files in '/etc' need updating.
* See the CONFIGURATION FILES section of the emerge
* man page to learn how to update config files.
Sh***t now nothing works... i try to start the x and doesn't work.
Quote:
Current version of pixman: 0.20.0
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Fri Feb 18 15:42:59 2011
(==) Using config file: "/etc/X11/xorg.conf"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
dlopen: libdrm_nouveau.so.1: cannot open shared object file: No such file or directory
(EE) Failed to load /usr/lib/xorg/modules/drivers/nouveau_drv.so
(EE) Failed to load module "nouveau" (loader failed, 7)
(EE) No drivers available.
Fatal server error:
no screens found
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
Please also check the log file at "/var/log/Xorg.0.log" for additional information.
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error
Sh***t now nothing works... i try to start the x and doesn't work.
Probably more of the same. When you recompile some critical X package, often, you also need to recompile all the X drivers so the ABIs match. Try recompiling x11-drivers/xf86-video-nouveau,
I never saw anything similar, but I noticed you didn't update your config files properly in your other post above. That's also a dangerous thing to ignore:
Code:
* IMPORTANT: 1 config files in '/etc' need updating.
* See the CONFIGURATION FILES section of the emerge
* man page to learn how to update config files.
Try running etc-update and fixing your config files. Maybe that's the source of the problem. Otherwise, I can't be of much help on diagnosing nano problems.
Then i run USE="video_cards_nouveau" revdep-rebuild (i can't edit my /etc/make.conf so i wrote it like this)
All went OK with x11-drivers/xf86-video-nouveau and now the revdep-rebuild returns this :
Quote:
* Configuring search environment for revdep-rebuild
* Checking reverse dependencies
* Packages containing binaries and libraries broken by a package update
* will be emerged.
* Collecting system binaries and libraries
* Generated new 1_files.rr
* Collecting complete LD_LIBRARY_PATH
* Generated new 2_ldpath.rr
* Checking dynamic linking consistency
[ 100% ]
* Dynamic linking on your system is consistent... All done.
After this i type etc-update but don't know what to choose
Quote:
Scanning Configuration files...
The following is the list of files which need updating, each
configuration file is followed by a list of possible replacement files.
1) /etc/pm/config.d/gentoo (1)
Please select a file to edit by entering the corresponding number.
(don't use -3, -5, -7 or -9 if you're unsure what to do)
(-1 to exit) (-3 to auto merge all remaining files)
(-5 to auto-merge AND not use 'mv -i')
(-7 to discard all updates)
(-9 to discard all updates AND not use 'rm -i'):
I want to make this (with the conf file) and then run again emerge -auDvN world and see what will happen..
Then i run USE="video_cards_nouveau" revdep-rebuild (i can't edit my /etc/make.conf so i wrote it like this)
All went OK with x11-drivers/xf86-video-nouveau and now the revdep-rebuild returns this :
The var you are looking for is VIDEO_CARDS, not USE. They are -internally- USE flags, but they work this way:
Code:
VIDEO_CARDS="nouveau" emerge <foo>
Quote:
After this i type etc-update but don't know what to choose
If you didn't change the file it is referring to, then choose the option to replace the old file with the new one. I think it's "1", but just read yourself. I am not sure right now.
* ERROR: gnome-base/libgtop-2.28.2 failed:
* econf failed
*
* Call stack:
* ebuild.sh, line 56: Called src_configure
* environment, line 1508: Called gnome2_src_configure
* environment, line 1251: Called econf '--disable-static' '--enable-debug=yes' '--disable-gtk-doc'
* ebuild.sh, line 552: Called die
* The specific snippet of code:
* die "econf failed"
*
* If you need support, post the output of 'emerge --info =gnome-base/libgtop-2.28.2',
* the complete build log and the output of 'emerge -pqv =gnome-base/libgtop-2.28.2'.
* The complete build log is located at '/var/tmp/portage/gnome-base/libgtop-2.28.2/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/gnome-base/libgtop-2.28.2/temp/environment'.
* S: '/var/tmp/portage/gnome-base/libgtop-2.28.2/work/libgtop-2.28.2'
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
i try to start the x and doesn't work.
