dev-qt/qtwebengine failed to compile

[Applescruff]

Hello Gentoo Community Support,
I need some assistance to emerge dev-qt/qtwebengine sucessfully.
I am new to using dpaste so this first attempt at sharing may not be the correct way to share.
Please let me know if I need to proceed in a better way.
The links below to emerge --info, build.log, and emerge -pqv

https://dpaste.com/G3YJEDS88

https://dpaste.com/ESDWUBVBA

https://dpaste.com/DM9GD3BR2

Thank you for you time, efforts, and skills.

[Goverp]

I'm not sure what the second file is, but AFAIK it's not the build.log. It looks like a dump of python variables from somewhere in portage. ... Can you check please?

I'm not sure if USE="jumbo-build" is working at the moment - it broke earlier this year.

You have --jobs=16 in both MAKEOPTS and PORTAGE_DEFAULT_OPTS. The first applies to the number of concurrent compilations per emerge, the second the number of emerges, so if they were both correct you'd be trying to do 256 concurrent compilations, which would bring anything less than a maximal Threadripper with 1/5 Terabyte memory to its knees!
You probably want something more like MAKEOPTS --jobs 8 and PORTAGE_DEFAULT_OPTIONS --jobs 2 or 3.
However, at the moment, it's moot, as you've misspelt MAKE0PTS with a 0, not an O, in make.conf...

[Applescruff]

Thank you for your comments. I'm not sure how I got the 'not the build.log'. I repeated the cat /var/tmp/portage/dev-qt/qtwebengine-5.15.2_p20211207/temp/build.log > Desktop/build.log_dev-qt_qtwebengine. While attempting to pastebin this file I discovered it is too large, 35MB+, so I'm wondering how to proceed. Is it useful to find the section where the compile begins to fail and paste from there to EOF, or to append the beginning file info + the section where the compile begins to fail to EOF?
I'm currently attemping to emerge dev-qt/qtwebengine with MAKEOPTS="-j2 -l2" and EMERGE_DEFAULT_OPTS="--jobs=2 --load-average=2.0 to see if better results come from the "nice and easy" approach to emerging. Thank you for pointing out the need to correct my typo error and the critique of the relation between MAKEOPTS settings and EMERGE_DEFAULT_OPTS settings.
I also did a bit of exploring the jumbo-build, but have not determined if it remains fixed.
I'll post again when this emerge completes.

[Goverp]

What I do in general with emerge logs, and this may not work for giants like qtwebengine, is to use "less -i" to view the file: page to the end, and then search backwards with "?error|failure" until I find a line that looks like a real error message, rather than the error percolating up through "make" recursion levels. You might then be able to paste the relevant part. But as I say, this might not be practicable for qtwebengine logs.

[Applescruff]

Thank you for the tip. I will utilize it next chance I get.
For now though, great news! The "nice and easy" approach delivered the installed qtwebengine. It was the first ebuild on a list of 222 emerging and installing updating programs @world. After ebuild 2 through 186 loaded, qtwebengine successfully installed. I watched the Tuxedo System Monitor throughout the process and had the thought that like when driving a car with a big block V8, of course you can put the pedal to the metal, but to arrive home safely, you will drive the speed limit and obey the rules of the road.
Thank you again for your wise suggestions.

[ngorelen]

Thank you guys. I had the same problem.
Your suggested command works for me too:

Code: Select all

EMERGE_DEFAULT_OPTS="--jobs=2 --load-average=2.0" MAKEOPTS="-j2 -l2" emerge dev-qt/qtwebengine

[grknight]

Thank you guys. I had the same problem.
Your suggested command works for me too:

Code: Select all

EMERGE_DEFAULT_OPTS="--jobs=2 --load-average=2.0" MAKEOPTS="-j2 -l2" emerge dev-qt/qtwebengine

FWIW, setting EMERGE_DEFAULT_OPTS is rather pointless here unless there are further options to ignore. Every option specified to emerge directly overrides the defaults.

You also forgot oneshot here.

The better command is:

Code: Select all

MAKEOPTS="-j2 -l2" emerge --jobs=2 --load-average=2.0 --oneshot dev-qt/qtwebengine

or (short options)

Code: Select all

MAKEOPTS="-j2 -l2" emerge -j2 -l2 -1 dev-qt/qtwebengine

[ngorelen]

Thank you grknight for further clarifications and suggestions.
Yes, i had (as well as others) MAKEOPTS set up to different (default) values in my make.conf file.
And i guess you don't want to make that change through make.conf. Issuing one line command makes perfect sense.

After reading both "man make.conf" and "man emerge" it looks to me that the options in

Code: Select all

MAKEOPTS="-j2 -l2" emerge -j2 -l2 -1 dev-qt/qtwebengine

are redundant to each other. That is the following should suffice:

Code: Select all

 emerge -j2 -l2 -1 dev-qt/qtwebengine 

[Hu]

Yes, i had (as well as others) MAKEOPTS set up to different (default) values in my make.conf file.
And i guess you don't want to make that change through make.conf. Issuing one line command makes perfect sense.

Specifying an override in the environment is convenient for testing, but if you will always need this MAKEOPTS override for dev-qt/qtwebengine, you would be better served using package.env to define a per-package override persistently, so that Portage always uses the reduced MAKEOPTS for this package. Then you can just write emerge -1 dev-qt/qtwebengine and get the right result automatically, without needing to remember to set this override. This is also helpful from the perspective that if emerge schedules multiple packages, one of which is dev-qt/qtwebengine, you cannot use an environment override to affect only dev-qt/qtwebengine; you would affect every package in that emerge run. If the override is done via package.env, then Portage will do the right thing even in a multiple package run.

After reading both "man make.conf" and "man emerge" it looks to me that the options in

Code: Select all

MAKEOPTS="-j2 -l2" emerge -j2 -l2 -1 dev-qt/qtwebengine

are redundant to each other. That is the following should suffice:

Code: Select all

 emerge -j2 -l2 -1 dev-qt/qtwebengine 

That is not correct. MAKEOPTS specifies options to Make (and other Make-like programs). That tells a Make how many recipes it can run at once. emerge -j2 tells Portage to run up to 2 independent package builds at once. You can use both at once, in which case up to 2 packages can run up to 2 recipes each, for a total of 4 concurrent recipes.

[ngorelen]

To resolve the issue (it came up just now), I ran the world update using:

emerge -j2 -l2 -uvNDq world

This rebuilt the dependency chain and, in particular, updated qtwebengine and webkit-gtk, which would otherwise have remained in an unupdated state.

[ngorelen]

Hmm, i followed my own advice and after seeing that problem again I got an error from emerge world, qtwebengine part of it: https://bpa.st/VWDA
Then after I fixed it, another error came up from grub: https://bpa.st/4WPQ
I don't think there is an issue with the disk space cause I have 12G of free space - should be enough.

[logrusx]

I'm not sure how I got the 'not the build.log'.

I guess you passed -d instead of -D to emerge and thus got a lot of portage debug logs in the build.log.

Best Regards,
Georgi

[Ionen]

I don't think there is an issue with the disk space cause I have 12G of free space - should be enough.

Note that (for qtwebengine), that's rather borderline, qtwebengine-6.10.x needs about 10-11G to build in typical circumstances (could vary), and if there was anything else using up space at same time then running out is quite possible.

grub doesn't use much on the other hand, but I can't say what happened without a build log.