Re: [Discuss-gnuradio] RDS decoding

[jean-michel . friedt]

I have just completed the translation to English of my description of
RDS decoding. It is now available at 

http://jmfriedt.free.fr/lm_rds_eng.pdf

Corrections welcome, both on the content (not familiar enough with error
correcting codes and bitrate synchronization to be sure I did't make
mistakes in describing my experiments) and the spelling.

JM

> As briefly mentioned at FOSDEM, I have been investigating RDS since
> last christmas, trying to tackle each issue step by step from LO
> synchronization for BPSK demodulation, bit decoding, sentence
> synchronization, station name and free text extraction, error
> correcting code implementation and finally transferred time analysis.
> My objective was of course not to compete with gr_rds, used as a
> reference, but to acquire a detailed understanding of each step.
> Since I protoype with GNU/Octave, I wanted to convert most digital
> signal processing from LFSR to linear algebra (matrix). I think I
> pretty much understand now the whole process, despite designing the
> error correcting code being still beyond my capability. An internal
> lab presentation on the topic is now available at
> http://jmfriedt.free.fr/slides_rds.pdf and for the French speaking
> audience, accompanying article (in French at the moment, will be
> translated ASAP to English, as soon as I have completed RDS v.s GPS
> time comparisons) at http://jmfriedt.free.fr/lm_rds.pdf
> 
> I am well aware of Tom Rondeau's sponsoring Polyphase clock recovery,
> but at the moment I could only figure out how to use MM-Clock
> recovery and MPSK, which worked quite well for my purpose.
> 
> Any feedback welcome,
> JM
> 



-- 
JM Friedt, FEMTO-ST Time & Frequency/SENSeOR, 26 rue de l'Epitaphe,
25000 Besancon, France

___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

[Discuss-gnuradio] OS X Fuzzy Text in GRC

[Dave NotTelling]

I just installed GNU Radio via macports and the text in the blocks is
really fuzzy.  I ran across https://trac.macports.org/ticket/36410 but I
don't quite understand how to make it work for my issue.  Is there
something in /Applications/MacPorts/Qt4 that I should be changing?

I'm running OS X 10.11.6

Thanks!
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] OS X Fuzzy Text in GRC

[Michael Dickens]

Can you send me (off list) a screen snapshot or the like so that I can
see what you mean by "fuzzy"? I see nothing out of the ordinary in GRC
when running, but then maybe I'm not looking at the correct text...
Cheers! - MLD


On Sun, Apr 2, 2017, at 10:12 AM, Dave NotTelling wrote:

> I just installed GNU Radio via macports and the text in the blocks is
> really fuzzy.  I ran across https://trac.macports.org/ticket/36410 but
> I don't quite understand how to make it work for my issue.  Is there
> something in /Applications/MacPorts/Qt4 that I should be changing? I'm
> running OS X 10.11.6.
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] GNURadio Error On Mac

[Michael Dickens]

Hi Vamsi - It looks like you're doing everything correctly for building
& installing your OOT & GR itself.


If I had to guess, I'd think that, somehow, the 2 argument to "map" is
being provided either directly or indirectly in the "top_block.py"
script & clearly doesn't support iteration & needs to be able to do so.
Since I don't have the code it's kinda hard to say anything more about
what's going on.


I'm not sure how to test the gateway block, whatever it provides.
If you can send me example code off-list I'll give it & try & see
what I can do.


Cheers! - MLD



> I’m facing the following error when I run an OOT module:

> 

> Executing: /opt/local/Library/Frameworks/Python.framework/Versions/2.-
> 7/Resources/Python.app/Contents/MacOS/Python -u
> /Users/vamsi/Documents/GNURadio/CompanionWorkspace/top_block.py
> 

> Traceback (most recent call last):

>   File
>   "/Users/vamsi/Documents/GNURadio/CompanionWorkspace/top_block.py",
>   line 204, in 
> main()

>   File
>   "/Users/vamsi/Documents/GNURadio/CompanionWorkspace/top_block.py",
>   line 192, in main
> tb = top_block_cls()

>   File
>   "/Users/vamsi/Documents/GNURadio/CompanionWorkspace/top_block.py",
>   line 160, in __init__
> self.iris_ml_svm_0 = iris.ml_svm('')

