On Fri, Jun 17, 2011 at 10:06:01PM +0200, Matthias Kilian wrote:
> Just wait a few days until I've some spare time available to help
> you with this, will you?
Certainly! Thank you for your interest; I know that you know far
more than me about this.
Please also take a look at two recent git comm
On Fri, Jun 17, 2011 at 07:35:19PM +0100, Graham Percival wrote:
> > >Again, on the shell, it would be something like this:
> > > make ...blah... || echo "build failed" && tail logfile
> > >but there might be a nicer way to do it.
> >
> > but then when blah fails, make will not stop, since the re
On Fri, Jun 17, 2011 at 07:35:19PM +0100, Graham Percival wrote:
> On Fri, Jun 17, 2011 at 02:18:55PM -0400, Julien Rioux wrote:
> > On 17/06/2011 2:11 PM, Graham Percival wrote:
> > > make ...blah... || echo "build failed" && tail logfile
> >
> > but then when blah fails, make will not stop, sin
On Fri, Jun 17, 2011 at 02:18:55PM -0400, Julien Rioux wrote:
> On 17/06/2011 2:11 PM, Graham Percival wrote:
> >Again, on the shell, it would be something like this:
> > make ...blah... || echo "build failed" && tail logfile
> >but there might be a nicer way to do it.
>
> but then when blah fail
On 17/06/2011 2:11 PM, Graham Percival wrote:
On Fri, Jun 17, 2011 at 06:32:22PM +0100, Phil Holmes wrote:
- Original Message - From: "Graham Percival"
with my memory of recent discussions, I know to look in
/home/gperciva/src/lilypond/build/out/lybook-db/snippet-names--25272072.log
On Fri, Jun 17, 2011 at 06:32:22PM +0100, Phil Holmes wrote:
> - Original Message - From: "Graham Percival"
>
> >with my memory of recent discussions, I know to look in
> >/home/gperciva/src/lilypond/build/out/lybook-db/snippet-names--25272072.log
>
> This kind of issue prompted my sugges
- Original Message -
From: "Graham Percival"
[snip]
with my memory of recent discussions, I know to look in
/home/gperciva/src/lilypond/build/out/lybook-db/snippet-names--25272072.log
for hints, but that's not at all obvious from just looking at the
command-line output. Inside that fil
On Fri, Jun 17, 2011 at 04:35:47PM +0100, Phil Holmes wrote:
> - Original Message - From: "Graham Percival"
>
> >So when Reinhold and I say "we must not hide any errors in make",
>
> In that case, I can't see that anything I can do can prevent these
> being visible. The only thing I can
- Original Message -
From: "Graham Percival"
To: "Phil Holmes"
Cc:
Sent: Friday, June 17, 2011 4:19 PM
Subject: Re: Logfiles from build
On Fri, Jun 17, 2011 at 11:53:15AM +0100, Phil Holmes wrote:
- Original Message - From: "Graham Percival"
On Fri, Jun 17, 2011 at 11:53:15AM +0100, Phil Holmes wrote:
> - Original Message - From: "Graham Percival"
>
>
> >On Fri, Jun 17, 2011 at 09:34:38AM +0100, Phil Holmes wrote:
> >Before any work is done on the central log/ or
> >build-log/ directory, I would really like to have the capabi
On Fri, Jun 17, 2011 at 04:19:33PM +0100, Graham Percival wrote:
> In keeping with the GOP mentor discussion, (proposal summary)
> http://lilypond.org/~graham/gop/gop_2.html
> I feel compelled to warn you that you do not have "a realistic
> expectation of how things will work". I hate to say it, b
On 11-06-17 02:34 AM, Phil Holmes wrote:
I realise I may be on thin ice here...
As many will know, I'm trying to reduce the clutter that appears on
screen as lily's build progresses. A key way of doing this is by
redirecting output to log files. If you've recently done a make doc
and look i
- Original Message -
From: "Graham Percival"
To: "Phil Holmes"
Cc:
Sent: Friday, June 17, 2011 11:41 AM
Subject: Re: Logfiles from build
On Fri, Jun 17, 2011 at 09:34:38AM +0100, Phil Holmes wrote:
I'm now thinking it would actually be better to gather al
- Original Message -
From: "Graham Percival"
To: "Phil Holmes"
Cc:
Sent: Friday, June 17, 2011 11:41 AM
Subject: Re: Logfiles from build
On Fri, Jun 17, 2011 at 09:34:38AM +0100, Phil Holmes wrote:
I'm now thinking it would actually be better to gather al
On Fri, Jun 17, 2011 at 09:34:38AM +0100, Phil Holmes wrote:
> I'm now thinking it would actually be better to gather all the
> output from make in a single directory, something like
> build/makelogs. That way, you'd only need to look in one place for
> any failing logged output, and it would prob
I realise I may be on thin ice here...
As many will know, I'm trying to reduce the clutter that appears on screen
as lily's build progresses. A key way of doing this is by redirecting
output to log files. If you've recently done a make doc and look in
build/out/lybook-db you'll see some of t
16 matches
Mail list logo
