That's normal operation. The actual file is
libgnuradio.grhpsdr.so.e487bf33 and libgnuradio.grhpsdr.so.1.0.0git and
libgnuradio.grhpsdr.so are symbolic links.
The e487bf33 is the git hash of your last commit.
Ron
On 6/14/21 10:23 AM, Tom McDermott wrote:
I have successfully built my OOT in gnuradio 3.9. This was done with
a plain vanilla gr_modtool
constructed build, and built using cmake, make, make install, etc.
One of the folks who uses my module and packages it for one of the
linux distributions noticed that
it is generating some strange output files, and I can confirm on my
own system.
The .so filenames are installed in /usr/lib (for that specific
person) or /usr/x86-64-linux-gnu/ (for my system)
The correct .so is being generated and used without any issues:
libgnuradio.grhpsdr.so <http://libgnuradio.grhpsdr.so>
But it is also generating:
libgnuradio.grhpsdr.so.1.0.0git
libgnuradio.grhpsdr.so.e487bf33
I noticed that other modules have a series of versioned soft links.
For example:
libgnuradio.analog.so <http://libgnuradio.analog.so> ->
libgnuradio.analog.so.3.9.1
libgnuradio.analog.so.3.9.1 -> libgnuradio.analog.so.3.9.1.0
libgnuradio.analog.so.3.9.1.0
Is the way my OOT's .so files (and no soft links) being generated a
problem?
Will this fail on a subsequent update to my OOT?
Is there some sort of extra configuration I need to do to the
auto-generated make or cmake files ?
-- Tom, N5EG
