On 12/10/2010 01:53 PM, Graham Percival wrote:
> On Fri, Dec 10, 2010 at 01:03:37PM +0200, Dave Plater wrote:
>   
>> Hi, openSUSE:Factory lilypond is failing to build documentation since
>> texlive was updated, I've added the updated texlive-bin package to the
>> successful 11.3 build and it causes the same failure.
>> I can't quite understand bibtex's use of /tmp in this failure :
>> make[3]: Entering directory
>>     
> Well, the first step is to isolate the problem.  If you go to this
> directory:
>
>   
>> `/usr/src/packages/BUILD/lilypond-2.12.3/Documentation/bibliography'
>>     
> and then enter this command all as one line:
>
>   
>> BSTINPUTS=.
>> /usr/src/packages/BUILD/lilypond-2.12.3/scripts/build/out/bib2html -o
>> out-www/colorado.html colorado.bib
>>     
> then does it produce a .html file in out-www/ ?
> (oh, you need to create the out-www/ directory first)
>
> I'm not certain precisely why bibtex wants to write stuff to
> /tmp/, but it'll be a lot easier to debug the problem once you
> reduce it to a single command-line.
>
>
> Be aware that this part of the build process has changed in 2.13
> and the upcoming 2.14 release.
>
> Cheers,
> - Graham
>
>   
I did that and it gives the same error, I made a local build and entered
the directory :
Arbuthnot:/usr/src/packages # pushd
/usr/src/packages/BUILD/lilypond-2.12.3/Documentation/bibliography
/usr/src/packages/BUILD/lilypond-2.12.3/Documentation/bibliography
/usr/src/packages
Arbuthnot:/usr/src/packages/BUILD/lilypond-2.12.3/Documentation/bibliography
# BSTINPUTS=.
/usr/src/packages/BUILD/lilypond-2.12.3/scripts/build/out/bib2html -o
out-www/colorado.html colorado.bib
Invoking `bibtex /tmp/tmp65e8GYbib2html'

bibtex: Not writing to /tmp/tmp65e8GYbib2html.blg (openout_any = p).
I couldn't open file name `/tmp/tmp65e8GYbib2html.blg'

And the same result. Can you spot any change in the normal bibtex behaviour?
Thanks
Dave P

_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Reply via email to