Sender: rich AT phekda DOT freeserve DOT co DOT uk Message-ID: <3E18133A.EE2ECC59@phekda.freeserve.co.uk> Date: Sun, 05 Jan 2003 11:12:58 +0000 From: Richard Dawe X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.23 i586) X-Accept-Language: de,fr MIME-Version: 1.0 To: djgpp-workers AT delorie DOT com Subject: Re: GDB 5.3 build query/problem & solution References: <200212291526 DOT gBTFQJU25879 AT delorie DOT com> <004c01c2b452$54044880$0100a8c0 AT acp42g> <3791-Sun05Jan2003063253+0200-eliz AT is DOT elta DOT co DOT il> <3E17CB17 DOT DA533BC8 AT yahoo DOT com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Reply-To: djgpp-workers AT delorie DOT com Hello. CBFalconer wrote: > Point of order - why don't the documentation zips contain the > original info source so that the user can create the format(s) of > interest? AFAICT the only way to get this is to download the > massive complete source. To me the formats of interest are the > info files and the one piece html, which is easily printed if > desired. In the packages I build I include the original texinfo sources. I seem to have had some trouble recently getting texi2dvi's include option to work, so you may have to copy some files around, to get the gdb texinfo sources to build. E.g. in gdb/doc: texi2dvi -I ../mi -I../../../readline/doc (This is off the top of my head, so the paths may be wrong.) texi2dvi would ask me for the paths to files which it should have found in the include paths. So I typed in the relative paths for the files and still it could not find them. Has anyone else seen this problem? In the end I just copied all the files from ../mi and ../../../readline/doc into gdb/doc and removed them after I had built the .dvi file. Bye, Rich =] -- Richard Dawe [ http://www.phekda.freeserve.co.uk/richdawe/ ]