Re: Issue 1635 in lilypond: clean up misleading warnings in website build

[lilypond]

Comment #16 on issue 1635 by percival.music.ca: clean up misleading  
warnings in website build
http://code.google.com/p/lilypond/issues/detail?id=1635

@Colin in comment 10: I personally never trust debuggers; I always add
  print
commands myself, and sometimes add a
  sys.exit(1)
to cause the build to die (so that I don't have too much console output to  
look at)

BTW, what's the minimal way to reproduce these warnings?  Running
  make website
gives you tons of stuff; can't we only look at the xref warnings by doing  
something like:
  ../python/build/extract_texi.py -I ... -I ...  
-I ...  ../Documentation/web.texi
  ../python/build/extract_texi.py -I ... -I ...  
-I ...  ../Documentation/learning learning.tely

?  I mean, the junk in website.make from lines 67 to 71 (inclusive), and 77  
to 81, is what defines the actual command-line.  Could somebody figure out  
the EXACT command-line which gets called for one of the cases where we see  
a bunch of warnings?

I think there's an option you can give to make... maybe -n ...? which  
forces it to print extra information.  That might helpful here, instead of  
just manually looking at variables in website.make.

Also, is website-xrefs called before or after website-bibs ?