lilypond-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: building lilypond from freebsd ports


From: Glen Hein
Subject: Re: building lilypond from freebsd ports
Date: Tue, 24 Feb 2009 15:44:08 -0700



On Tue, Feb 24, 2009 at 2:38 PM, Matthias Kilian <address@hidden> wrote:
On Tue, Feb 24, 2009 at 01:03:00PM -0700, Glen Hein wrote:
> I sent this question to the freebsd port maintainer, but I also wanted to
> ask this list. I'm trying to build lilypond from the free port
> (print/lilypond) and I'm getting a seg fault from Ghostscript. I was
> wondering if anybody has seen this problem. Here is the error I get from the
> build:
[...]

- is this reproducable, i.e. does it always crash in ghostscript, and at
 the same file?

- does increasing your datasize limit (see ulimit if you're running
 something like ksh or bash) fix the problem?

I'm asking because I'm doing the OpenBSD port of lilypond and
experienced some really ugly bugs when running out of memory (that's
a fault in either guile or lilypond, but not relevant here), and
during testing, I had at least one or two cases where ghostscript
ran out of memory, too.

Ciao,
       Kili

--
make: don't know how to make love. Stop in /usr/src.
               -- make(1)

The problem is reproducible. It fails on the same file every time. I had been building using csh, so as a WAG, I tried bash. The bash ulimit values are:

core file size          (blocks, -c) unlimited
data seg size           (kbytes, -d) 33554432
file size               (blocks, -f) unlimited
max locked memory       (kbytes, -l) unlimited
max memory size         (kbytes, -m) unlimited
open files                      (-n) 32768
pipe size            (512 bytes, -p) 1
stack size              (kbytes, -s) 524288
cpu time               (seconds, -t) unlimited
max user processes              (-u) 5547
virtual memory          (kbytes, -v) unlimited

Building under bash made no difference.

-Glen

http://www.arizonacoppersoft.com/



reply via email to

[Prev in Thread] Current Thread [Next in Thread]