qtwebengine-6* needs more than 10GB on /var/tmp?

[ExecutorElassus]

I just want to check something: I tried emerging qtwebengine-6* yesterday, and the build failed at the install phase because it ran out of space on /var/tmp. I have 10GB on that partition; is that not enough?

Thanks for the help!

EE

[logrusx]

I just want to check something: I tried emerging qtwebengine-6* yesterday, and the build failed at the install phase because it ran out of space on /tmp. I have 10GB on that partition; is that not enough?

Thanks for the help!

EE

I hoped that crap goes away in QT 6, but it obviously didn't. Qtwebengine is a repackage of chromium, so expect the same requirements as for chromium.
This is with tests enabled, but I don't think that makes much difference:

Code: Select all

du -sh /var/tmp/portage/www-client/chromium-114.0.5735.110
13G	/var/tmp/portage/www-client/chromium-114.0.5735.110

And also:

Code: Select all

>>> Running pre-merge checks for www-client/chromium-113.0.5672.126
 * Checking for at least 4 GiB RAM ...                                                                                                                                                      [ ok ]
 * Checking for at least 12 GiB disk space at "/var/tmp/portage/www-client/chromium-113.0.5672.126/temp" ...   

But it looks like the ebuild is checking only for 7GiB:

Code: Select all

>>> Running pre-merge checks for dev-qt/qtwebengine-6.5.1
 * Checking for at least 32 GiB RAM ...
 * Amount of main memory is insufficient, but amount
 * of main memory combined with swap is sufficient.
 * Build process may make computer very slow!                                                                                                                                               [ ok ]
 * Checking for at least 7 GiB disk space at "/var/tmp/portage/dev-qt/qtwebengine-6.5.1/temp" ...                                                                                           [ ok ]
 * Checking for at least 150 MiB disk space at "/usr" ...                                                                                                                                   [ ok ]

Also the default portage build location is /var/tmp, not /tmp unless you explicitly changed it.

Best Regards,
Georgi

[ExecutorElassus]

haha whoops, I mistyped. Yes, it was at /var/tmp.

qtwebengine is only required by PyQtWebEngine, but that is in turn required by calibre (needed for reading ebooks) and frescobaldi (music typesetting program I absolutely need since, well, music typesetting is my job).

So I'm 3GB short to install the package. I didn't have this problem with qtwebengine-5*; did they change the requirements? /var/tmp is its own partition; will I need to use vgexpand to add space?

Cheers,

EE

[logrusx]

I'm still using 5.x, why did you switch to 6.x? And I'm using it for the same reason btw.

If you have enough space in your root partition you could mount a file big enough to do the job. I've always wondered why people create headaches for themselves by overly splitting things into different partitions.

p.s. although calibre is actually doing a pretty bad job and I think I'll remove it again, because there's nothing it can do that pandoc combined with libreoffice with an epub extension, can't. All this because of my old ebook reader that can't handle recent epubs. And calibre actually does not do a good job in that either.

p.s. 2 writing the above I realized I should do it and got rid of all this qt crap altogether.

Best Regards,
Georgi

[Zucca]

Also if you have parallel builds, expect even more temp space usage.
Although I suspect emerge is smart enough not to start parallel builds of packages whose combined CHECKREQS_DISK_BUILD value exceeds the limit of space on PORTAGE_TMPDIR.

[asturm]

No, it is simply a function of check-reqs.eclass, not inherent to emerge internals, so it cannot take the combined space requirements into account.

[Hu]

The size requirement for C++ packages can vary with compiler options. The output of emerge --info ; emerge --pretend --verbose dev-qt/qtwebengine might be useful (and build failures usually tell you to post this).

[Ionen]

Did go over 7GB, but my last build wasn't so bad:

Code: Select all

>>> Completed installing dev-qt/qtwebengine-6.5.1 into /var/tmp/portage/dev-qt/qtwebengine-6.5.1/image

 * Final size of build directory: 9358932 KiB (8.9 GiB)
 * Final size of installed tree:  1272960 KiB (1.2 GiB)

Mileage may vary of course, not always obvious to set good checkreqs limits on these without going too high for nothing and considering USE, *FLAGS, and even the compiler choice. Not to mention it tend to go up with every major versions that bumped chromium internally and maintainer may not always think to update it (can file bugs when it gets too away from reality though).

[Zucca]

Not to mention it tend to go up with every major versions that bumped chromium internally and maintainer may not always think to update it (can file bugs when it gets too away from reality though).

There's this bug (enhancement proposal) reported.

No, it is simply a function of check-reqs.eclass, not inherent to emerge internals, so it cannot take the combined space requirements into account.

Ah yes, of course. ;)
Quickly searching I didn't found any bugs related to that. Seems like that's not (usually) a problem for people then.