>   File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/l-
>   ib/python2.7/site-packages/iris/ml_svm.py", line 33, in __init__
> out_sig=numpy.complex64)

>   File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/l-
>   ib/python2.7/site-packages/gnuradio/gr/gateway.py", line 221, in
>   __init__
> factor=1, #not relevant factor

>   File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/l-
>   ib/python2.7/site-packages/gnuradio/gr/gateway.py", line 91, in
>   __init__
> self.__in_sig = sig_to_dtype_sig(in_sig)

>   File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/l-
>   ib/python2.7/site-packages/gnuradio/gr/gateway.py", line 90, in
>   sig_to_dtype_sig
> return map(numpy.dtype, sig)

> TypeError: argument 2 to map() must support iteration

> 

> I don’t have any issue running regular blocks, but not just the
> OOT ones.
> 

> I have installed GNURadio using Macports:

> sudo port install gnuradio -universal

> 

> I use the following steps to compile the block:

> mkdir build

> cd build

> cmake -DCMAKE_INSTALL_PREFIX=/opt/local -
> DPYTHON_EXECUTABLE=/opt/local/bin/python2.7 -
> DPYTHON_INCLUDE_DIR=/opt/local/Library/Frameworks/Python.framework/Ve-
> rsions/2.7/Headers -
> DPYTHON_LIBRARY=/opt/local/Library/Frameworks/Python.framework/Versio-
> ns/2.7/Python -
> DGR_PYTHON_DIR=/opt/local/Library/Frameworks/Python.framework/Version-
> s/2.7/lib/python2.7/site-packages ../
> sudo make install

> 


___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] GNURadio Error On Mac

[Michael Dickens]

Hi Vamsi - Glad to hear you worked out the issue. Cheers! - MLD

On Sun, Apr 2, 2017 at 4:21 PM, Vamsi Krishna Adsumilli 
wrote:

> Thanks for the reply.
> We were able to narrow down the issue. After generating a OOT module using
> gr_modtool, i have incorrectly edited the following lines, which caused the
> issue.
>
> in_sig=numpy.complex64,
> out_sig=numpy.complex64)
>
> Where it should have been
>
> in_sig=[numpy.complex64],
> out_sig=[numpy.complex64])
>
> I faced new issues each time I restart using GNURadio on MAC, so I
> initially jumped to that conclusion, I’m sorry about the confusion.
>
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] log4cpp library not found

[Cinaed Simson]

On 04/01/2017 03:40 PM, li...@lazygranch.com wrote:
> 
> find / -name "FindLog4cpp.cmake"
> /usr/local/src/gnuradio/cmake/Modules/FindLog4cpp.cmake
> /usr/local/lib/cmake/gnuradio/FindLog4cpp.cmake
> 
> That file is found twice. Is that the problem? If not, which do I
> replace? Or perhaps both. Or does one file cause the other file to be
> updated?

No, one file is the source file and the other file is the installed in
your gnuradio installation directory.

Try

   diff /usr/local/src/gnuradio/cmake/Modules/FindLog4cpp.cmake
/usr/local/lib/cmake/gnuradio/FindLog4cpp.cmake

That is, diff on the two files and make sure they're the same.

If they're different, I'm not sure which one it would be reading - my
guess would be the one
/usr/local/src/gnuradio/cmake/Modules/FindLog4cpp.cmake.

In any case, I'm not sure where you stand with this problem.

Did you receive a file from Marcus?

-- Cinaed


