emerging sci-mathematics/fricas with USE=sbcl fails to install: make[1]: Leaving directory `/var/tmp/portage/sci-mathematics/fricas-1.0.8/work/fricas-1.0.8/contrib/emacs' 79 FriCAS installation finished. rm: cannot remove `/var/tmp/portage/sci-mathematics/fricas-1.0.8/image//usr/lib/fricas/emacs': No such file or directory * ERROR: sci-mathematics/fricas-1.0.8 failed: * rm -r emacs failed Furthermore, when using MAKEOPTS=-j4 it looks like one process is waiting for manual input: ; compiling (MAKEPROP (QUOTE |ExtensionField&|) ...) ; /var/tmp/portage/sci-mathematics/fricas-1.0.8/work/fricas-1.0.8/src/algebra/XF-.fasl written ; compilation finished in 0:00:00.024 Value = #P"/var/tmp/portage/sci-mathematics/fricas-1.0.8/work/fricas-1.0.8/src/algebra/XF-.fasl" (1) -> (1) quit Type: Variable(quit) (2) -> Reproducible: Always
I have a single-core processor, and cannot check parallel make. Please try -j1. If this solves your problems, I'll add -j1 to the ebuild.
(In reply to comment #1) > I have a single-core processor, and cannot check parallel make. Please try -j1. > If this solves your problems, I'll add -j1 to the ebuild. > No, I've tried -j1 already. It still doesn't install with the very same problem (cannot rm -r emacs) Would it be safe to replace this with 'rm -rf emacs', or does this failure come from another more critical issue?
It is absolutely safe to say rm -rf, or even to omit this line completely. But this is really strange. make install installs /usr/lib/fricas/emacs/ with 2 files, at least on 2 computers on which I tested. Why doesn't it do so on your computer? Please post the complete log (with -j1, otherwise it will be difficult to understand) as an attachment.
I have a hypothesis: maybe, you don't have emacs installed? And ./configure detects this fact, and emacs support files are not installed. Then it's better to use rm -rf "${D}"/usr/lib/${PN}/emacs and rm -f "${D}"/usr/bin/efricas - if these files are not installed, there's no need to remove them. So, please, post your log file.
(In reply to comment #4) > I have a hypothesis: maybe, you don't have emacs installed? And ./configure > detects this fact, and emacs support files are not installed. Then it's better > to use > rm -rf "${D}"/usr/lib/${PN}/emacs > and > rm -f "${D}"/usr/bin/efricas > - if these files are not installed, there's no need to remove them. So, please, > post your log file. > eix -I emacs shows that app-admin/eselect-emacs-1.13 app-editors/emacs-22.3-r2 and 23.1-r2 app-editors/xemacs-21.5.29-r2 app-emacs/emacs-common-gentoo-1.2 app-xemacs/xemacs-base-2.19 virtual/emacs-23 are installed! I've put the buildlog into an attachment. Thanks for looking into it!
Created attachment 215822 [details] build.log (compressed with lzma)
Aha! I see. On your system, emake install installed the emacs stuff to ${D}/usr/lib64/fricas/emacs/ but rm -r tries to remove ${D}/usr/lib/fricas/emacs. I need to do something to select /usr/lib or /usr/lib64 automatically. The same goes for the line elisp-install ${PN} "${D}"/usr/lib/${PN}/emacs/*.el which is invoked when USE=emacs. I'll try to write something appropriate tomorrow. But I have no amd64 hardware, so, you'll have to be the guinea pig for the improved ebuild. But if it will work, I'll be able to add ~amd64. Thanks in advance
(In reply to comment #7) > ${D}/usr/lib/fricas/emacs. I need to do something to select /usr/lib or > /usr/lib64 automatically. In all ebuilds, always use /usr/$(get_libdir) to be multilib strict, from the eutils eclass. (In reply to comment #1) > I have a single-core processor, and cannot check parallel make. Please try -j1. > If this solves your problems, I'll add -j1 to the ebuild. You can still test -j2 on a single core processor, and probably -j3. Also if parallel building does not work, QA considers -j1 to be the last resource only when everything else failed.
(In reply to comment #8) > In all ebuilds, always use /usr/$(get_libdir) to be multilib strict, from the > eutils eclass. I know. This is exactly what I've done now (at the moment I'm testing the ebuild on my computer; if nothing breaks down, I'll commit).
I've just committed a corrected ebuild. Could you please sync and check if it works on amd64? (better if you do it both with and without USE=emacs). If it works, I'll add ~amd64 to KEYWORDS.
(In reply to comment #10) > I've just committed a corrected ebuild. Could you please sync and check if it > works on amd64? (better if you do it both with and without USE=emacs). If it > works, I'll add ~amd64 to KEYWORDS. > Thanks, I works flawlessly on amd64 now - even using 4 processors. Helmut.
Keyworded ~amd64. Thanks.
