1 |
I have to admit that I'm a recent convert to Gentoo and don't really |
2 |
understand (read: haven't the slightest clue about) the inner workings |
3 |
of portage, emerge, ebuild et al. |
4 |
|
5 |
My problem is that I've installed a multilib-enabled 64-bit system and |
6 |
realised that /usr/lib32 and /usr/lib64 are vastly of different. There |
7 |
are around 2200 dynamic and some 130 static libs in lib64 while there |
8 |
are around 300 dynamic and 15 static libs in lib32. That is, about 85% |
9 |
of libraries exist in 64-bit version only. |
10 |
|
11 |
Consequently, pretty much any 32-bit binary fails to launch due to |
12 |
missing libraries. Which is most unfortunate as I have quite a few |
13 |
of such binaries from EDA tools to productivity tools to games. |
14 |
|
15 |
I would much appreciate if someone would explain how to tell the system |
16 |
to build a 32-bit version of *every* library it installs (and have |
17 |
already installed) so that 32-bit binaries could run (and could also be |
18 |
built against those libs, actually). |
19 |
|
20 |
Due to my complete lack of understanding of the magic embedded in |
21 |
portage, my reading of the Gentoo Wiki did not help at all. Yes, I |
22 |
found the multilib pages, all sorts of references to ebuild categories |
23 |
but, unfortunately, I don't really understand what they talk about. |
24 |
|
25 |
So if a good soul came down to the level of the unfranked and told me |
26 |
what to do, I'd be most obliged. In addition, if there's some decent |
27 |
documentation on the package management system (apart from the Wiki), |
28 |
preferably in a format that can be printed for night-time reading, I'd |
29 |
be glad to receive some pointers. |
30 |
|
31 |
Thanks, |
32 |
|
33 |
Zoltan |