log files

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

log files

Jean-Charles MALAHIEUDE
Hi Francisco!

Have you had a look at the logs?

in learning.splittexi.log:
** node_next `coro y piano' for `Orquesta' not found
WARNING: Node 'Orquesta' was NOT found in the map
File name: orchestra-choir-and-piano.html

in notation.splittexi.log:
** Node following `Instrumentos MIDI' in menu `Lista de colores' and in
sectionning `El bloque MIDI' differ
** Node following `Tamaños de página predefinidos' in menu `Instrumentos
MIDI' and in sectionning `instrumentos MIDI' differ
** `instrumentos MIDI' doesn't appear in menus
** `Tablas del manual sobre notación' is up for `instrumentos MIDI', but
has no menu entry for this node
** No node following `instrumentos MIDI' in menu, but `Lista de colores'
follows in sectionning
WARNING: Unable to find node 'Construcción del marcado en Scheme' in
book extending.
WARNING: Unable to find node 'Construcción del marcado en Scheme' in
book extending.
WARNING: Unable to find node 'Platillas de cuarteto de cuerda' in book
learning.
WARNING: Unable to find node 'Lista bibliográfica' in book essay.
WARNING: Unable to find node 'Otras fuentes de inforamción' in book
learning.
WARNING: Unable to find node 'Sintaxis de las funciones musicales' in
book extending.
WARNING: Unable to find node 'Sintaxis de las funciones musicales' in
book extending.

in usage.splittexi.log:
WARNING: Unable to find node 'Primeros pasos' in book learning.
WARNING: Unable to find node 'LilyPond-book' in book usage.
WARNING: Unable to find node 'Configuración para MacOS X' in book usage.
WARNING: Unable to find node 'LilyPond-book' in book usage.



Sorry for you, I don't have them.

Cheers,
Jean-Charles



Reply | Threaded
Open this post in threaded view
|

Re: log files

Francisco Vila
2013/3/9 Jean-Charles Malahieude <[hidden email]>:
> Hi Francisco!
>
> Have you had a look at the logs?

No, I can not complete doc build due to an error in Documentation/cs
but I have successfully completed "make -C Docmentation/es doc" with a
clean exit. I will look and try again but I have a concert tomorrow
here http://goo.gl/maps/bVzkv and will have to wait until Monday at
best.

Thank you!
--
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com


Reply | Threaded
Open this post in threaded view
|

Re: log files

Francisco Vila
2013/3/9 Francisco Vila <[hidden email]>:

> 2013/3/9 Jean-Charles Malahieude <[hidden email]>:
>> Hi Francisco!
>>
>> Have you had a look at the logs?
>
> No, I can not complete doc build due to an error in Documentation/cs
> but I have successfully completed "make -C Docmentation/es doc" with a
> clean exit. I will look and try again but I have a concert tomorrow
> here http://goo.gl/maps/bVzkv and will have to wait until Monday at
> best.
>
> Thank you!

I have fixed the problems. As for the "WARNING: Unable to find
node..." I thought everyone else had them. I don't know what they mean
or what can I do to avoid them for the moment.
--
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com


Reply | Threaded
Open this post in threaded view
|

Re: log files

Jean-Charles MALAHIEUDE
Le 09/03/2013 21:51, Francisco Vila disait :

> 2013/3/9 Francisco Vila <[hidden email]>:
>> 2013/3/9 Jean-Charles Malahieude <[hidden email]>:
>>> Hi Francisco!
>>>
>>> Have you had a look at the logs?
>>
>> No, I can not complete doc build due to an error in Documentation/cs
>> but I have successfully completed "make -C Documentation/es doc" with a
>> clean exit. I will look and try again but I have a concert tomorrow
>> here http://goo.gl/maps/bVzkv and will have to wait until Monday at
>> best.
>>
>> Thank you!
>
> I have fixed the problems. As for the "WARNING: Unable to find
> node..." I thought everyone else had them. I don't know what they mean
> or what can I do to avoid them for the moment.
>

When I run: make -j3 doc LANGS='fr'
I check all logs (I now know I still should read the end of
*.texi2pdf.log as well) if there are WARNINGS about nodes not found in
books except snippets and internals.
It's most of the time due to misspelling, a renaming that has not been
updated in an @ref or @rbook, or having used what is after @node instead
of after @sectioning.


Wishing you tons of applauds this afternoon,
Jean-Charles