| 1 |
On Sun, 12 Dec 2021 10:05:58 +0000 |
| 2 |
Wols Lists <antlists@××××××××××××.uk> wrote: |
| 3 |
|
| 4 |
> On 12/12/2021 05:55, Bryan Gardiner wrote: |
| 5 |
> > I don't really look forward to uninstalling bzip2. Manually |
| 6 |
> > uninstalling and reinstalling freetype and harfbuzz doesn't fix the |
| 7 |
> > issue. I am thinking about deleting all of these libraries by hand |
| 8 |
> > and then rebuilding the packages, or perhaps unmerging freetype and |
| 9 |
> > harfbuzz with FEATURES="-preserved-libs". I'm not sure if this will |
| 10 |
> > clean up all of Portage's metadata about the libraries though. |
| 11 |
> > |
| 12 |
> > Any insight into a 'proper' way to fix this would be appreciated. |
| 13 |
> |
| 14 |
> If you read the messages, it should tell you which program is actually |
| 15 |
> pulling freetype and harfbuzz in with the flags you don't want. Are they |
| 16 |
> currently installed with the correct flags you want? |
| 17 |
> |
| 18 |
> If they don't have the flags you want, try to force-emerge them with the |
| 19 |
> flags you do want and portage will complain "can't do that because of |
| 20 |
> ..." That should tell you the problem program. Do an emerge -C on that |
| 21 |
> program, re-emerge harfbuzz and freetype with the correct flags, and you |
| 22 |
> SHOULD be home and dry ... |
| 23 |
|
| 24 |
Hi and thanks, |
| 25 |
|
| 26 |
I finally had time to look at this again, and setting USE=-harfbuzz |
| 27 |
and running |
| 28 |
|
| 29 |
ABI_X86_32='32 64' emerge -v1 freetype harfbuzz |
| 30 |
emerge -v1 freetype harfbuzz |
| 31 |
|
| 32 |
fixed it (by breaking the 32-bit freetype -> harfbuzz dep). I don't |
| 33 |
know where I went wrong before. I also broke Portage temporarily by |
| 34 |
force-emerging the older harfbuzz that the preserved lib was from, and |
| 35 |
hit bug #521968, but it's all good now. |
| 36 |
|
| 37 |
Cheers, |
| 38 |
Bryan |
Archives