discuss-gnuradio
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: 3.10.7.0 upgrade advice request


From: Jeff Long
Subject: Re: 3.10.7.0 upgrade advice request
Date: Tue, 25 Jul 2023 18:34:19 -0400

Remove the build directory and try it again. I've seen this often when I just do a pull/cmake/make using an existing build dir.

On Tue, Jul 25, 2023 at 3:01 PM aardric <aardric@aardvarr.ca> wrote:
Hail,
I had some time to invest in an upgrade from gr 3.10.5.1 to 3.10.7.0 and
ran into a problem about 1/4 of the way through the build. I will be
digging into this although I'm not a developer and suspect that clearing
the local repository and starting clean may be a quicker road to success.
However, I should at least query as to whether I did something obviously
wrong (looking ahead to the next upgrade attempt). I don't expect anyone
to provide any debugging, just off the top advice, if any.
The steps were:

(1)
gnuradio> git pull
( ...output...)
Updating 3daaeb4ed..d79e0be3f

(2)
gnuradio/build> make uninstall
( ...output...)

(3)
gnuradio/build> cmake -DCMAKE_INSTALL_PREFIX=~/.local
-DCMAKE_BUILD_TYPE=Release -DPYTHON_EXECUTABLE=/usr/bin/python3
-DBoost_LIBRARY_DIRS=/usr/lib64 -DQWT_LIBRARIES=/usr/lib64/libqwt.so.6
-DQWT_INCLUDE_DIRS=/usr/include/qt5/qwt6 -DENABLE_GR_UHD=OFF
-DZEROMQ_LIBRARIES=/usr/local/lib64/libzmq.so
-DZEROMQ_INCLUDE_DIRS=/usr/local/include DENABLE_GR_SOAPY=ON ../
( ...output...)
-- Building for version: 3.10.7.0 / 3.10.7
-- Configuring done
-- Generating done
-- Build files have been written to: .... gnuradio/build

(4)
make -j4
( ...output...)
In file included from
gnuradio/build/gnuradio-runtime/python/gnuradio/gr/bindings/logger_pydoc.h:9,
                  from
gnuradio/gnuradio-runtime/python/gnuradio/gr/bindings/logger_python.cc:29:
gnuradio/gnuradio-runtime/python/gnuradio/gr/bindings/logger_python.cc:
In function ‘void bind_logger(pybind11::module&)’:
gnuradio/build/gnuradio-runtime/python/gnuradio/gr/bindings/pydoc_macros.h:11:28:
error: ‘__doc_gr_logger_log’ was not declared in this scope; did you
mean ‘__doc_gr_logger_logger’?

Here I stand.

Rick




reply via email to

[Prev in Thread] Current Thread [Next in Thread]