help-texinfo
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[help-texinfo] Texinfo 4.5: makeinfo works; texi2dvi says "Undefined cr


From: Alan Mackenzie
Subject: [help-texinfo] Texinfo 4.5: makeinfo works; texi2dvi says "Undefined cross reference"
Date: Wed, 9 Nov 2005 21:17:54 +0000 (GMT)

Hi, 

I'm using texi2dvi (GNU Texinfo 4.5) 1.14.

When I do

    > makeinfo cc-mode.texi

, I get cc-mode.info out the other end, with no sign of any error
messages.  When I try

    > TEXINPUTS=/usr/src/packages/BUILD/texinfo-4.5/doc:~/.TeX:/usr/doc/.TeX
    > texi2dvi cc-mode.texi

, I get the error messages (from cc-mode.log):

    508: Undefined cross reference `Config Basics-snt'.
    508: Undefined cross reference `Config Basics-snt'.
    508: Undefined cross reference `Config Basics-pg'. (cc-mode.tmp)  
    (cc-mode.tmp)
    (cc-mode.tmp) (cc-mode.tmp) (cc-mode.tmp) Chapter 4 [4] (cc-mode.tmp)
    (cc-mode.tmp) (cc-mode.tmp) (cc-mode.tmp) (cc-mode.tmp) (cc-mode.tmp)
    (cc-mode.tmp) [5] (cc-mode.tmp) (cc-mode.tmp)
    Underfull \hbox (badness 10000) in paragraph at lines 684--687
    address@hidden If @texttt c-indent-comments-syntactically-p[] @textrm is
    address@hidden
    t nil[] @textrm then @texttt c-

.  Lines 506-508 of cc-mode.texi look like this:

    As you get to know the mode better, you may want to make more
    ambitious changes to your configuration.  For this, you should start
    reading the chapter @ref{Config Basics}.

The lines defining the @node "Config Basics" look like this:

    @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
    @node    Config Basics, Custom Filling and Breaking, Font Locking, Top
    @comment  node-name,  next,  previous,  up
    @chapter Configuration Basics
    @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!



I get quite a few other error similar messages in this log, both for
@xrefs to "Config Basics" and to several other nodes.

I cannot see any pattern here, any way in which these particular @xref's
are different from other ones which work OK.

Would somebody give me a clue, please!

Thanks in advance!

-- 
Alan Mackenzie (Munich, Germany)






reply via email to

[Prev in Thread] Current Thread [Next in Thread]