> 
> 
> On Sat, 1 Apr 2017 19:03:52 +0200
> Marcus Müller  wrote:
> 
>> That's very interesting, considering that I believe the CMake script
>> that looks for log4cpp uses the same pkg-command to look for it...
>>
>> Ok. So there's something strange going on with that
>> cmake/Modules/FindLog4cpp.cmake, probably.
>>
>> Can you replace that Find...cmake with the one I've attached and give
>> it a try?
>>
>> Cheers,
>>
>> Marcus
>>
>>
>> On 01.04.2017 18:27, li...@lazygranch.com wrote:
>>> Hyphen instead of underscore.
>>>
>>> pkg-config --libs log4cpp
>>> -L/usr/local/lib64 -llog4cpp 
>>>
>>> So pkg-config finds the library. Note I got the same problem
>>> regarding not finding log4cpp when I used the opensuse package
>>> manager version instead of making my own in /usr/src.
>>>
>>>
>>>
>>>
>>> On Sat, 1 Apr 2017 11:19:14 +0200
>>> Marcus Müller  wrote:
>>>
 Hi,

 if you've built it yourself, chances are that automatic tools like
 CMake's find_package or the general pkg_config can't find it,
 because you didn't put the right files in the distro-typical
 places.

 Try running

 pkg_config --libs log4cpp

 If that fails: Please make sure the installation put the
 packageconfig files in a place that packageconfig looks into.

 Best regards,
 Marcus

 On 04/01/2017 11:13 AM, li...@lazygranch.com wrote:
> I built it myself in usr local. 
>
> The source exists at github and sourceforge. Apparently SF is the
> original. I built both versions and neither is found by gnuradio
> in the build process.
>
> The contents /usr/local/include/log4cpp is at this pastebin.
> https://pastebin.com/fw6NUR6x
> This is the after the SF build.
>
>
>
> On Fri, 31 Mar 2017 22:07:59 -0400
> "Marcus D. Leech"  wrote:
>  
>> On 03/31/2017 09:13 PM, li...@lazygranch.com wrote:  
>>> opensuse 42.2
>>>
>>> This is the only "missing" thing I can find in the cmake ..:
>>>
>>>
>>>
>>> -- Configuring volk support...
>>> --   Enabling volk support.
>>> --   Override with -DENABLE_VOLK=ON/OFF
>>> --   Override with -DENABLE_INTERNAL_VOLK=ON/OFF
>>> -- ENABLE_GR_LOG set to ON.
>>> -- HAVE_LOG4CPP set to False.
>>> -- LOG4CPP_LIBRARIES set to .
>>>
>>> Though the library is there. Perhaps it has a different name in
>>> other distributions? I can make symbolic links if need be.
>>>
>>> /usr/lib64 # ls
>>> liblog4cpp* liblog4cpp.so  liblog4cpp.so.5  liblog4cpp.so.5.0.6
>>>
>>>
>>>
>> It may be the case that you don't have the matching #include
>> files, which is what code being compiled needs in addition to the
>> libraries.
>>
>>
>>
>> ___
>> Discuss-gnuradio mailing list
>> Discuss-gnuradio@gnu.org
>> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio  
> ___
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio  

 ___
 Discuss-gnuradio mailing list
 Discuss-gnuradio@gnu.org
 https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>>>
>>> ___
>>> Discuss-gnuradio mailing list
>>> Discuss-gnuradio@gnu.org
>>> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>>
> 
> 
> ___
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
> 


___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

[Discuss-gnuradio] gr-trellis test_cpm.py question

[Andy Walls]

Hi Achilleas:

In the test_cpm.py example under gr-trellis, there is a comment:

"# only works for N=2, do it manually for N>2..."
https://github.com/gnuradio/gnuradio/blob/master/gr-trellis/examples/python/test_cpm.py#L108

Could you, or anyone else, elaborate on what need to be done manually for N>2?

Thanks,
Andy

___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] log4cpp library not found

[li...@lazygranch.com]

Regarding the Marcus cmake, I guessed that src would copy to lib, but
that didn't happen. (Easy to check by file dates.) I ended up copying
the new FindLog4cpp.cmake to both locations myself. I did a diff with
the -s option and they are the same. 

diff -s /usr/local/src/gnuradio/cmake/Modules/FindLog4cpp.cmake 
/usr/local/lib/cmake/gnuradio/FindLog4cpp.cmake
Files /usr/local/src/gnuradio/cmake/Modules/FindLog4cpp.cmake and 
/usr/local/lib/cmake/gnuradio/FindLog4cpp.cmake are identical


The problem is still there. I downloaded the log4cpp from the opensuse
repo, which of course would use the "normal" library (/usr/lib64)
rather than the local library, but that didn't work either.

So in summary, the problem is still there. 


On Sun, 2 Apr 2017 14:16:07 -0700
Cinaed Simson  wrote:

