I removed all the files, and rerun texi2pdf 2019308.texi Still, I get undefined. Still haven't figured out how this is happening.
when I use @setfilename and run texi2pdf a few times, everything is correct. --------------------- Christopher Dimech Chief Administrator - Naiad Informatics - GNU Project (Geocomputation) - Geophysical Simulation - Geological Subsurface Mapping - Disaster Preparedness and Mitigation - Natural Resource Exploration and Production - Free Software Advocacy > Sent: Monday, July 15, 2019 at 11:52 AM > From: "Gavin Smith" <[email protected]> > To: "Christopher Dimech" <[email protected]> > Cc: "help-texinfo gnu" <[email protected]> > Subject: Re: [help-texinfo] Cross-References display undefined when using > @include > > On Sat, Jul 13, 2019 at 12:38:09AM +0200, Christopher Dimech wrote: > > This is a basic test composed of two files "2019308.texi" (main with > > cross-references) and > > "bibl.texi" (bibliography with an anchor). > > > > Cross-References do work (when one clicks on the reference, it directs you > > to the cross-reference). > > However the pdf file shows > > <undefined> [bibl-Semenza-et-Ghirotti-2000], page <undefined> > > > > However when one uses @setfilename 2019308.info (comment the line out), one > > gets > > [bibl-Semenza-et-Ghirotti-2000], page 2 > > > > Have been under the impression that if there is no @setfilename line, > > makeinfo uses the > > input file name to determine the output name. Was aware that @setfilename > > used to be > > required by the Texinfo processors, but I've read it is no longer > > required.However, this > > test shows otherwise. > > @setfilename is not used at all when processing with TeX. The most > likely explanation is that the auxiliary files changed between runs of > TeX. If you had processed the file again *without* commenting out the > @setfilename line, then I expect the cross-reference would also have > been output correctly. > > I tested it both with "texi2pdf 2019308.texi" and "makeinfo --pdf > 2019308.texi" and both times TeX is run twice as it should be. > > If you run "pdfetex 2019308.texi" just once when 2019308.aux and > 2019308.toc don't exist, then the output is what you got. > > What exactly are you doing to process the files? >
