--------------------------- ACCESS VIOLATION SUMMARY --------------------------- LOG FILE = "/tmp/sandbox-lyx-1.3.0-24990.log" mkdir: /var/cache/fonts/tfm/jknappen mkdir: /var/cache/fonts/tfm/jknappen/ec -------------------------------------------------------------------------------- Reproducible: Always Steps to Reproduce:
Created attachment 8318 [details] capture from make install
I dont know why, but I have found that adding a line: econf "" before line 41 in /usr/portage/app-office/lyx/lyx-1.3.0.ebuild may solve your problem. cf bugzilla.lyx.org #874.
This might be coincidence, but it is similar enough to note here. A couple days ago, with 'emerge html2latex' (required by something else), the I received the same Access Violation with LOG_FILE=/tmp/sandbox-pyOpenSSL-0.5.1-30089.log and said file contains mkdir: /usr/share/texmf/fonts/tfm/jknappen mkdir: /usr/share/texmf/fonts/tfm/jknappen/ec I note this because of the unusual permissions on /usr/share/texmf/fonts/tfm: 1 drwxrwxrwt 11 1340 1340 272 Feb 18 17:38 tfm/ Creating the directories by hand ant retrying gives open_wr: /usr/share/texmf/fonts/source/jknappen/ec/mf30534.tmp unlink: /usr/share/texmf/fonts/source/jknappen/ec/ecrm1000.mf And here, we have drwxrwxrwt 5 1340 1340 120 Sep 13 15:29 jknappen/ I am not sure why tetex sets the sticky bit on these directories (and, of course, I have no userid=1340). Then again, this might be totally unrelated to the problem with lyx.
I had the same problems, I solved it by using the patch provided in this bug report: http://bugs.gentoo.org/show_bug.cgi?id=15425 After modfiing lib/configure, I called ebuild compile, install and merge manually, and the sandbox violation did not occur anymore.
Added this patch to the new lyx-1.3.2 version ebuild that is now in portage. Should fix the sandbox violation.