> On 04/01/2017 03:40 PM, li...@lazygranch.com wrote:
> > 
> > find / -name "FindLog4cpp.cmake"
> > /usr/local/src/gnuradio/cmake/Modules/FindLog4cpp.cmake
> > /usr/local/lib/cmake/gnuradio/FindLog4cpp.cmake
> > 
> > That file is found twice. Is that the problem? If not, which do I
> > replace? Or perhaps both. Or does one file cause the other file to
> > be updated?
> 
> No, one file is the source file and the other file is the installed in
> your gnuradio installation directory.
> 
> Try
> 
>diff /usr/local/src/gnuradio/cmake/Modules/FindLog4cpp.cmake
> /usr/local/lib/cmake/gnuradio/FindLog4cpp.cmake
> 
> That is, diff on the two files and make sure they're the same.
> 
> If they're different, I'm not sure which one it would be reading - my
> guess would be the one
> /usr/local/src/gnuradio/cmake/Modules/FindLog4cpp.cmake.
> 
> In any case, I'm not sure where you stand with this problem.
> 
> Did you receive a file from Marcus?
> 
> -- Cinaed
> 
> 
> > 
> > 
> > On Sat, 1 Apr 2017 19:03:52 +0200
> > Marcus Müller  wrote:
> > 
> >> That's very interesting, considering that I believe the CMake
> >> script that looks for log4cpp uses the same pkg-command to look
> >> for it...
> >>
> >> Ok. So there's something strange going on with that
> >> cmake/Modules/FindLog4cpp.cmake, probably.
> >>
> >> Can you replace that Find...cmake with the one I've attached and
> >> give it a try?
> >>
> >> Cheers,
> >>
> >> Marcus
> >>
> >>
> >> On 01.04.2017 18:27, li...@lazygranch.com wrote:
> >>> Hyphen instead of underscore.
> >>>
> >>> pkg-config --libs log4cpp
> >>> -L/usr/local/lib64 -llog4cpp 
> >>>
> >>> So pkg-config finds the library. Note I got the same problem
> >>> regarding not finding log4cpp when I used the opensuse package
> >>> manager version instead of making my own in /usr/src.
> >>>
> >>>
> >>>
> >>>
> >>> On Sat, 1 Apr 2017 11:19:14 +0200
> >>> Marcus Müller  wrote:
> >>>
>  Hi,
> 
>  if you've built it yourself, chances are that automatic tools
>  like CMake's find_package or the general pkg_config can't find
>  it, because you didn't put the right files in the distro-typical
>  places.
> 
>  Try running
> 
>  pkg_config --libs log4cpp
> 
>  If that fails: Please make sure the installation put the
>  packageconfig files in a place that packageconfig looks into.
> 
>  Best regards,
>  Marcus
> 
>  On 04/01/2017 11:13 AM, li...@lazygranch.com wrote:
> > I built it myself in usr local. 
> >
> > The source exists at github and sourceforge. Apparently SF is
> > the original. I built both versions and neither is found by
> > gnuradio in the build process.
> >
> > The contents /usr/local/include/log4cpp is at this pastebin.
> > https://pastebin.com/fw6NUR6x
> > This is the after the SF build.
> >
> >
> >
> > On Fri, 31 Mar 2017 22:07:59 -0400
> > "Marcus D. Leech"  wrote:
> >  
> >> On 03/31/2017 09:13 PM, li...@lazygranch.com wrote:  
> >>> opensuse 42.2
> >>>
> >>> This is the only "missing" thing I can find in the cmake ..:
> >>>
> >>>
> >>>
> >>> -- Configuring volk support...
> >>> --   Enabling volk support.
> >>> --   Override with -DENABLE_VOLK=ON/OFF
> >>> --   Override with -DENABLE_INTERNAL_VOLK=ON/OFF
> >>> -- ENABLE_GR_LOG set to ON.
> >>> -- HAVE_LOG4CPP set to False.
> >>> -- LOG4CPP_LIBRARIES set to .
> >>>
> >>> Though the library is there. Perhaps it has a different name
> >>> in other distributions? I can make symbolic links if need be.
> >>>
> >>> /usr/lib64 # ls
> >>> liblog4cpp* liblog4cpp.so  liblog4cpp.so.5
> >>> liblog4cpp.so.5.0.6
> >>>
> >>>
> >>>
> >> It may be the case that you don't have the matching #include
> >> files, which is what code being compiled needs in addition to
> >> the libraries.
> >>
> >>
> >>
> >> ___
> >> Discuss-gnuradio mailing list
> >> Discuss-gnuradio@gnu.org
> >> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio  
> > ___

