search

pi-2r / volatility

Automatically exported from code.google.com/p/volatility
GNU General Public License v2.0
0 stars 0 forks source link

Cannot run the 'make' command #512

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. I tried searching online and look through yuor issues but found 
unsuccessful. 
2.

What is the expected output? What do you see instead?

What version of the product are you using? On what operating system?

I am running Linux Debian OS under my Virtual Machine. 

Please provide any additional information below.

This is what comes up in my terminal

make -C //lib/modules/3.2.0-41-generic/build CONFIG_DEBUG_INFO=y 
M=/home/santoku/Downloads/Volitility /volatility-2.3.1/tools/linux modules
make[1]: Entering directory `/usr/src/linux-headers-3.2.0-41-generic'
make[1]: *** No rule to make target `/volatility-2.3.1/tools/linux'.  Stop.
make[1]: Leaving directory `/usr/src/linux-headers-3.2.0-41-generic'
make: *** [dwarf] Error 2

I believe that according to a site, it is missing a relocs.c file by the 
makefile.  

Any help would be appreciated. 

Thanks

Original issue reported on code.google.com by Nicholas...@gmail.com on 23 Jul 2014 at 5:05

GoogleCodeExporter commented 9 years ago

Original comment by michael.hale@gmail.com on 24 Jul 2014 at 12:35

GoogleCodeExporter commented 9 years ago 
I also tried this over a week. But found to be unsucessful. I am not sure what 
will be the cause of this error, i even updated my correct linux header.

Original comment by Nicholas...@gmail.com on 24 Jul 2014 at 11:46

GoogleCodeExporter commented 9 years ago 
Can you please copy/paste the full command line input/output when running make?

Original comment by atc...@gmail.com on 24 Jul 2014 at 1:26

GoogleCodeExporter commented 9 years ago 
Here is my full code it has returned to me once i run the command make. 

santoku@santoku-virtual-machine:~/Downloads/Volitility /volatility-2.3.1/tools$ 
ls 
linux  mac  vtype_diff.py
santoku@santoku-virtual-machine:~/Downloads/Volitility /volatility-2.3.1/tools$ 
cd linux 
santoku@santoku-virtual-machine:~/Downloads/Volitility 
/volatility-2.3.1/tools/linux$ ls 
Makefile  module.c  pmem
santoku@santoku-virtual-machine:~/Downloads/Volitility 
/volatility-2.3.1/tools/linux$ make
make -C //lib/modules/3.2.0-41-generic/build CONFIG_DEBUG_INFO=y 
M=/home/santoku/Downloads/Volitility /volatility-2.3.1/tools/linux modules
make[1]: Entering directory `/usr/src/linux-headers-3.2.0-41-generic'
make[1]: *** No rule to make target `/volatility-2.3.1/tools/linux'.  Stop.
make[1]: Leaving directory `/usr/src/linux-headers-3.2.0-41-generic'
make: *** [dwarf] Error 2

Original comment by Nicholas...@gmail.com on 24 Jul 2014 at 5:41

GoogleCodeExporter commented 9 years ago 
I even tried running sudo make command but nothing

Original comment by Nicholas...@gmail.com on 24 Jul 2014 at 5:46

GoogleCodeExporter commented 9 years ago 
Hmm that is quite confusing.

Can you cat your Makefile?

Original comment by atc...@gmail.com on 24 Jul 2014 at 5:50

GoogleCodeExporter commented 9 years ago 
This is what i get when i cat Makefile run. 

santoku@santoku-virtual-machine:~/Downloads/Volitility 
/volatility-2.3.1/tools/linux$ cat Makefile
obj-m += module.o
KDIR ?= /
KVER ?= $(shell uname -r)

-include version.mk

all: dwarf 

dwarf: module.c
    $(MAKE) -C $(KDIR)/lib/modules/$(KVER)/build CONFIG_DEBUG_INFO=y M=$(PWD) modules
    dwarfdump -di module.ko > module.dwarf
    $(MAKE) -C $(KDIR)/lib/modules/$(KVER)/build M=$(PWD) clean

clean:
    $(MAKE) -C $(KDIR)/lib/modules/$(KVER)/build M=$(PWD) clean
    rm -f module.dwarf

Original comment by Nicholas...@gmail.com on 25 Jul 2014 at 1:45

GoogleCodeExporter commented 9 years ago 
But when i entered the make command alone. The following code appear. 

santoku@santoku-virtual-machine:~/Downloads/Volitility 
/volatility-2.3.1/tools/linux$ make 
make -C //lib/modules/3.2.0-41-generic/build CONFIG_DEBUG_INFO=y 
M=/home/santoku/Downloads/Volitility /volatility-2.3.1/tools/linux modules
make[1]: Entering directory `/usr/src/linux-headers-3.2.0-41-generic'
make[1]: *** No rule to make target `/volatility-2.3.1/tools/linux'.  Stop.
make[1]: Leaving directory `/usr/src/linux-headers-3.2.0-41-generic'
make: *** [dwarf] Error 2

Original comment by Nicholas...@gmail.com on 25 Jul 2014 at 1:53

GoogleCodeExporter commented 9 years ago 
Can you:

ls /usr/src

And can you also run:

sudo apt-get install linux-headers-`uname -r`

Assuming you are building a profile for the system that is running. If you 
aren't can you explain how you put together your headers directory?

Original comment by atc...@gmail.com on 25 Jul 2014 at 1:56

GoogleCodeExporter commented 9 years ago 
This is what i get from running ls/usr/src 

linux-headers-3.2.0-23             linux-headers-3.5.0-26
linux-headers-3.2.0-23-generic     linux-headers-3.5.0-26-generic
linux-headers-3.2.0-41             linux-headers-lbm-3.2.0-41-generic
linux-headers-3.2.0-41-generic     linux-headers-lbm-3.2.0-41-virtual
linux-headers-3.2.0-41-lowlatency  linux-source-3.2.0
linux-headers-3.2.0-41-virtual     linux-source-3.2.0.tar.bz2

After running sudo apt-get install linux-headers-`uname -r

santoku@santoku-virtual-machine:~/Downloads/Volitility 
/volatility-2.3.1/tools/linux$ sudo apt-get install linux-headers-`uname -r`
[sudo] password for santoku: 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
linux-headers-3.2.0-41-generic is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 384 not upgraded.

I had to just installed and the linux update and it provides me with all the 
header. i also installed my correct header

Original comment by Nicholas...@gmail.com on 25 Jul 2014 at 2:09

GoogleCodeExporter commented 9 years ago 
Ok, what made you originally say about 'relocs.c' in your first post? I don't 
see relocs.c in any output.

Original comment by atc...@gmail.com on 25 Jul 2014 at 2:16

GoogleCodeExporter commented 9 years ago 
I get it from this a site. 

According to it, it say when i get this rule as shown below. i need the relic.c 
file

make[2]: * No rule to build the target « arch/x86/tools/relocs.c », needed 
for « arch/x86/tools/relocs ». Stop.

The makefile is looking for a code module called relocs.c.

Original comment by Nicholas...@gmail.com on 25 Jul 2014 at 2:21

GoogleCodeExporter commented 9 years ago 
So, i am not sure if it needs it to run the make command in linux

Original comment by Nicholas...@gmail.com on 25 Jul 2014 at 2:22

GoogleCodeExporter commented 9 years ago 
Hiya Nicholas,

Could you please try moving your Volatility directory to one that doesn't 
contain a space?  If that succeeds then we can investigate how to allow it to 
build when there is a space in the directory name.  If not then we'll have to 
keep searching for a solution...

Original comment by mike.auty@gmail.com on 26 Jul 2014 at 10:23

GoogleCodeExporter commented 9 years ago 
I try but its not a directory. it automatically put the space for it.  I just 
cant physically run the make command under the tools/linux directory but when i 
go to the  Volatility main folder and run it. I get this 

santoku@santoku-virtual-machine:~/Downloads/Volitility /volatility-2.3.1$ make
make: Nothing to be done for `all'.
santoku@santoku-virtual-machine:~/Downloads/Volitility /volatility-2.3.1$ 

Thank you for helping me because I tried it for a week and no help, even asked 
people but no one knows.

Original comment by Nicholas...@gmail.com on 26 Jul 2014 at 2:42

GoogleCodeExporter commented 9 years ago 
My make command is already installed

Original comment by Nicholas...@gmail.com on 26 Jul 2014 at 2:45

GoogleCodeExporter commented 9 years ago 
Hi there,

I'm not sure you quite understood what I was trying to say.  From the output 
you provided, it looks like you've installed volatility into 
"~/Downloads/Volatility /volatility-2.3.1/".  The space at the end of the 
"Volatility " directory is probably what's causing your problems.  Please try 
the following commands from your Downloads directory:

santoku@santoku-virtual-machine:~/Downloads$ mv "Volatility " "Volatility"
santoku@santoku-virtual-machine:~/Downloads$ cd 
Volatility/volatility-2.3.1/tools/linux
santoku@santoku-virtual-machine:~/Downloads/Volitility/volatility-2.3.1/tools/li
nux$ make

Then let us know if that solves your compilation problems.

Original comment by mike.auty@gmail.com on 26 Jul 2014 at 5:22

GoogleCodeExporter commented 9 years ago 
this is what i get 

santoku@santoku-virtual-machine:~/Downloads/Volatility/volatility-2.3.1/tools$ 
cd linux
santoku@santoku-virtual-machine:~/Downloads/Volatility/volatility-2.3.1/tools/li
nux$ make
make -C //lib/modules/3.2.0-41-generic/build CONFIG_DEBUG_INFO=y 
M=/home/santoku/Downloads/Volatility/volatility-2.3.1/tools/linux modules
make[1]: Entering directory `/usr/src/linux-headers-3.2.0-41-generic'
  CC [M]  /home/santoku/Downloads/Volatility/volatility-2.3.1/tools/linux/module.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /home/santoku/Downloads/Volatility/volatility-2.3.1/tools/linux/module.mod.o
  LD [M]  /home/santoku/Downloads/Volatility/volatility-2.3.1/tools/linux/module.ko
make[1]: Leaving directory `/usr/src/linux-headers-3.2.0-41-generic'
dwarfdump -di module.ko > module.dwarf
make -C //lib/modules/3.2.0-41-generic/build 
M=/home/santoku/Downloads/Volatility/volatility-2.3.1/tools/linux clean
make[1]: Entering directory `/usr/src/linux-headers-3.2.0-41-generic'
  CLEAN   /home/santoku/Downloads/Volatility/volatility-2.3.1/tools/linux/.tmp_versions
  CLEAN   /home/santoku/Downloads/Volatility/volatility-2.3.1/tools/linux/Module.symvers

Original comment by Nicholas...@gmail.com on 26 Jul 2014 at 8:06

GoogleCodeExporter commented 9 years ago 
Ok, so that built fine.  The issue was having a space in the directory, and 
I've fixed this in the main repository with commit r3615.  Thanks for raising 
the issue, marking as Fixed.

Original comment by mike.auty@gmail.com on 26 Jul 2014 at 8:09