RE: [Discuss-gnuradio] No better

[Robert McGwier]

I for-all-dirs  buildit twice and almost everything worked
without my having to copy the incorrect Makefile.in.  The
"do bootstrap twice" part of the buildit run twice did the
trick.

I agree with time skew.  Mine is controlled to <50 ms by
GPS. ;-).  All is well now with one exception, when I
attempt to do things in the "how to do your own module"
I get an error message about the howto module not found
even though I can find howto.py and .pyc in the directory.
I attempted to modify load library path to no avail.

Bob


-----Original Message-----
From: Eric Blossom [mailto:address@hidden
Sent: Saturday, February 19, 2005 5:06 PM
To: Robert W. McGwier
Cc: address@hidden
Subject: Re: [Discuss-gnuradio] No better


On Fri, Feb 18, 2005 at 11:49:21PM -0500, Robert W. McGwier wrote:
> 
> Here is the  first warning in this
> 
> n4hy:/usr/local/GnuRadio/gr-build # ./for-all-dirs ../buildit 2>&1 | tee 
> make.log
> >>> /usr/local/GnuRadio/gr-build/gnuradio-core
> /usr/share/aclocal/cppunit.m4:4: warning: underquoted definition of 
> AM_PATH_CPPUNIT

Warning is OK.  Means the the cppunit packagers haven't updated to the
latest standard for config macros.

> and here is where it loses it:
> 
> checking boost/shared_ptr.hpp usability... yes
> checking boost/shared_ptr.hpp presence... yes
> checking for boost/shared_ptr.hpp... yes
> configure: creating ./config.status
> config.status: creating Makefile
> config.status: error: cannot find input file: Makefile.in
> >>> build FAILED in /usr/local/GnuRadio/gr-build/gnuradio-core
> 
> I am completely unfamiliar with cppunit but I installed it 3 days ago 
> for this purpose.
> 
> Idea?
> 
> Bob