Re: [Discuss-gnuradio] log4cpp library not found

[Cinaed Simson]

On 04/02/2017 04:17 PM, li...@lazygranch.com wrote:
> Regarding the Marcus cmake, I guessed that src would copy to lib, but
> that didn't happen. (Easy to check by file dates.) I ended up copying
> the new FindLog4cpp.cmake to both locations myself. I did a diff with
> the -s option and they are the same. 
> 
> diff -s /usr/local/src/gnuradio/cmake/Modules/FindLog4cpp.cmake 
> /usr/local/lib/cmake/gnuradio/FindLog4cpp.cmake
> Files /usr/local/src/gnuradio/cmake/Modules/FindLog4cpp.cmake and 
> /usr/local/lib/cmake/gnuradio/FindLog4cpp.cmake are identical
> 
> 
> The problem is still there. I downloaded the log4cpp from the opensuse
> repo, which of course would use the "normal" library (/usr/lib64)
> rather than the local library, but that didn't work either.
> 
> So in summary, the problem is still there. 

Correct me if I'm wrong, but it appears the system installed version of
liblog4cpp is in /usr/lib64 and the source version you built is in
/usr/local/lib64.

Please post the output of

   yum search log4cpp

and

  ldconfig -v | grep liblog4cpp

-- Cinaed
> 
> 
> On Sun, 2 Apr 2017 14:16:07 -0700
> Cinaed Simson  wrote:
> 
>> On 04/01/2017 03:40 PM, li...@lazygranch.com wrote:
>>>
>>> find / -name "FindLog4cpp.cmake"
>>> /usr/local/src/gnuradio/cmake/Modules/FindLog4cpp.cmake
>>> /usr/local/lib/cmake/gnuradio/FindLog4cpp.cmake
>>>
>>> That file is found twice. Is that the problem? If not, which do I
>>> replace? Or perhaps both. Or does one file cause the other file to
>>> be updated?
>>
>> No, one file is the source file and the other file is the installed in
>> your gnuradio installation directory.
>>
>> Try
>>
>>diff /usr/local/src/gnuradio/cmake/Modules/FindLog4cpp.cmake
>> /usr/local/lib/cmake/gnuradio/FindLog4cpp.cmake
>>
>> That is, diff on the two files and make sure they're the same.
>>
>> If they're different, I'm not sure which one it would be reading - my
>> guess would be the one
>> /usr/local/src/gnuradio/cmake/Modules/FindLog4cpp.cmake.
>>
>> In any case, I'm not sure where you stand with this problem.
>>
>> Did you receive a file from Marcus?
>>
>> -- Cinaed
>>
>>
>>>
>>>
>>> On Sat, 1 Apr 2017 19:03:52 +0200
>>> Marcus Müller  wrote:
>>>
 That's very interesting, considering that I believe the CMake
 script that looks for log4cpp uses the same pkg-command to look
 for it...

 Ok. So there's something strange going on with that
 cmake/Modules/FindLog4cpp.cmake, probably.

 Can you replace that Find...cmake with the one I've attached and
 give it a try?

 Cheers,

 Marcus


 On 01.04.2017 18:27, li...@lazygranch.com wrote:
