Hi,
Well, this build takes a long time (at least 45 minutes from start to
failure). I'm getting tired of trying over and over again; it took me
about four hours of compiling to prove certainly that Blars suggestion
wouldn't work.
Can you give me a hook script that will give an
Blars Blarson [EMAIL PROTECTED] writes:
In article [EMAIL PROTECTED] [EMAIL PROTECTED] writes:
I'm trying to solve bug 304932/334877.
I can reproduce the build failure using pbuilder, but not when I build
on my own system directly.
I would like to do the pbuilder build and then examine the
On Friday, 21 October 2005 07:26, Thomas Bushnell BSG wrote:
I'm trying to solve bug 304932/334877.
I can reproduce the build failure using pbuilder, but not when I build
on my own system directly.
I would like to do the pbuilder build and then examine the failing
filesystem, but pbuilder
Isaac Clerencia [EMAIL PROTECTED] writes:
On Friday, 21 October 2005 07:26, Thomas Bushnell BSG wrote:
I'm trying to solve bug 304932/334877.
I can reproduce the build failure using pbuilder, but not when I build
on my own system directly.
I would like to do the pbuilder build and then
On Saturday, 22 October 2005 00:36, Thomas Bushnell BSG wrote:
Isaac Clerencia [EMAIL PROTECTED] writes:
On Friday, 21 October 2005 07:26, Thomas Bushnell BSG wrote:
I'm trying to solve bug 304932/334877.
I can reproduce the build failure using pbuilder, but not when I build
on my own
Isaac Clerencia [EMAIL PROTECTED] writes:
I've an ugly hack to get ccache working inside the pbuilder, that saves lots
of build time.
Thanks, but the big build time for lilypond is mostly consumed with
tracing fonts, not compiling C code. :(
Well, I tried that and didn't managed to get it
I demand that Thomas Bushnell BSG may or may not have written...
Isaac Clerencia [EMAIL PROTECTED] writes:
I've an ugly hack to get ccache working inside the pbuilder, that saves
lots of build time.
Thanks, but the big build time for lilypond is mostly consumed with tracing
fonts, not
Darren Salt [EMAIL PROTECTED] writes:
A uuencoded tarball of the generated files would appear to be useful here.
(You'll probably want tar's -m option when unpacking.)
Well, I'm now closer in. The first invocation of lilypond from within
the build fails. But it fails silently. The failing
Thomas Bushnell BSG wrote:
Ok, so lilypond is failing. But dammitall, I can't get it to fail
ever else. If I run this command myself after the failure, it works
fine. Likewise if I invoke make, or if I clean the directory and go
up and do debian/rules build.
Clearly something about
Anthony DeRobertis [EMAIL PROTECTED] writes:
Clearly something about the buildd dynamic environment is *different*
from what I get if I just enter and do it myself, and that difference
causes the generated lilypond to fail.
Quick random guess: Could pbuilder be providing either no stdin, or
Thomas Bushnell BSG [EMAIL PROTECTED] writes:
Quick random guess: Could pbuilder be providing either no stdin, or
something silly for stdin?
It's possible, but the command invoked doesn't (shouldn't?!) read from
stdin. I'll check this out...
Good golly, Miss Molly, that's it. It does
Thomas Bushnell BSG wrote:
Good golly, Miss Molly, that's it. It does indeed blow chunks if the
input is /dev/null (whether within a chroot or just a normal native
build).
Heh. Glad that helped. Took a wild guess from your previous message
about hooks not getting stdin.
Now, you just get
Anthony DeRobertis [EMAIL PROTECTED] writes:
Thomas Bushnell BSG wrote:
Good golly, Miss Molly, that's it. It does indeed blow chunks if the
input is /dev/null (whether within a chroot or just a normal native
build).
Heh. Glad that helped. Took a wild guess from your previous message
Thomas Bushnell BSG [EMAIL PROTECTED] writes:
Anthony DeRobertis [EMAIL PROTECTED] writes:
Thomas Bushnell BSG wrote:
Good golly, Miss Molly, that's it. It does indeed blow chunks if the
input is /dev/null (whether within a chroot or just a normal native
build).
Heh. Glad that helped.
I'm trying to solve bug 304932/334877.
I can reproduce the build failure using pbuilder, but not when I build
on my own system directly.
I would like to do the pbuilder build and then examine the failing
filesystem, but pbuilder always deletes the build directory, and the
manual gives no
In article [EMAIL PROTECTED] [EMAIL PROTECTED] writes:
I'm trying to solve bug 304932/334877.
I can reproduce the build failure using pbuilder, but not when I build
on my own system directly.
I would like to do the pbuilder build and then examine the failing
filesystem, but pbuilder always
16 matches
Mail list logo
