| 1 |
On 03/13/2010 11:04 PM, Chris wrote: |
| 2 |
> World updates are rare for me (once every 6 months if that). I come |
| 3 |
> from a slack distro and I'm accustomed to handling everything |
| 4 |
> directly. So I haven't automated system updates in any sort of fashion |
| 5 |
> either. As for this package I am currently in the beta stage you |
| 6 |
> could say, I just want to see it run, then I'll worry about getting |
| 7 |
> runtime configuration that will survive updates. |
| 8 |
> |
| 9 |
|
| 10 |
You might want to do an emerge -u world before trying to install your |
| 11 |
package. |
| 12 |
|
| 13 |
Generally gentoo QA ensures that ~amd64 packages work on a system that |
| 14 |
generally has current ~amd64 packages installed on it, and amd64 |
| 15 |
packages work on a system that has current amd64 packages installed on it. |
| 16 |
|
| 17 |
Usually you can mix and match, but on rare occasion you can run into |
| 18 |
issues with that. |
| 19 |
|
| 20 |
However, if you're running a system that is six months out of date from |
| 21 |
stable, and you're trying to install a package marked for testing, you |
| 22 |
definitely have the potential to run into issues. |
| 23 |
|
| 24 |
Also - are you sure you've even synced your portage tree recently? It |
| 25 |
looks like the package you're trying to install is marked stable. |
| 26 |
|
| 27 |
One thing that you'll find with Gentoo is that you do need to update |
| 28 |
fairly often. Not necessarily daily, or even weekly. However, if you |
| 29 |
install gentoo today, and then do an emerge --sync and an emerge -u |
| 30 |
world two years from now, I'd be surprised if you don't run into a bunch |
| 31 |
of errors, and you might even have to dig up packages from cvs to even |
| 32 |
have an upgrade path (for example, very old versions of portage can't |
| 33 |
even upgrade itself to anything other than the oldest version of portage |
| 34 |
in the tree - which might not be around in a year). |
| 35 |
|
| 36 |
Try generally catching your system up, and see if the problem persists. |
| 37 |
It could be that the package is having compatibility issues with some |
| 38 |
library that was retired in the past, and generally we don't do QA |
| 39 |
checks against old packages that aren't in the tree any longer. |
| 40 |
|
| 41 |
Regarding multilib - the other posts explained the problems - in general |
| 42 |
you as a user can't install apps 32-bit unless they're designed to be |
| 43 |
run that way, unless you just create a chroot with an x86 install of |
| 44 |
gentoo. Sure, it can probably be done for simpler packages if you |
| 45 |
REALLY know what you're doing, but this isn't my recommendation. Also, |
| 46 |
I think you may have gotten a little confused about what multilib |
| 47 |
actually means. In a nutshell it means having support for libraries |
| 48 |
built for more than one architecture in a single install. Gentoo amd64 |
| 49 |
has very limited support for this, but it isn't what most would consider |
| 50 |
"full" support so you can only use it for packages that are designed to |
| 51 |
use it by the maintainer, or for fairly simple stuff you build/install |
| 52 |
yourself (put it in /usr/local or somewhere not maintained by Gentoo). |
| 53 |
There is some desire for true multilib support, but I think the impetus |
| 54 |
has gotten weaker since 64-bit has become fairly mainstream. |
| 55 |
|
| 56 |
Good luck! |
| 57 |
|
| 58 |
Rich |
Archives