On Tue, 29 Aug 2006, Vadim wrote: > I almost build succesfully, but I get some error on the very last step. > I suspect the problem is somewhere in general config, rather than in > particular "matio", but googling did not help for me. > > Can you please help me? > > Error is: > > .... > mv latex/refman.pdf latex/libmatio.pdf > make[1]: Leaving directory `/var/tmp/portage/matio-1.3.0/work/matio/doxygen' > make[1]: Entering directory `/var/tmp/portage/matio-1.3.0/work/matio' > make[1]: Nothing to be done for `all-am'. > make[1]: Leaving directory `/var/tmp/portage/matio-1.3.0/work/matio' > >>> Source compiled. > --------------------------- ACCESS VIOLATION SUMMARY > --------------------------- > LOG FILE = "/var/log/sandbox/sandbox-sci-libs_-_matio-1.3.0-25187.log" > > access_wr: /usr/share/texmf/fonts > mkdir: /var/cache/fonts/tfm > access_wr: /usr/share/texmf/fonts > mkdir: /var/cache/fonts/tfm > -------------------------------------------------------------------------------- > !!! This ebuild is from an overlay: '/usr/local/sci' > Arrgh!!
This kind of access violation again. I was told that they have been fixed once and for all. This has nothing to do with matio. This sort of thing happend to me innumerable times, for various packages. What happens: 1. Some ebuild (usually with the USE flag "doc") starts latex 2. Some font used in the latex file has not yet been used on this particular computer 3. latex starts metafont to generate this font 4. metafont wants to write it to /var/cache/fonts 5. This triggers sandbox violation I don't know how to fight against this. The only way seems to emerge with sandboxing switched off. The next time the same package can be emerged in the normal way, because all fonts used in its documentation has been already generated. This is *absolutely* generic problem, and something should be done about it. Andrey -- [email protected] mailing list
