On Tue, 2009-06-09 at 12:39 +0200, Øyvind Harboe wrote: > On Tue, Jun 9, 2009 at 12:24 PM, Zach Welch<[email protected]> wrote: > > On Tue, 2009-06-09 at 12:00 +0200, Øyvind Harboe wrote: > >> I use a different build & openocd src dir, this means "make > >> maintainer-clean" does not work... > >> > >> Is this old news? > >> > >> This is reproduceable under Linux as well as Cygwin. > >> > >> I tricked myself into believing that "make maintainer-clean" worked from > >> the build directory at some point and confused that with the eol native > >> line issues.... > > > > Whoops! I will commit a patch that fixes this shortly. > > Works fine now. Thanks! > > My remaining concern is that "bootstrap" does not do a "make > maintainer-clean"...
If you _always_ do a maintainer-clean _before_ merging changes that touch the build system, then the clean building process you want to work should work flawlessly (if there are no bugs). I would even say that doing otherwise is a "user error". Your mess. ;) > I'd want/expect the following sequence to *always* work: > > - svn update > - boostrap > - configure > - make Without a maintainer-clean first, this is impossible to guarantee. Specifically, there is no way for the build system to know the version or state of the old code version and how to clean it up. That said, it should work most of the time. With --enable-maintainer-mode, you should not even need to bother with the bootstrap and configure steps! A simple make is usually sufficient, and it will rebuild the required Makefiles or other files when the autotools sources are changed. If it doesn't, well, that's why I warn you to run maintainer-clean. :) The first place to start debugging will be "starting from a fresh checkout", which was what that preparatory command was meant to do. Cheers, Zach _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
