On Sat, Aug 23, 2008 at 02:47:45PM -0500, Murtuza wrote:
> The result is the same when done as a user.
>
> [EMAIL PROTECTED]:/opt/gnuradio/gr-howto-write-a-block$ sudo ./bootstrap
> Password:
> src/lib/Makefile.am:56: Python sources seen but `PYTHON' is undefined
> src/lib/Makefile.am:56: The us
The result is the same when done as a user.
[EMAIL PROTECTED]:/opt/gnuradio/gr-howto-write-a-block$ sudo ./bootstrap
Password:
src/lib/Makefile.am:56: Python sources seen but `PYTHON' is undefined
src/lib/Makefile.am:56: The usual way to define `PYTHON' is to add
`AM_PATH_PYTHON'
src/lib/Makefil
Murtuza wrote:
[EMAIL PROTECTED]:/opt/gnuradio/gr-howto-write-a-block# ./bootstrap
Usually it is not a good idea to do things like this while you are
logged in as root - the environment variables might not be suitable so
things will not work how you expected, and you could accidentally break
Hi Friends
I wrote the c++ and .i codes for a new block based on the gnuradio tutorial
and used the same bootstrap, configure.ac and Makefile.am files found in
gr-howto-write-a-block folder with minor changes in places where the source
file names are present. As I do not have a "qa_test" python fi
