Date: Thu, 14 Nov 2002 06:05:08 +0700 From: pirat <pirat@access.inet.co.th> To: Giorgos Keramidas <keramida@ceid.upatras.gr> Cc: freebsd-doc@freebsd.org Subject: Re: make at /usr/doc fail Message-ID: <20021113230508.GA3664@thai-aec.org> In-Reply-To: <20021113174722.GD15366@gothmog.gr> References: <20021106084711.GB749@thai-aec.org> <20021107115736.GE990@gray.sea.gr> <20021108021917.GA46833@thai-aec.org> <20021113174722.GD15366@gothmog.gr>
index | next in thread | previous in thread | raw e-mail
hi sirs, very much thanks for your great helps and hints. actually, i face serveral problems but i do not need to disturb the list. but the last one was so strange that i could not withstand to ask to the list. once again , thanks to you all who have helped me so much and particularly to Giorgos Keramidas. with best regards, pirat sriyotha On Wed, Nov 13, 2002 at 07:47:22PM +0200, Giorgos Keramidas wrote: > Date: Wed, 13 Nov 2002 19:47:22 +0200 > From: Giorgos Keramidas <keramida@ceid.upatras.gr> > To: pirat <pirat@access.inet.co.th> > Cc: freebsd-doc@freebsd.org > Subject: Re: make at /usr/doc fail > > On 2002-11-08 09:19, pirat <pirat@access.inet.co.th> wrote: > > On Thu, Nov 07, 2002 at 01:57:36PM +0200, Giorgos Keramidas wrote: > > > > *** Error code 4 > > > > Stop in /usr/doc/en_US.ISO8859-1/articles/releng. > > > > > > It works fine here. (just guessing here) Have you built ny of > > > your ports with optimizations? This could cause "strange" > > > problems afaik. Can you try removing and reinstalling your > > > textproc/docproj port and its dependencies? > > > > that happends with my two machines which install 4.7-stabel > > anew. for the first one, i simply copy those .eps from my old > > machine and remake again and there is no problem then . > > [...] > > i hate to give up, so i simply , while waiting for your answer, > > start make once again with some prediction in mind. error ? no, very > > strange really, it works fine for the second make ! > > If you re still having problems building the documentation, you'll > have to post a full log of the build to let people know what went > wrong. Start with a clean /usr/doc copy that you haven't modified at > all. If you are downloading the documentation through CVSup, the most > reliable way to do this is: > > # cd /usr > # rm -fr doc > # mkdir doc > # cvsup -h cvsup10.freebsd.org share/examples/cvsup/doc-supfile > > This is bound to take a while, but it's the only way to be sure that > you are running a build on a clean copy of /usr/doc if you haven't > kept a backup copy of the /usr/doc tree before. > > The next step should be easy to guess. You keep a backup copy of the > clean /usr/doc tree: > > # cd /usr > # tar cvf - doc | gzip -9c - > doc.tgz > > This way, if you ever need to return to a clean version of the docs, > you can simply: > > # cd /usr/doc > # rm -fr doc > # tar xzvf doc.tgz > > Then use script(1) and keep a log file of the entire build that is > failing. Post the log file either to the freebsd-doc list, or > personally to me. > > Giorgos. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the messagehelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021113230508.GA3664>