Does anyone else have to "./bootstrap" twice in a freshly checked-out
tree?
I'm wondering if it is just my setup, but I have to "./bootstrap;
./bootstrap" or else the Makefile.in doesn't appear.
[EMAIL PROTECTED]:~/src/gnuradio/tmp> cvs -d :ext:[EMAIL
PROTECTED]:/cvsroot/gnuradio co gnuradio-core
cvs checkout: Updating gnuradio-core
U gnuradio-core/.buildpri
U gnuradio-core/.cvsignore
U gnuradio-core/AUTHORS
[...]
[EMAIL PROTECTED]:~/src/gnuradio/tmp> cd gnuradio-core
[EMAIL PROTECTED]:~/src/gnuradio/tmp/gnuradio-core> ./bootstrap
[ delete m4 warnings ]
configure.ac: installing `./install-sh'
configure.ac: installing `./missing'
src/gen_interpolator_taps/Makefile.am: installing `./depcomp'
src/lib/swig/Makefile.am:50: installing `./py-compile'
configure.ac:24: required file `config.h.in' not found
[EMAIL PROTECTED]:~/src/gnuradio/tmp/gnuradio-core> ./configure
checking build system type... x86_64-unknown-linux-gnu
[...]
config.status: creating Makefile
config.status: error: cannot find input file: Makefile.in
[EMAIL PROTECTED]:~/src/gnuradio/tmp/gnuradio-core> ./bootstrap
[ delete m4 warnings ]
[EMAIL PROTECTED]:~/src/gnuradio/tmp/gnuradio-core> ./configure
checking build system type... x86_64-unknown-linux-gnu
[...]
config.status: creating Makefile
config.status: creating gnuradio-core.pc
[...]
config.status: executing swig_deps commands
[EMAIL PROTECTED]:~/src/gnuradio/tmp/gnuradio-core>
If I apply the following patch to "bootstrap", a single pass suffices.
*** gnuradio-core-old/bootstrap Mon Feb 28 15:29:38 2005
--- gnuradio-core/bootstrap Sat Apr 10 10:59:35 2004
***************
*** 29,37 ****
(
cd $dir
aclocal -I config
- autoconf
- autoheader
libtoolize --automake
automake --add-missing
)
done
--- 29,37 ----
(
cd $dir
aclocal -I config
libtoolize --automake
automake --add-missing
+ autoconf
+ autoheader
)
done
--
Joshua Lackey, PhD. -- [EMAIL PROTECTED]
_______________________________________________
Discuss-gnuradio mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
