Perryg wrote:Sorry I don't use pelican. I use latex from texlive.
You do need to install beramono.sty for latex to get it to compile though.
Thanks Perry - apologies for late reply, but I was on vacation with very little access
to the 'net... I did have beramono.sty, since at least the F19 times (I keep around
an older Fedora release in case the new one breaks spectacularly):
Uncompressing VirtualBox for Linux installation...........
VirtualBox Version 4.3.28_OSE r100309 (2015-07-27T13:40:04Z) installer
Removing previous installation of VirtualBox 4.3.28_OSE r100309 from /opt/VirtualBox
Installing VirtualBox to /opt/VirtualBox
Python found: python, installing bindings...
Building the VirtualBox kernel modules
VirtualBox has been installed successfully.
You will find useful information about using VirtualBox in the user manual
/opt/VirtualBox/UserManual.pdf
and in the user FAQ
http://www.virtualbox.org/wiki/User_FAQ
We hope that you enjoy using VirtualBox.
Any idea on how I can debug this 5.0.0 failing build issue?
Still stuck so far (and getting ready to report build issues under 4.2.0-rc kernels)...
I'll be getting a F22 system ready in the next weeks to see whether the issue is still there (hopefully it won't) - however a pointer about where to look in the Makefiles to try and hunt a reason why the build fails would still be much appreciated (alas, my kbuild-fu is basically zero).
Actually there are a few missing files in the tarball. This is fixed in the subversion repository and will be fixed in the next 5.0.x maintenance release.
Frank Mehnert wrote:Actually there are a few missing files in the tarball. This is fixed in the subversion repository and will be fixed in the next 5.0.x maintenance release.
Hi Frank - I just tried 5.0.4 and it still fails the same way, is that expected?
I even tried the w/a of touching/chmoding the validatemanual.run file and re-run my build scripts - but that also doesn't work for me (didn't delete the "out" dir though).
[asuardi@xbox trunk]$ ls -l /share/vbox/trunk/out/linux.amd64/release/obj/manual/en_US/validatemanual.run
ls: cannot access /share/vbox/trunk/out/linux.amd64/release/obj/manual/en_US/validatemanual.run: No such file or directory
[asuardi@xbox trunk]$
Frank Mehnert wrote:Actually there are a few missing files in the tarball. This is fixed in the subversion repository and will be fixed in the next 5.0.x maintenance release.
Hi Frank - I just tried 5.0.4 and it still fails the same way, is that expected?
I even tried the w/a of touching/chmoding the validatemanual.run file and re-run my build scripts - but that also doesn't work for me (didn't delete the "out" dir though).
Thanks,
--alessandro
Indeed, 5.0.4 build still fails at the same point.
But it works when I touching the validatemanual.run file (it seems that chmoding is not needed).
I tried using kmk as you're doing instead of kmk all as per the procedure taken from PerryG's FAQs here - still no luck; an empty .sh yields an Error 2 regardless.
Build still fails in SVN r57900.
Hopefully I'll be able to set up a new OL7.1 host (and maybe a F22 VM within said host) to try compilation there this week.