Re: [Flightgear-devel] fgfs compile error, today's cvs
After consulting our local autotools Guru and the web our conclusion is that the cost effective way is to remove the dependency file, rerun configure and then make. In this case this means rm test/.deps/est-epsilon.Po ./configure make This will work for est-epsilon since the .Po is regenerated. However there were more filenames changed so rm -rf tests/.deps/ ./configure make is required and new dependency files are regenerated for files in tests. The above will minimize compile time. 'make distclean' or a new checkout of the source will trigger a complete recompilation of the source. Cheers, Jari Jari Häkkinen wrote: > John Denker wrote: >> Curtis Olson wrote: I'm not sure the best way to handle this but if you start at the top and run ./autogen.sh followed by ./configure --options I think the error will be cleaned up. Switching files from abc.c to abc.cxx confuses the dependency tracking of automake. >> It may be even worse than that. I had to >> rm tests/.deps/* >> before doing >> ./autogen.sh >> configure --whatever >> >> >> On 12/10/2009 02:04 AM, Erik Hofman wrote: >>> Indeed.that's a pity. >> Yes. > > And I think it is possible to avoid the problem with autotools. I'll > have a look. > > >> = >> >> Suggestion: Perhaps "make clean" should clear out all >> the .deps directories. > > No, it should not. Try 'make distclean' before updating configure.ac or > Makefile.am files. This will remove most of the generated files based on > the current autotools setup. Then update, autogen, configure, make. > Performing 'make distclean' after update will usually leave stray > obsolete files. > > > >> It would also be nice if the automake system handled >> 64-bit libraries properly. >> http://www.av8n.com/fly/fgfs/htm/bug-list.htm#bug-64bit > > I really like your bug tracker. > > > Jari > > > -- > Return on Information: > Google Enterprise Search pays you back > Get the facts. > http://p.sf.net/sfu/google-dev2dev > ___ > Flightgear-devel mailing list > Flightgear-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] fgfs compile error, today's cvs
John Denker wrote: > Curtis Olson wrote: >>> I'm not sure the best way to handle this but if you start at the top and >>> run ./autogen.sh followed by ./configure --options I think the error >>> will be cleaned up. Switching files from abc.c to abc.cxx confuses the >>> dependency tracking of automake. > > It may be even worse than that. I had to > rm tests/.deps/* > before doing > ./autogen.sh > configure --whatever > > > On 12/10/2009 02:04 AM, Erik Hofman wrote: >> Indeed.that's a pity. > > Yes. And I think it is possible to avoid the problem with autotools. I'll have a look. > = > > Suggestion: Perhaps "make clean" should clear out all > the .deps directories. No, it should not. Try 'make distclean' before updating configure.ac or Makefile.am files. This will remove most of the generated files based on the current autotools setup. Then update, autogen, configure, make. Performing 'make distclean' after update will usually leave stray obsolete files. > It would also be nice if the automake system handled > 64-bit libraries properly. > http://www.av8n.com/fly/fgfs/htm/bug-list.htm#bug-64bit I really like your bug tracker. Jari -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] fgfs compile error, today's cvs
A simple make clean && make was enough to get the ball rolling for me. -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] fgfs compile error, today's cvs
On Thu, Dec 10, 2009 at 1:01 PM, John Denker wrote: > Curtis Olson wrote: > >> I'm not sure the best way to handle this but if you start at the top and > >> run ./autogen.sh followed by ./configure --options I think the error > >> will be cleaned up. Switching files from abc.c to abc.cxx confuses the > >> dependency tracking of automake. > > It may be even worse than that. I had to > rm tests/.deps/* > before doing > ./autogen.sh > configure --whatever > > make distclean, followed by running autogen.sh and configure, seems to gett the job done. Tim > > On 12/10/2009 02:04 AM, Erik Hofman wrote: > > Indeed.that's a pity. > > Yes. > > = > > Suggestion: Perhaps "make clean" should clear out all > the .deps directories. > > > > It would also be nice if the automake system handled > 64-bit libraries properly. > http://www.av8n.com/fly/fgfs/htm/bug-list.htm#bug-64bit > > > > -- > Return on Information: > Google Enterprise Search pays you back > Get the facts. > http://p.sf.net/sfu/google-dev2dev > ___ > Flightgear-devel mailing list > Flightgear-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/flightgear-devel > -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] fgfs compile error, today's cvs
Curtis Olson wrote: >> I'm not sure the best way to handle this but if you start at the top and >> run ./autogen.sh followed by ./configure --options I think the error >> will be cleaned up. Switching files from abc.c to abc.cxx confuses the >> dependency tracking of automake. It may be even worse than that. I had to rm tests/.deps/* before doing ./autogen.sh configure --whatever On 12/10/2009 02:04 AM, Erik Hofman wrote: > Indeed.that's a pity. Yes. = Suggestion: Perhaps "make clean" should clear out all the .deps directories. It would also be nice if the automake system handled 64-bit libraries properly. http://www.av8n.com/fly/fgfs/htm/bug-list.htm#bug-64bit -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] fgfs compile error, today's cvs
Curtis Olson wrote: > I'm not sure the best way to handle this but if you start at the top and > run ./autogen.sh followed by ./configure --options I think the error > will be cleaned up. Switching files from abc.c to abc.cxx confuses the > dependency tracking of automake. Indeed.that's a pity. Erik -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] fgfs compile error, today's cvs
I had the same and fixed it by re-checking out source from CVS. Just executing autogen.sh didn't help. I have not tried "make distclean" or so. :-) On Wed, 2009-12-09 at 22:32 -0600, Curtis Olson wrote: > I'm not sure the best way to handle this but if you start at the top > and run ./autogen.sh followed by ./configure --options I think the > error will be cleaned up. Switching files from abc.c to abc.cxx > confuses the dependency tracking of automake. Roland signature.asc Description: This is a digitally signed message part -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] fgfs compile error, today's cvs
I'm not sure the best way to handle this but if you start at the top and run ./autogen.sh followed by ./configure --options I think the error will be cleaned up. Switching files from abc.c to abc.cxx confuses the dependency tracking of automake. Curt. On Wed, Dec 9, 2009 at 7:33 PM, dave perry wrote: > I am getting the following error compiling fgfs from cvs today on two > different systems. > > $ make > Making all in tests > make[1]: Entering directory `/home/dad/source-osg/source-fgfs/tests' > make[1]: *** No rule to make target `est-epsilon.c', needed by > `est-epsilon.o'. Stop. > make[1]: Leaving directory `/home/dad/source-osg/source-fgfs/tests' > make: *** [all-recursive] Error 1 > $ > > > -- > Return on Information: > Google Enterprise Search pays you back > Get the facts. > http://p.sf.net/sfu/google-dev2dev > ___ > Flightgear-devel mailing list > Flightgear-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/flightgear-devel > -- Curtis Olson: http://baron.flightgear.org/~curt/ -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] fgfs compile error, today's cvs
I am getting the following error compiling fgfs from cvs today on two different systems. $ make Making all in tests make[1]: Entering directory `/home/dad/source-osg/source-fgfs/tests' make[1]: *** No rule to make target `est-epsilon.c', needed by `est-epsilon.o'. Stop. make[1]: Leaving directory `/home/dad/source-osg/source-fgfs/tests' make: *** [all-recursive] Error 1 $ -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