> Hyphen instead of underscore.
>
> pkg-config --libs log4cpp
> -L/usr/local/lib64 -llog4cpp 
>
> So pkg-config finds the library. Note I got the same problem
> regarding not finding log4cpp when I used the opensuse package
> manager version instead of making my own in /usr/src.
>
>
>
>
> On Sat, 1 Apr 2017 11:19:14 +0200
> Marcus Müller  wrote:
>
>> Hi,
>>
>> if you've built it yourself, chances are that automatic tools
>> like CMake's find_package or the general pkg_config can't find
>> it, because you didn't put the right files in the distro-typical
>> places.
>>
>> Try running
>>
>> pkg_config --libs log4cpp
>>
>> If that fails: Please make sure the installation put the
>> packageconfig files in a place that packageconfig looks into.
>>
>> Best regards,
>> Marcus
>>
>> On 04/01/2017 11:13 AM, li...@lazygranch.com wrote:
>>> I built it myself in usr local. 
>>>
>>> The source exists at github and sourceforge. Apparently SF is
>>> the original. I built both versions and neither is found by
>>> gnuradio in the build process.
>>>
>>> The contents /usr/local/include/log4cpp is at this pastebin.
>>> https://pastebin.com/fw6NUR6x
>>> This is the after the SF build.
>>>
>>>
>>>
>>> On Fri, 31 Mar 2017 22:07:59 -0400
>>> "Marcus D. Leech"  wrote:
>>>  
 On 03/31/2017 09:13 PM, li...@lazygranch.com wrote:  
> opensuse 42.2
>
> This is the only "missing" thing I can find in the cmake ..:
>
>
>
> -- Configuring volk support...
> --   Enabling volk support.
> --   Override with -DENABLE_VOLK=ON/OFF
> --   Override with -DENABLE_INTERNAL_VOLK=ON/OFF
> -- ENABLE_GR_LOG set to ON.
> -- HAVE_LOG4CPP set to False.
> -- LOG4CPP_LIBRARIES set to .
>
> Though the library is there. Perhaps it has a different name
> in other distributions? I can make symbolic links if need be.
>
> /usr/lib64 # ls
> liblog4cpp* liblog4cpp.so  liblog4cpp.so.5
> liblog4cpp.so.5.0.6
>
>
>
 It may be the case that you don't have the matching #include
>>>

[Discuss-gnuradio] File sink Recording Issue

[Jahnavendra Mattipa]

Hello all,
​
 1st.py

​​
 array

​​
 fm_record.txt

​​
 lpf.grc

​​
 sam.dat

​​
 sam.doc

​ I am jahnavendra. I am facing some difficulty while recording the data in
the gnuradio 'grc' file. I recorded data using fil sink but it is looking
like some special characters are showing while opening the recorded file.
Can anyone please tell me how to identify the recorded data and which which
format best suites to open the file. While recording the data using signal
generator it is creating in the order of GB range files and i attached some
recorded files, using these you may get an idea about my problem.
  Thank you in advance.
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] log4cpp library not found

[li...@lazygranch.com]

sudo yum search all log4cpp
== Matched: log4cpp 
==
log4cpp-devel.x86_64 : Development tools for Log for C++
liblog4cpp5.x86_64 : Logging for C++

ldconfig -v | grep liblog4cpp
ldconfig: Can't stat /usr/lib64/graphviz/sharp: No such file or directory
ldconfig: Can't stat /usr/lib64/graphviz/java: No such file or directory
ldconfig: Can't stat /usr/lib64/graphviz/perl: No such file or directory
ldconfig: Can't stat /usr/lib64/graphviz/php: No such file or directory
ldconfig: Can't stat /usr/lib64/graphviz/ocaml: No such file or directory
ldconfig: Can't stat /usr/lib64/graphviz/python: No such file or directory
ldconfig: Can't stat /usr/lib64/graphviz/lua: No such file or directory
ldconfig: Can't stat /usr/lib64/graphviz/tcl: No such file or directory
ldconfig: Can't stat /usr/lib64/graphviz/guile: No such file or directory
ldconfig: Can't stat /usr/lib64/graphviz/ruby: No such file or directory
ldconfig: Path `/opt/kde3/lib64' given more than once
ldconfig: Path `/opt/kde3/lib' given more than once
ldconfig: Can't stat /libx32: No such file or directory
ldconfig: Can't stat /usr/libx32: No such file or directory
ldconfig: Cannot stat /opt/kde3/lib64/libgmcop.so: No such file or directory
liblog4cpp.so.5 -> liblog4cpp.so.5.0.6
liblog4cpp.so.6.0 -> liblog4cpp.so.6.0.0
liblog4cpp.so.5 -> liblog4cpp.so.5.0.6



