fusion809
commented
7 years ago My build log is here http://paste2.org/74AOb7NM
Closed fusion809 closed 7 years ago
fusion809
commented
7 years ago My build log is here http://paste2.org/74AOb7NM
kiwifb
commented
7 years ago The building of the documentation, pdf in particular is a memory hog. Upstream is aware of it and I cannot do much to make it fit. By curiosity, how much memory do you have available.
This is one of the reason why I provide pre-build documentation with the doc-html-bin and doc-pdf-bin useflags and why this is the default for the html documentation.
fusion809
commented
7 years ago I have 16 GB RAM available, of all PCs I'd expect mine to manage it.
kiwifb
commented
7 years ago I would have thought it would be sufficient too, but I don't have concrete numbers on that (I have 32GB here). Your /var/tmp/portage` is not in shm is it? That would potentially half your available memory.
fusion809
commented
7 years ago How would I test if it is? If it's not the default it shouldn't be, most of my Gentoo installation is pretty much as default, except I use systemd instead of OpenRC as my init system.
fusion809
commented
7 years ago If it should be listed in /etc/fstab (which Google results seem to suggest) then it's not my /etc/fstab is:
# /etc/fstab: static file system information.
#
# noatime turns off atimes for increased performance (atimes normally aren't
# needed); notail increases performance of ReiserFS (at the expense of storage
# efficiency). It's safe to drop the noatime options if you want and to
# switch between notail / tail freely.
#
# The root filesystem should have a pass number of either 0 or 1.
# All other filesystems should have a pass number of 0 or greater than 1.
#
# See the manpage fstab(5) for more information.
#
# <fs> <mountpoint> <type> <opts> <dump/pass>
# NOTE: If your BOOT partition is ReiserFS, add the notail option to opts.
#
# NOTE: Even though we list ext4 as the type here, it will work with ext2/ext3
# filesystems. This just tells the kernel to use the ext4 driver.
#
# NOTE: You can use full paths to devices like /dev/sda3, but it is often
# more reliable to use filesystem labels or UUIDs. See your filesystem
# documentation for details on setting a label. To obtain the UUID, use
## <fs> <mountpoint> <type> <opts> <dump/pass>
/dev/sda1 /boot/efi vfat noauto,noatime 1 2
/dev/sda2 /ot ext4 noatime 0 1
/dev/sda4 / ext4 noatime 0 1
/dev/sdb1 /data ext4 noatime 0 1
/dev/sda3 /funtoo ext4 noatime 0 1On systemd you /tmp is on /dev/shm by default but that's not it. After checking carefully your log you are not even building pdf. You are still building html (which matches my understanding better, I didn't think you could build the html and not the pdf).
fusion809
commented
7 years ago I just tried to recompile this package with the same USE flags and it gave a slightly different error:
Underfull \hbox (badness 10000) in paragraph at lines 33159--33160
\T1/ptm/m/n/10 Bases: \T1/pcr/m/n/10 sage.tensor.modules.free_module_alt_form.F
reeModuleAltForm \T1/ptm/m/n/10 ,
[428] [429] [430] [431] [432] [433] [434]
Overfull \hbox (8.34448pt too wide) in paragraph at lines 33729--33729
[]\T1/ptm/m/it/10 domain\T1/ptm/m/n/10 ,
Underfull \hbox (badness 10000) in paragraph at lines 33729--33729
\T1/ptm/m/it/10 la-
Overfull \hbox (47.82422pt too wide) in paragraph at lines 33729--33729
\T1/ptm/m/it/10 tex_name=None\T1/pcr/m/n/10 )
Underfull \hbox (badness 8113) in paragraph at lines 33773--33780
\T1/ptm/m/n/10 where $\OML/cmm/m/it/10 T[]\OT1/cmr/m/n/10 (\OML/cmm/m/it/10 M\O
T1/cmr/m/n/10 )$ \T1/ptm/m/n/10 stands for the $\OML/cmm/m/it/10 C[]\OT1/cmr/m/
n/10 (\OML/cmm/m/it/10 M\OT1/cmr/m/n/10 )$\T1/ptm/m/n/10 -module of ten-sor fie
lds of type $\OT1/cmr/m/n/10 (\OML/cmm/m/it/10 k; l\OT1/cmr/m/n/10 )$ \T1/ptm/m
/n/10 on $\OML/cmm/m/it/10 M$ \T1/ptm/m/n/10 (cf.
[435] [436] [437] [438] [439] [440] [441] [442] [443]
Underfull \hbox (badness 8170) in paragraph at lines 34469--34469
[]\T1/ptm/m/it/10 frame=None\T1/ptm/m/n/10 , \T1/ptm/m/it/10 chart=None\T1/ptm/
m/n/10 , \T1/ptm/m/it/10 sym-bol=None\T1/ptm/m/n/10 , \T1/ptm/m/it/10 la-tex_sy
mbol=None\T1/ptm/m/n/10 , \T1/ptm/m/it/10 in-dex_labels=None\T1/ptm/m/n/10 ,
Underfull \hbox (badness 10000) in paragraph at lines 34469--34469
\T1/ptm/m/it/10 in-dex_latex_labels=None\T1/ptm/m/n/10 , \T1/ptm/m/it/10 co-or-
di-nate_labels=True\T1/ptm/m/n/10 , \T1/ptm/m/it/10 only_nonzero=True\T1/ptm/m/
n/10 ,
[444] [445] [446] [447] [448] [449] [450] [451] [452] [453] [454]
Chapter 3.
Overfull \hbox (29.99387pt too wide) in paragraph at lines 35284--35284
[]\T1/ptm/m/it/10 vector_field_module\T1/ptm/m/n/10 ,
Underfull \hbox (badness 10000) in paragraph at lines 35284--35284
\T1/ptm/m/it/10 ture=None\T1/ptm/m/n/10 ,
Underfull \hbox (badness 10000) in paragraph at lines 35284--35284
\T1/ptm/m/it/10 la-
Overfull \hbox (17.82422pt too wide) in paragraph at lines 35284--35284
\T1/ptm/m/it/10 tex_name=None\T1/pcr/m/n/10 )
[455] [456] [457] [458] [459]
Underfull \hbox (badness 10000) in paragraph at lines 35668--35670
[]\T1/ptm/m/n/10 Note that a bet-ter dis-play of the Christof-fel sym-bols is p
ro-vided by the method
Underfull \hbox (badness 10000) in paragraph at lines 35686--35686
[]\T1/ptm/m/it/10 chart=None\T1/ptm/m/n/10 , \T1/ptm/m/it/10 sym-bol=None\T1/pt
m/m/n/10 , \T1/ptm/m/it/10 la-tex_symbol=None\T1/ptm/m/n/10 ,
Underfull \hbox (badness 10000) in paragraph at lines 35686--35686
\T1/ptm/m/it/10 in-dex_labels=None\T1/ptm/m/n/10 , \T1/ptm/m/it/10 in-dex_latex
_labels=None\T1/ptm/m/n/10 ,
Underfull \hbox (badness 10000) in paragraph at lines 35686--35686
\T1/ptm/m/it/10 co-or-di-nate_labels=True\T1/ptm/m/n/10 , \T1/ptm/m/it/10 only_
nonzero=True\T1/ptm/m/n/10 ,
[460] [461] [462] [463] [464] [465] [466] [467] [468]
Underfull \hbox (badness 10000) in paragraph at lines 1--36327
[]\T1/pcr/m/n/10 subdomain \T1/ptm/m/n/10 -- open sub-set $\OML/cmm/m/it/10 U$
\T1/ptm/m/n/10 of the met-ric's do-main (must be an in-stance of
[469] [470] [471] [472] [473] [474] [475 * The ebuild phase 'compile' with pid 12639 appears to have left an orphan
* process running in the background.
>>> Failed to emerge sci-mathematics/sage-7.6, Log file:
>>> '/var/tmp/portage/sci-mathematics/sage-7.6/temp/build.log'
* Messages for package sci-mathematics/sage-7.6:
* The ebuild phase 'compile' with pid 12639 appears to have left an orphan
* process running in the background.
* ERROR: sci-mathematics/sage-7.6::sage-on-gentoo failed (compile phase):
* failed to produce pdf doc
*
* Call stack:
* ebuild.sh, line 115: Called src_compile
* environment, line 4711: Called distutils-r1_src_compile
* environment, line 1320: Called _distutils-r1_run_common_phase 'python_compile_all'
* environment, line 517: Called _distutils-r1_run_foreach_impl 'python_compile_all'
* environment, line 531: Called python_foreach_impl 'distutils-r1_run_phase' 'python_compile_all'
* environment, line 3982: Called multibuild_foreach_variant '_python_multibuild_wrapper' 'distutils-r1_run_phase' 'python_compile_all'
* environment, line 2976: Called _multibuild_run '_python_multibuild_wrapper' 'distutils-r1_run_phase' 'python_compile_all'
* environment, line 2974: Called _python_multibuild_wrapper 'distutils-r1_run_phase' 'python_compile_all'
* environment, line 873: Called distutils-r1_run_phase 'python_compile_all'
* environment, line 1308: Called python_compile_all
* environment, line 3541: Called die
* The specific snippet of code:
* "${PYTHON}" sage_setup/docbuild/__main__.py all pdf || die "failed to produce pdf doc";
*
* If you need support, post the output of `emerge --info '=sci-mathematics/sage-7.6::sage-on-gentoo'`,
* the complete build log and the output of `emerge -pqv '=sci-mathematics/sage-7.6::sage-on-gentoo'`.
* The complete build log is located at '/var/tmp/portage/sci-mathematics/sage-7.6/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/sci-mathematics/sage-7.6/temp/environment'.
* Working directory: '/var/tmp/portage/sci-mathematics/sage-7.6/work/sage-7.6/src-python2_7'
* S: '/var/tmp/portage/sci-mathematics/sage-7.6/work/sage-7.6/src'OK reviewing your flags from the first post, there must be an error in the ebuild you shouldn't be building this. What's more you are building the html doc in the pdf phase. So something must be calling the building of the pdf but not html.
Have to leave you hanging for the next hour or so.
fusion809
commented
7 years ago Well I've decided 'til you have a solution, at least, to just do everything the easy way and emerge the package with the binary docs.
kiwifb
commented
7 years ago OK one of the thing you quoted didn't match your build log. So I thought there was something wrong with the ebuild but no.
In this instance I see your MAKEOPTS is -j9 your amount of memory per tasks is probably too small. Could you try at -j4 next time?
fusion809
commented
7 years ago OK, giving your suggestion a go.
fusion809
commented
7 years ago It worked! Thanks, closing.
Hi,
sci-mathematics/sage builds fine for most of the build, except near the end when it is trying to build the Sage PDF docs which is when it returns:
Now you might wonder how I managed to build sci-mathematics/sage given the sage-latex build fails (per #461), oddly enough after I installed a few extra deps sage-latex is no longer pulled in by sage.
emerge -pqvreturns:while
emerge --inforeturns:Thanks for your time, Brenton