Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
[SOLVED] Pango fails to compile on RPi4
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Gentoo on ARM
View previous topic :: View next topic  
Author Message
Tortue
Tux's lil' helper
Tux's lil' helper


Joined: 27 May 2005
Posts: 75
Location: Gatineau (Québec), Canada

PostPosted: Sun Jul 11, 2021 1:32 am    Post subject: [SOLVED] Pango fails to compile on RPi4 Reply with quote

Not sure I should write this message, but I will do it anyway.

My setup is a Raspberry Pi 4 with 8 Gb of RAM and two external hard drives that I simply use as a headless file server for the family. I followed the "64-bit Install" for both RPi3 and RPi4 guides on the Gentoo wiki, and installation went pretty smoothly. That was three months ago. I also I use my main box (Ryzen 5 2600) as a compiler helper with distcc, which accelerates the tasks a lot (maybe too much??). The RPi4 kernel was also compiled on that same main box, as per instructions on the wiki.

Then, in the last few weeks, pango failed to compile and with it, app-accessibility/at-spi2-core and gnome-base/libsrvg, which depend on pango. (By the way, I don't know why they are needed on a headless server, but that is another question). After some unsuccesful retries, I decided to disable distcc and reduce MAKEOPTS in /etc/portage/make.conf, like so:

From:
Code:
MAKEOPTS="-j6"
FEATURES="distcc"


To:
Code:
MAKEOPTS="-j2"
#FEATURES="distcc"


Pango emerged without problems with just "emerge -v pango", as well as the two other packages individually. I did not try it, but, once the pango problem was fixed, I guess I could have reverted back to the previous config in make.conf before emerging the last two packages.

Voilà. Hope this will help someone with the same problem.
_________________
"La vie est un formidable scénariste"
- Le cinéaste Bertrand Tavernier, citant un ami
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 54809
Location: 56N 3W

PostPosted: Sun Jul 11, 2021 11:01 am    Post subject: Reply with quote

Tortue,

Portage has a way to disable distcc or a per package basis.
That link will set you off on the right track.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
Tortue
Tux's lil' helper
Tux's lil' helper


Joined: 27 May 2005
Posts: 75
Location: Gatineau (Québec), Canada

PostPosted: Mon Jul 12, 2021 12:49 am    Post subject: Reply with quote

NeddySeagoon,

Thanks for the tip, I did not know that one.

So, if my understanding is correct, the deal would be to have a file like /etc/portage/env/nodistcc.conf that would contain the following:
Code:
MAKEOPTS="-j2"
#FEATURES="distcc"

and an entry in /etc/portage/package.env that would contain:
Code:
x11-libs/pango nodistcc.conf

Is that right?

Since it was the first time I hit a problem with updating the RPi, I think the best was to use my method first, just to see if it works, and then use your tip in the future, to avoid playing with make.conf every time pango comes up for an update.

Thanks again!
_________________
"La vie est un formidable scénariste"
- Le cinéaste Bertrand Tavernier, citant un ami
Back to top
View user's profile Send private message
Hu
Administrator
Administrator


Joined: 06 Mar 2007
Posts: 23066

PostPosted: Mon Jul 12, 2021 3:30 am    Post subject: Reply with quote

Tortue wrote:
Code:
#FEATURES="distcc"
That would be seen as a comment, and do nothing. You probably want:
Code:
FEATURES="-distcc"
That is a directive that explicitly disables distcc. Note that I have not tested whether this particular feature can be reset this way, but this is the style that is used for other things that are incrementally updated/reduced.
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 54809
Location: 56N 3W

PostPosted: Mon Jul 12, 2021 7:52 am    Post subject: Reply with quote

Hu,

That's correct. FEATURES is a cumulative environmental variable, like USE and unlike CFLAGS

Tortue,

The file names in /etc/portage/env can be anything. They need not end in .conf.
I have a nodistcc and a makeoptsj2 separately, since on smaller Raspberry Pis, some thing ran out of RAM with bigger MAKEOPTS

Portage understands a string of changes in /etc/portage/package.env
So I would write
Code:
x11-libs/pango nodistcc makeoptsj2

_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
Tortue
Tux's lil' helper
Tux's lil' helper


Joined: 27 May 2005
Posts: 75
Location: Gatineau (Québec), Canada

PostPosted: Tue Jul 13, 2021 12:08 am    Post subject: Reply with quote

Hu, NeddySeagoon,

Thanks to both of you.

Yes, it is much more logical to use
Code:
FEATURES="-distcc"

than go the other way around.

My bad
_________________
"La vie est un formidable scénariste"
- Le cinéaste Bertrand Tavernier, citant un ami
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Gentoo on ARM All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum