|
From: david m. <cac...@ya...> - 2008-11-04 02:04:40
|
hello I am new to freeBSD so bare with the stupid questions
i have mounted proc
and ee fstab according to google's instruction
then did a make install in the valgrind ports directory.
I have no idea what is considered normal or if it blowing up get lots of text that i dont fully understand ill copy and paste some just to make sure its the norm.
___________________________________________________________________________
gmake[3]: Leaving directory `/usr/ports/devel/valgrind/work/valgrind-stable-352/lackey/tests'
gmake[2]: Leaving directory `/usr/ports/devel/valgrind/work/valgrind-stable-352/lackey'
Making all in none
gmake[2]: Entering directory `/usr/ports/devel/valgrind/work/valgrind-stable-352/none'
Making all in .
gmake[3]: Entering directory `/usr/ports/devel/valgrind/work/valgrind-stable-352/none'
if cc -DHAVE_CONFIG_H -I. -I. -I.. -I../include -DVG_LIBDIR="\"/usr/local/lib"\" -Winline -Wall -Wshadow -O -fomit-frame-pointer -mpreferred-stack-boundary=2 -g -MT nl_main.o -MD -MP -MF ".deps/nl_main.Tpo" -c -o nl_main.o nl_main.c; \
then mv -f ".deps/nl_main.Tpo" ".deps/nl_main.Po"; else rm -f ".deps/nl_main.Tpo"; exit 1; fi
cc -Winline -Wall -Wshadow -O -fomit-frame-pointer -mpreferred-stack-boundary=2 -g -o vgskin_none.so -shared -Wl,-rpath,../coregrind nl_main.o
mkdir -p ../.in_place
rm -f ../.in_place/vgskin_none.so
ln -f -s ../none/vgskin_none.so ../.in_place/vgskin_none.so
gmake[3]: Leaving directory `/usr/ports/devel/valgrind/work/valgrind-stable-352/none'
Making all in docs
gmake[3]: Entering directory `/usr/ports/devel/valgrind/work/valgrind-stable-352/none/docs'
gmake[3]: Nothing to be done for `all'.
gmake[3]: Leaving directory `/usr/ports/devel/valgrind/work/valgrind-stable-352/none/docs'
Making all in tests
gmake[3]: Entering directory `/usr/ports/devel/valgrind/work/valgrind-stable-352/none/tests'
gmake[3]: Nothing to be done for `all'.
gmake[3]: Leaving directory `/usr/ports/devel/valgrind/work/valgrind-stable-352/none/tests'
gmake[2]: Leaving directory `/usr/ports/devel/valgrind/work/valgrind-stable-352/none'
gmake[1]: Leaving directory `/usr/ports/devel/valgrind/work/valgrind-stable-352'
__________________________________________________________________________
A. is that normal ^^ ?
B. could i get a verbatim example of a tool command. sometimes i am not sure what should be considered abstract and literal with the manuals
For instance:
I should be able to do --version and get the version right? no matter what directory I am in.
It is telling me command not found so did i not install it properly or do i have to be in a special directory?
again thanks for helping a noob out.
|
|
From: Chris P. <jud...@gm...> - 2008-11-04 02:46:50
|
The make install output doesn't indicate any error. Having said that if you're just doing make install thats probably not enough. Before we get to far just check that valgrind isn't already installed most Linux distros ship with it I'm guessing the same is true for BSD. From a shell type 'valgrind --version' here is an example from my system chrisp@localhost:~> valgrind --version valgrind-3.2.3 If you do want to compile your own valgrind from source the normal steps are below. I emphasise the fact that its probably easier to get it from your package installation system (I don't know what freeBSD uses for this) rather than building it from scratch. # extract the source from your tarball tar -xf valgrind-3.2.3.tar.bz2 # configure it for your system, there are a bunch of options you can pass to ./configure I won't confuse matters by putting in the ones I use cd valgrind-3.2.3 ./configure # build it make # install it (sudo is needed if you're not using the root user account, also I'm not sure if sudo is available on BSD systems) sudo make install Try the 'valgrind --version' again and if everything has gone well it should be the version that has just been compiled. A simple usage is just 'valgrind <app>' e.g. valgrind ls Depending on your system you may need to specifiy the full path to the app you want to debug e.g. valgrind /bin/ls Once you're comfortable with that you can start using the different tools e.g valgrind --tool=memcheck ls memcheck is the default tool so 'valgrind ls' and 'valgrind --tool=memcheck ls' will do the same thing. Hope that helps On Tue, Nov 4, 2008 at 3:04 PM, david mellick <cac...@ya...>wrote: > hello I am new to freeBSD so bare with the stupid questions > > i have mounted proc > and ee fstab according to google's instruction > > then did a make install in the valgrind ports directory. > I have no idea what is considered normal or if it blowing up get lots of > text that i dont fully understand ill copy and paste some just to make sure > its the norm. > > > ___________________________________________________________________________ > gmake[3]: Leaving directory > `/usr/ports/devel/valgrind/work/valgrind-stable-352/lackey/tests' > gmake[2]: Leaving directory > `/usr/ports/devel/valgrind/work/valgrind-stable-352/lackey' > Making all in none > gmake[2]: Entering directory > `/usr/ports/devel/valgrind/work/valgrind-stable-352/none' > Making all in . > gmake[3]: Entering directory > `/usr/ports/devel/valgrind/work/valgrind-stable-352/none' > if cc -DHAVE_CONFIG_H -I. -I. -I.. -I../include > -DVG_LIBDIR="\"/usr/local/lib"\" -Winline -Wall -Wshadow -O > -fomit-frame-pointer -mpreferred-stack-boundary=2 -g -MT nl_main.o -MD -MP > -MF ".deps/nl_main.Tpo" -c -o nl_main.o nl_main.c; \ > then mv -f ".deps/nl_main.Tpo" ".deps/nl_main.Po"; else rm -f > ".deps/nl_main.Tpo"; exit 1; fi > cc -Winline -Wall -Wshadow -O -fomit-frame-pointer > -mpreferred-stack-boundary=2 -g -o vgskin_none.so -shared > -Wl,-rpath,../coregrind nl_main.o > mkdir -p ../.in_place > rm -f ../.in_place/vgskin_none.so > ln -f -s ../none/vgskin_none.so ../.in_place/vgskin_none.so > gmake[3]: Leaving directory > `/usr/ports/devel/valgrind/work/valgrind-stable-352/none' > Making all in docs > gmake[3]: Entering directory > `/usr/ports/devel/valgrind/work/valgrind-stable-352/none/docs' > gmake[3]: Nothing to be done for `all'. > gmake[3]: Leaving directory > `/usr/ports/devel/valgrind/work/valgrind-stable-352/none/docs' > Making all in tests > gmake[3]: Entering directory > `/usr/ports/devel/valgrind/work/valgrind-stable-352/none/tests' > gmake[3]: Nothing to be done for `all'. > gmake[3]: Leaving directory > `/usr/ports/devel/valgrind/work/valgrind-stable-352/none/tests' > gmake[2]: Leaving directory > `/usr/ports/devel/valgrind/work/valgrind-stable-352/none' > gmake[1]: Leaving directory > `/usr/ports/devel/valgrind/work/valgrind-stable-352' > __________________________________________________________________________ > > A. is that normal ^^ ? > > B. could i get a verbatim example of a tool command. sometimes i am not > sure what should be considered abstract and literal with the manuals > > For instance: > I should be able to do --version and get the version right? no matter > what directory I am in. > > It is telling me command not found so did i not install it properly or do i > have to be in a special directory? > > > > again thanks for helping a noob out. > > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Valgrind-users mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-users > > |
|
From: Chris P. <jud...@gm...> - 2008-11-04 22:04:33
|
OK so forget most of my jabbering. To get back to the original question. The make install output looks fine. Try 'valgrind --version' to see if it is installed. If it is then try 'valgrind ls' or 'valgrind --tool=memcheck ls' On Wed, Nov 5, 2008 at 5:16 AM, tom fogal <tf...@al...> wrote: > "Chris Packham" <jud...@gm...> writes: > > If you do want to compile your own valgrind from source the normal steps > are > > below. I emphasise the fact that its probably easier to get it from your > > package installation system (I don't know what freeBSD uses for this) > rather > > than building it from scratch. > > The open source BSDs have a `ports' system, which is a source-based > package management solution. He just wants to cd to valgrind's port > directory and run `sudo make install'. > > > I'm not sure if sudo is available on BSD systems) > > sudo make install > > It's in ports, but last I checked wasn't installed by default. > > -tom > |