| 1 |
On 02/11/2019 01:36, John Covici wrote: |
| 2 |
> Hi. Well, I was finally able to do the change of profile tothe 17.1 |
| 3 |
> profile. I have gotten all the way almost to the end of this process |
| 4 |
> to the final step where itwantsto emerge all the 32-bit packages. I |
| 5 |
> am about two from the end of that list and trying to emerge |
| 6 |
> x11-libs/gtk+-2.24.32-r1 andI have run into this problem: |
| 7 |
> |
| 8 |
> libtool: link: x86_64-pc-linux-gnu-gcc -O2 -mtune=core2 -pipe -ggdb |
| 9 |
> -Wall -Wl,-O1 -o decompose-bits decompose-bits.o -Wl,--as-needed |
| 10 |
> /usr/lib/libatk-1.0.so -lpango-1.0 -lcairo -lgdk_pixbuf-2.0 |
| 11 |
> -lgobject-2.0 -lglib-2.0 |
| 12 |
> /usr/lib/gcc/x86_64-pc-linux-gnu/8.3.0/../../../../x86_64-pc-linux-gnu/bin/ld: |
| 13 |
> /usr/lib/libatk-1.0.so: error adding symbols: file in wrong format |
| 14 |
> collect2: error: ld returned 1 exit status |
| 15 |
> |
| 16 |
> Now, I re-emerged dev-libs/atk which contains the offending |
| 17 |
> library, but no joy. the gtk package is pulled in by several other |
| 18 |
> packages, so I cannot remove it. |
| 19 |
|
| 20 |
If you re-emerged atk successfully, then the gtk linking stage should |
| 21 |
not fail with the same error as /usr/lib/libatk-1.0.so should now be in |
| 22 |
the correct format (32-bit instead of 64-bit). |
| 23 |
|
| 24 |
> |
| 25 |
> Thanks in advance for any suggestions asto howto proceed. |
| 26 |
> |
| 27 |
|
| 28 |
You have to pull in some packages in a very specific order. |
| 29 |
|
| 30 |
With KDE we have a sort of circular dependency on freetype[harfbuzz], |
| 31 |
because harfbuzz itself depends on freetype. For this reason I had to do |
| 32 |
the following: |
| 33 |
|
| 34 |
env USE=-harfbuzz emerge -1 freetype |
| 35 |
emerge -1 harfbuzz |
| 36 |
emerge -1 freetype |
| 37 |
|
| 38 |
There is currently no way for Portage to do this automatically. |
| 39 |
|
| 40 |
Your issue sounds similar and I would suggest emerging offending |
| 41 |
packages separately before continuing the rebuild process for /lib32, |
| 42 |
etc. The order is going to depend on other packages you have installed. |
| 43 |
|
| 44 |
As soon as one of these special packages errors, you need to check the |
| 45 |
build log. Most likely it was during the configure stage where a |
| 46 |
dependency is not being found in /lib because it has not been built yet. |
| 47 |
Build that dependency with --oneshot and try again with the failing |
| 48 |
package after. |
| 49 |
|
| 50 |
-- |
| 51 |
Andrew |
Archives