You said you didn't mirror /usr/local, does that imply you copied over other things?
Best regards, Marcus On 03.04.2017 12:32, li...@lazygranch.com wrote: > Funny thing you mention a clean installation. I found btrfs to be a disaster > on opensuse. It turns out on some machines this is a known problem. It turned > out the snapshots provided by btrfs were worthless, and it would lock up my > machine. So I did a fresh install of opensuse on ext4 for the OS just last > week. I didn't mirror /usr/local, so everything there is fresh off of mostly > git source. So I would say the installation is as clean as can be expected. I > had to add the ham and science repositories. > > Original Message > From: Marcus Müller > Sent: Monday, April 3, 2017 3:19 AM > To: li...@lazygranch.com; discuss-gnuradio@gnu.org > Subject: Re: [Discuss-gnuradio] log4cpp library not found > > No, you probably shouldn't fiddle manually. You should rather figure out > what went wrong there. I'm getting the slight feeling that your system > might be pretty special; can you try this whole dance on a clean Suse > installation? Not quite sure we're not chasing ghosts here, due to > something else on your system breaking things and making it wrong to > make common assumptions about how things work on modern distros... > > Best regards, > > Marcus > > > On 03.04.2017 12:17, li...@lazygranch.com wrote: >> Yes to the dev install. >> >> I'm not exactly sure what I can do about ldconfig. >> >> Apologies in advance for an advert laden website link, but should I add >> /usr/local/lib64 as shown below: >> https://codeyarns.com/2014/01/14/how-to-add-library-directory-to-ldconfig-cache/ >> >> The odd thing is log4cpp is the only library with this problem, yet many >> other libraries are found in /usr/local by gnuradio. The libraries for the >> sdrs for example. I also built my own iqbalance (forgot the exact name) in >> /use/local. There was some issue with what opensuse provided. >> >> >> >> >> Original Message >> From: Marcus Müller >> Sent: Monday, April 3, 2017 3:02 AM >> To: discuss-gnuradio@gnu.org >> Subject: Re: [Discuss-gnuradio] log4cpp library not found >> >> Hi, >> >> Ok, there's something wrong with your ldconfig. Since we're actively >> talking about linkage of stuff, you would probably do good if you fixed >> that. >> >> Anyway, did you also install log4cpp-devel? >> >> Best regards, >> Marcus >> >> On 03.04.2017 08:12, li...@lazygranch.com wrote: >>> 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 <cinaed.sim...@gmail.com> 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 <cinaed.sim...@gmail.com> 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 <marcus.muel...@ettus.com> 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 <marcus.muel...@ettus.com> 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" <mle...@ripnet.com> 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 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