On Sun, 2 Apr 2017 20:27:03 -0700
Cinaed Simson  wrote:

> On 04/02/2017 04:17 PM, li...@lazygranch.com wrote:
> > Regarding the Marcus cmake, I guessed that src would copy to lib,
> > but that didn't happen. (Easy to check by file dates.) I ended up
> > copying the new FindLog4cpp.cmake to both locations myself. I did a
> > diff with the -s option and they are the same. 
> > 
> > diff
> > -s /usr/local/src/gnuradio/cmake/Modules/FindLog4cpp.cmake 
> > /usr/local/lib/cmake/gnuradio/FindLog4cpp.cmake
> > Files /usr/local/src/gnuradio/cmake/Modules/FindLog4cpp.cmake
> > and /usr/local/lib/cmake/gnuradio/FindLog4cpp.cmake are identical
> > 
> > 
> > The problem is still there. I downloaded the log4cpp from the
> > opensuse repo, which of course would use the "normal" library
> > (/usr/lib64) rather than the local library, but that didn't work
> > either.
> > 
> > So in summary, the problem is still there.   
> 
> Correct me if I'm wrong, but it appears the system installed version
> of liblog4cpp is in /usr/lib64 and the source version you built is in
> /usr/local/lib64.
> 
> Please post the output of
> 
>yum search log4cpp
> 
> and
> 
>   ldconfig -v | grep liblog4cpp
> 
> -- Cinaed
> > 
> > 
> > On Sun, 2 Apr 2017 14:16:07 -0700
> > Cinaed Simson  wrote:
> >   
> >> On 04/01/2017 03:40 PM, li...@lazygranch.com wrote:  
> >>>
> >>> find / -name "FindLog4cpp.cmake"
> >>> /usr/local/src/gnuradio/cmake/Modules/FindLog4cpp.cmake
> >>> /usr/local/lib/cmake/gnuradio/FindLog4cpp.cmake
> >>>
> >>> That file is found twice. Is that the problem? If not, which do I
> >>> replace? Or perhaps both. Or does one file cause the other file to
> >>> be updated?  
> >>
> >> No, one file is the source file and the other file is the
> >> installed in your gnuradio installation directory.
> >>
> >> Try
> >>
> >>diff /usr/local/src/gnuradio/cmake/Modules/FindLog4cpp.cmake
> >> /usr/local/lib/cmake/gnuradio/FindLog4cpp.cmake
> >>
> >> That is, diff on the two files and make sure they're the same.
> >>
> >> If they're different, I'm not sure which one it would be reading -
> >> my guess would be the one
> >> /usr/local/src/gnuradio/cmake/Modules/FindLog4cpp.cmake.
> >>
> >> In any case, I'm not sure where you stand with this problem.
> >>
> >> Did you receive a file from Marcus?
> >>
> >> -- Cinaed
> >>
> >>  
> >>>
> >>>
> >>> On Sat, 1 Apr 2017 19:03:52 +0200
> >>> Marcus Müller  wrote:
> >>>  
>  That's very interesting, considering that I believe the CMake
>  script that looks for log4cpp uses the same pkg-command to look
>  for it...
> 
>  Ok. So there's something strange going on with that
>  cmake/Modules/FindLog4cpp.cmake, probably.
> 
>  Can you replace that Find...cmake with the one I've attached and
>  give it a try?
> 
>  Cheers,
> 
>  Marcus
> 
> 
>  On 01.04.2017 18:27, li...@lazygranch.com wrote:  
> > Hyphen instead of underscore.
> >
> > pkg-config --libs log4cpp
> > -L/usr/local/lib64 -llog4cpp 
> >
> > So pkg-config finds the library. Note I got the same problem
> > regarding not finding log4cpp when I used the opensuse package
> > manager version instead of making my own in /usr/src.
> >
> >
> >
> >
> > On Sat, 1 Apr 2017 11:19:14 +0200
> > Marcus Müller  wrote:
> >  
> >> Hi,
> >>
> >> if you've built it yourself, chances are that automatic tools
> >> like CMake's find_package or the general pkg_config can't find
> >> it, because you didn't put the right files in the
> >>>