Hi Ken ... On Mon, Feb 25, 2002 at 08:11:34PM +1100, Ken Foskey wrote: >> dmake: Error code 1, while making '../unxlngppc.pro/misc/zip_dflt_description.cxx' >This is because the rather brutal aproach I took, clean up everything >and restart. This is the definition of make clean in GNU standards. Yes .. you' re right >> >> ...If I run dmake before ./bootstrap, it will not have an effect. >Because you have deleted everything you do have to start from scratch >this includes bootstrap (I recommend running configure as well, I even >remove some files from config_office as well, like cache.) Ok .. I will try ... but I think, that will not solve the problem ... >> Sure .. I can delete the output directory of rsc and do a build again, >> but the buildscript stops, if an error occurs. >> >> Sometime, I'm asking myself, why many people do not run into this >> problem ... what are they doing? >If there is a problem with rsc that stops the build dead then the >problem must be resolved before you can continue. In theory this should >never happen in a standard release build (if you are bleeding edge then >good luck). Unfortunately we have some problems with variations in >build software and hardware causing some problems, ironing these out can >be a little hit and miss at first and require a purge of the directories >to get them to work exactly right. In this case if you had applied the >bison patch BEFORE you had started the build then there would have been >no problem (I hope...). When you patch after sometimes the patch >requires you to force builds on parts of the software, the fastest way I >know of is to purge the directories. With the buildsystem in debian to package source to debianpackages, wie apply the patches before running ./configure, all the time, so the patch will be applied before the whole build begins .... There, usually, nothing should be deleted ... for propper build, because, there is nothing to delete anyway ... >In fact I have some fairly heavy duty patches on OpenOffice and I >sometimes purge all output directories (dmake clean) in order to force >the whole build to run from start to finish and guarantee a clean >compile for others (even though tests can break!!!). I regularly do >this for debian woody QA on new releases before the general >anouncement. I do not do this for fun, it takes me a couple of days. >(When she who must be obeyed (Wife) lets me have some money I will buy a >new box) :) >Hoep this clears it up a bit. If I have missed the mark on the question >please ask again. I thinkk .. I have to grap into source, because, for me, it's not clear, why the 'undefined symbol yyparse__Fv' is coming and where does it come from ... Regards Jan -- One time, you all will be emulated by linux! ---- Jan- Hendrik Palic Url:"http://www.billgotchy.de"; E-Mail: "palic@billgotchy.de" -----BEGIN GEEK CODE BLOCK----- Version: 3.12 GCS d- s: a-- C++ UL++ P+++ L+++ E W++ N+ o+ K- w--- O- M- V- PS++ PE Y+ PGP++ t--- 5- X+++ R-- tv- b++ DI-- D+++ G+++ e+++ h+ r++ z+ ------END GEEK CODE BLOCK------
Attachment:
pgp8c8MUDLadI.pgp
Description: PGP signature