When emerging Lyx 1.3.2, I get the following error: -----------------------ACCESS VIOLATION SUMMARY------------------------ LOG FILE = "/tmp/sandbox-lyx-1.3.2-28858.log" mkdir: /var/cache/fonts/tfm/jknappen mkdir: /var/cache/fonts/tfm/jknappen/ec ------------------------------------------------------------------------------------------------- Reproducible: Always Steps to Reproduce: 1. 2. 3. Expected Results: Completed emerge without errors
Ok, so emerging from a console rather than an xterm fixes this problem. Maybe not a bug afterall?
I get the error in either way, emerging from an xterm or from the console - doesn't matter.
Hmm, It was actually a couple of days time between when I emerged using xterm and when I emerge from a console. I saw that advice for something else in portage so I tried it and it worked. I guess it must have been something else I did in the couple of days. Can't remember what though.
same problem over here. the log file doesn't provide any useful information.
This seems to the the sandbox violation reported in Bug #15425 and Bug #15766 . The lyx-1.3.2-configure.diff patch does not seem to work. It creates this line in the lib/configure script: rm -f wrap_chkconfig.ltx -no-mktex=tfm chkconfig.vars chkconfig.classes chklayouts.tex But when the configure script is run we see this: checking LaTeX configuration... auto rm: invalid option -- n Try `rm --help' for more information. +Inspecting your LaTeX configuration. The "-no-mktex=tfm" provided by the patch is seen as a flag of the rm command. Instead the -no-mktex=tfm flag should be associated with the latex command. Adding --no-mktex=tfm a little furthur down the configure script fixes things nicely. We need to change eval ${LATEX} wrap_chkconfig.ltx 2>/dev/null | grep '^\+' to eval ${LATEX} --no-mktex=tfm wrap_chkconfig.ltx 2>/dev/null | grep '^\+'
Created attachment 16857 [details, diff] Patch to run a latex check with the --no-mktex=tfm flag
thanks, once again, to brandy for supplying the patch. i've added the fix to 1.3.2 and 1.3.2-r1
