Re: Help in removing Oprofile

[Shiva M <shi...@gm...>]

Hi Will,

I am using Oprofile 0.9.9.  I tried with Oprofile-1.0.0 but later I found
kernel CPU counters were not supported. Shall I try with Oprofile-0.9.7?. I
did following to build Oprofile

Oprofile-0.9.9>./configure --enable-static  --with-kernel-support
 --prefix=/home/shiva/usr
    sudo make
    make install
    DESTDIR="/home/shiva/user"


Thanks,
Shiva

On Wed, Feb 1, 2017 at 10:56 PM, William Cohen <wc...@re...> wrote:

> On 02/01/2017 12:17 PM, Shiva M wrote:
> > Hi William,
> >
> > Also, I have built Oprofile as part of rootfs. My linux version is
> 2.6.38, but Oprofile is not running on my target machine.
> >
> > I see the following :
> > modprobe: chdir(/lib/modules): No such file or directory
> > Kernel doesn't support oprofile
> >
> > I have enabled CONFIG_OPROFILE as part of .config, downloaded and built
> popt/, binutils/ and Oprofile. Built went successfully but opcontrol is not
> working. Can you please help what I am doing wrong.
> >
> > Thanks,
> > Shiva
>
> Hi Shiva,
>
> Which specific version of oprofile are you building? Newer versions of
> oprofile since 0.9.8 have used the kernels perf infrastructure to collect
> data.  Kernels sinces 2.6.32 have provided the perf systemcall.  Depending
> how your kernel is built it may or may not have the oprofile driver built.
> I know that we disabled (kernel CONFIG_OPROFILE is not set for the kernel
> builds) in in more recent versions of Fedora because the newer versions of
> oprofile did not use it and opcontrol was removed.  One should be using
> operf instead to collect data.
>
> -Will
>
> >
> >
> > On Wed, Feb 1, 2017 at 10:34 PM, Shiva M <shi...@gm...
> <mailto:shi...@gm...>> wrote:
> >
> >     Hi William,
> >
> >     Thanks a ton for your response. I have found the cause of my issue,
> after adding -ldl to other packages, build went through fine.  I tried
> doing make uninstall to give a try to uninstall Oprofile and re-install but
> its not working. I have deleted Oprofile package directory after building,
> I downloaded again and tried make uninstall but that not worked.
> >
> >     Thanks,
> >     Shiva
> >
> >     On Tue, Jan 31, 2017 at 10:07 PM, William Cohen <wc...@re...
> <mailto:wc...@re...>> wrote:
> >
> >         On 01/31/2017 05:58 AM, Shiva M wrote:
> >         > Hi All,
> >         >
> >         > I have build Oprofile from source on my system. Oprofile is
> workng fine. I have not specified any installation directory while building
> Oprofile, it installed to default directories.
> >         >
> >         >
> >         > We have one ts/ package which was building fine before. Atter
> installign Oprofile on my system, I see
> >         >
> >         > [0m/usr/bin/ld: ../libscul.a(scul_sslcompat.c.o): undefined
> reference to symbol 'dlsym@@GLIBC_2.2.5'
> >         >
> >         > /lib/x86_64-linux-gnu/libdl.so.2: error adding symbols: DSO
> missing from command line
> >         >
> >         > collect2: ld returned 1 exit status
> >         >
> >         > make[2]: *** [source/scul/selftests/scul_asn1_test] Error 1
> >         >
> >         > make[1]: *** [source/scul/selftests/
> CMakeFiles/scul_asn1_test.dir/all] Error 2
> >         >
> >         > make: *** [all] Error 2
> >         >
> >         >
> >         > Any help would be appreciated.
> >         >
> >         >
> >         > I want to remove Oprofile and re-install on specific install
> directory
> >         >
> >         >
> >         > Thanks,
> >         >
> >         > Shiva
> >
> >
> >         Hi Shiva,
> >
> >         It is unlikely that oprofile is causing the build with the other
> package.  Was there anything else changed in the sources or system?
> OProfile does install some additional librarys, but it is unlikely to
> significantly affect libraries for other things.  If the software that is
> having this problem is in a git repository you might try to check out
> earlier versions and see if a specific patch is causing this problem.
> >
> >         By default oprofile should install things in /usr/local/bin/ (o*
> commands), /usr/local/share/oprofile/, and /usr/local/lib/oprofile.  If you
> still have the oprofile build directory that installed them, then you
> should as root be able to the following as root to remove the oprofile
> installed files:
> >
> >         make uninstall
> >
> >         -Will
> >
> >
> >
>
>