Summary: | emerge of lyx1.3.4 failed with "Access violation" from sandbox | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | anonymus <Sebydra> |
Component: | Current packages | Assignee: | Text-Markup Team (OBSOLETE) <text-markup+disabled> |
Status: | RESOLVED NEEDINFO | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | 2004.2 | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
anonymus
2004-09-23 15:22:06 UTC
Please attach full emerge log here. Also, does lyx-1.3.5.ebuild fail with the same error? hy ! remember #54221 and #42478 an maybe others. If my tip in #54479 does make sense, we should try to solve all errors with -j1. A. Maybe it was not a real solution, or B. maybe all compile-runs who fail when using -j2 at different points are caused by parallel building no matter at which point they fail. Is there anyone who did get lyx-1.3.4 compiled without errors when -j2 was used ? On real SMP-machines, HT, or just of fun? It does build on my x86 and ppc machines with -j4, though they are not SMP or HT machines. If lyx tries to modify /usr/share/texmf/web2c/latex.log it is likely that you have something wrong in tetex installation, and we need full compile log to determine what's wrong on your system. First, sorry for not keeping track of this thread so long. I couldn't reproduce the error because I completly reinstalled my system, but had other errors instead in lyx dependencies (t1lib, chktex). Now i have solved them by simply preventing portage from installing these "dependencies", and lyx(1.3.4) installs without problems now. So your propably right, with the presumption it could be a failure in the tetex installation. It would help to put a hint at the "enter a bug"-page, also to test with the ~x86=testversions before submitting a bug, and to submit the complete compileroutput as attachment, and not only the error messages. I'm sure a lot of persons forget this, like me. Another problem is that normaly only a little part of the output fits in the terminalbuffer. So if you haven't redirected the output before, you need to restart compilation process to get the hole output. This can be annoying if it tooks an hour... Is there any standartfile the output is saved to while being writen to the standartoutput? @Karl Ernst I already tested to compile lyx with -j 1 (before I changed my system) but it didn't helped. The option -j n is an internal option for gcc to split into multiple threads an (possibly) run faster, perhaps using more memory. Its other behaviour mustn't change. So if some packages only compile with -j 1, it's shurely an issue to gcc or your system configuration, not to these packages. By the way I use -j 2 on a single processor system and never experienced problems with it. For optimal speed you should use one thread more than you have cpus. No worries, that's okay. In this case, if you had set PORT_LOGDIR in /etc/make.conf (sample configuration is in /etc/make.conf, so all you have to do is comment out PORT_LOGDIR line) you would have compilation log automagically. |