On Wed, 9 May 2007, Nikolay Sturm wrote:
> * Otto Moerbeek [2007-05-09]:
> > I see systrace things during make:
> >
> > systrace: deny user: otto, prog: /usr/local/bin/fontforge, pid:
> > 32458(0)[25445],
> > policy: /usr/bin/env, filters: 193, syscall: native-fswrite(136),
> > filename: /lilypond-2.8.8_writes_to_HOME/.PfaEdits
>
> legitimate (i.e. systrace is behaving correctly)
>
> > [the build continues]
> >
> > and during make fake:
> >
> > /usr/ports/print/lilypond/w-lilypond-2.8.8/fake-i386/usr/local/share/lilypond/2.8.8/fonts/type1:
> > failed to write cachesystrace: deny user: root, prog:
> > /usr/X11R6/bin/fc-cache, pid: 2897(0)[24786], policy: /usr/bin/env,
> > filters: 193, syscall: native-fswrite(10), filename:
> > /var/cache/fontconfig/9d5904fd1710b46775398a2ce65f03cc-x86.cache-2
> > gmake[1]: *** [install-fc-cache] Error 5
> > gmake[1]: Leaving directory
> > `/usr/ports/print/lilypond/w-lilypond-2.8.8/lilypond-2.8.8/mf'
> > gmake: *** [install] Error 2
> > *** Error code 2
>
> and this as well
>
> If this is all there is, then the port is just broken. But what I got
> from the discussion so far, is that it fails randomly with the
> intercept_get_string error. I started a lilypond build myself a couple
> of minutes ago.
I did 4 builds without seeing "intercept_get_string" or "Operation not
permitted". So I'll wait and see if you can reproduce.
-Otto
