On Wed, May 09, 2007 at 08:23:36PM +0200, Otto Moerbeek wrote:
> I did a couple of builds of print/lilypond on i386 of.
>
> 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
Yes, known issue. I hope to update fontforge soon and also add an
option to disable it's autosave "feature" (which is a silly feature
when running fontforge in scripted mode).
> [the build continues]
No systrace warnings and bailouts from mftrace and mf?
That's odd -- I *never* managed to build it within one run. As a
sidenote, I could watch for at least two times a "sticky" failure,
i.e. the build bails out on one specific font (say, for example,
feta26), and *keeps* bailing out on that font no matter of how often
I re-run the build. Then, after doing some find ${WRKDIR} > /dev/null,
the next attempt to build it just succeeds (at least on that font,
maybe on some more).
> 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
Now that's *really* bad. I'll check wether this still happens with
the update for lilypond i'm working on.
Anyway, thanks for feedback.
Ciao,
Kili
--
Ich dachte immer das der heilige Bimbam der Schniedel des Papstes wäre.
-- WoKo in detebe
