Fixed several issues found using a coverity-scan

[proxmark3-svn] / COMPILING.txt

diff --git a/COMPILING.txt b/COMPILING.txt
index 536aa229249a92f22a0fe77f33636b3d4a736287..c894f0ff04f14f6d9aa7d61e2502140ce50225b6 100644 (file)
--- a/COMPILING.txt
+++ b/COMPILING.txt
@@ -94,10 +94,10 @@ http://sourceforge.net/projects/devkitpro/files/devkitARM
 Select the one you need (32bit or 64bit) and unpack to a convinient place, eg 
 $HOME/proxmark3/. It will create a devkitARM/ subdirectory.
 
 Select the one you need (32bit or 64bit) and unpack to a convinient place, eg 
 $HOME/proxmark3/. It will create a devkitARM/ subdirectory.
 

-Of course, you will need a general compiling environment on your computer for
+You will also need a general compiling environment on your computer for

 the client and the libusb headers. In most distributions you will get all you 
 need with the lsb-package (Linux Standard Base). In debian/ubuntu you simply 
 the client and the libusb headers. In most distributions you will get all you 
 need with the lsb-package (Linux Standard Base). In debian/ubuntu you simply 

-call `aptitude install lsb libusb-dev`. 
+call `aptitude install lsb libusb-dev libreadline-dev libreadline6`. 

 
 For the graphical plot view, you might need the qtlibs (debian/ubuntu: 
 libqt4-dev), too.
 
 For the graphical plot view, you might need the qtlibs (debian/ubuntu: 
 libqt4-dev), too.