| View previous topic :: View next topic |
| Author |
Message |
sancho
n00b
Joined: 14 Apr 2003
Posts: 19
|
 Posted: Thu Aug 26, 2004 5:02 pm Post subject: emul-linux-x86 libs on amd64 |
 |
|
When I installed my amd64 system back in January, there were only 3 libraries for x86 compatability in portage tree:
emul-linux-x86-xlibs
emul-linux-x86-gtk-libs
emul-linux-x86-baselibs
I noticed that there is a new nvidia driver. After seeing that I noticed some new script or app called nvidia-settings. When I attempted to install that, I noticed a list of x86 libs. Can someone explain to me if it is safe to uninstall baselibs and then install all of these dependencies for nvidia-settings?
Thanks,
sancho
----------------
myprompt # ACCEPT_KEYWORDS="~amd64" emerge -av nvidia-settings
These are the packages that I would merge, in order:
Calculating dependencies ...done!
[blocks B ] <app-emulation/emul-linux-x86-baselibs-1.2 (from pkg app-emulation/emul-linux-x86-glibc-1.1)
[ebuild N ] media-video/nvidia-kernel-1.0.6111 15,138 kB
[ebuild U ] x11-base/opengl-update-1.8.1 [1.5] [empty/missing/bad digest]
[ebuild U ] media-video/nvidia-glx-1.0.6111 [1.0.5332-r1] +multilib 15,138 kB
[ebuild N ] media-video/nvidia-settings-1.0.6111 720 kB
[ebuild N ] app-emulation/emul-linux-x86-glibc-1.1 3,238 kB
[ebuild N ] app-emulation/emul-linux-x86-compat-1.0 1,200 kB
[ebuild U ] app-emulation/emul-linux-x86-baselibs-1.2.2 [1.0] 3,640 kB
[ebuild U ] app-emulation/emul-linux-x86-xlibs-1.2 [1.0] 4,645 kB
[ebuild N ] app-emulation/emul-linux-x86-nvidia-1.0.6111-r1 7,161 kB |
|
| Back to top |
|
 |
ballyn
n00b
Joined: 14 Aug 2003
Posts: 73
|
| Posted: Thu Aug 26, 2004 6:00 pm Post subject: |
|
|
Yeah, this should be safe... This is telling you that emul-linux-x86-glibc is blocked by baselibs-1.2, but in your list it shows it wants to update baselibs to 1.2.2. You could probably also just upgrade baselibs (using ~amd64) and then emerge nvidia-settings.
If you look at the changelog for baselibs (/usr/portage/app-emulation/emul-linux-x86-baselibs/ChangeLog), on 16 Aug. the glibc stuff was split off into its own ebuild. So, you can't have glibc 1.1 and baselibs 1.2 since they both contain the glibc emulation libraries. |
|
| Back to top |
|
|
ikshaar
Veteran
Joined: 23 Jul 2002
Posts: 1339
Location: Baltimore, MD
|
| Posted: Thu Aug 26, 2004 6:43 pm Post subject: |
|
|
It's still an unstable package ~amd64, so you can try it but you have to understand the risk of using ~amd64 keywords... this is not the recommended usage.
I did it myself so you can unemerge baselibs and reemerge what you need, but it's NOT SAFE per se. Per definition using unstable package is not safe 
_________________
"May God stands between you and harm in all the empty places where you must walk" - Babylon 5 |
|
| Back to top |
|
|
Lv
Retired Dev
Joined: 22 Jun 2003
Posts: 352
|
| Posted: Fri Aug 27, 2004 4:26 am Post subject: |
|
|
| i broke some of what used to be in baselibs out into glibc to decrease the size of future multilib stages. since glibc would overwrite files in the older baselibs, they conflict. you can solve the conflict by uninstalling baselibs before installing emul-linux-x86-glibc and the new baselibs that uses it. |
|
| Back to top |
|
|
radagast
Apprentice
Joined: 20 Mar 2004
Posts: 217
Location: sydney, .au
|
| Posted: Sun Sep 26, 2004 5:47 am Post subject: |
|
|
| ikshaar wrote: | It's still an unstable package ~amd64, so you can try it but you have to understand the risk of using ~amd64 keywords... this is not the recommended usage.
|
it doesn't look ~
i've been wondering about that blocking thing myself. and afraid of uninstalling the baselibs in case they never worked again. which is how i found this thread... but i've double checked, and all the emul-linux-x86 stuff is marked stable. the ebuild says
KEYWORDS="-* amd64"
i think i'm going to do it..... |
|
| Back to top |
|
|
|
Gentoo on AMD64
