Graham et al,
In the instructions for getting the source code, why not just use
git-clone? Is there a difference? The currently suggested method of
remote-add + checkout produces a bunch of warnings (below).
Andrew
and...@obi-wan:~$ mkdir lilypond-web
and...@obi-wan:~$ cd lilypond-web
and...@o
Hi Jan,
On Mon, Feb 16, 2009 at 11:19:32AM +0100, Jan Nieuwenhuizen wrote:
> iOn zo, 2009-02-15 at 19:13 -0800, Patrick McCarty wrote:
>
> > Those files exist, and libintl.la looks correct. It is not executable
> > (755) like all of the other .la files I see, but this does not seem to
> > make a
Here's a patch for the FIXME DOING SOMETHING part.
Jon
On Sun, Feb 15, 2009 at 4:34 PM, Valentin Villenave
wrote:
> 2009/2/15 Graham Percival :
> > You can hopefully figure out what the FIXME DOING SOMETHING means,
> > and then write a patch to fix the CG on this issue. If not, bug
> > Valentin
On Sat, Feb 14, 2009 at 03:04:55AM +0100, John Mandereau wrote:
> Sawada wrote:
>> In that sub subsection, there is a command as following:
>> nice make LILYPOND_EXTERNAL_BINARY=/path/to/bin/lilypond web
>>
>> I wonder "nice" is not needed, though it is harmless.
>>
> "nice" is not needed, that'
On Mon, Feb 16, 2009 at 10:53 AM, Jan Nieuwenhuizen
wrote:
>> Ah, my restrict-stat.c hack broke your stat function. Ouch. I had
>> the impression that Han-Wen also ran 32 bits and it worked there.
>> Otherwise I hope he can give some insight/fixes :-) Han-Wen?
>
> This is getting uglier than I
On ma, 2009-02-16 at 11:19 +0100, Jan Nieuwenhuizen wrote:
Hi Patrick,
> > >LIBRESTRICT=open:stat bin/gub mingw::guile # or mingw::lilypond
> >
> > Starting fresh, this halts at tools::tar. Attached are relevant
> > sections of build.log and config.log.
>
> Ah, my restrict-stat.c hack bro
On ma, 2009-02-16 at 01:11 +0100, John Mandereau wrote:
> Jan Nieuwenhuizen a écrit :
> > Does the attached patch help?
> It doesn't, I get exactly the same error :-(
Thanks for trying... I'm a bit at loss how to fix this without being
able to reproduce it. I can think of one other thing to try,
iOn zo, 2009-02-15 at 19:13 -0800, Patrick McCarty wrote:
Hi Patrick,
> Those files exist, and libintl.la looks correct. It is not executable
> (755) like all of the other .la files I see, but this does not seem to
> make a difference; compilation still fails.
Ok. I figure that libtool reads f
