“cd” to the extracted directory where you downloaded the tarball of asterisk. Try to not copy and paste commands but understand what the commands does.
You do not compile AsteriskNOW; it is for people who want to install Asterisk without even a basic understanding of Linux/Unix and who have probably never compiled a program in their life. You want Asterisk Support if you are building from source (or writing your own configurations).
Assuming Asterisk 11 has the same tarball structure as previous versions, you would expect the directory containing the source tree to be immediately below the current directory and named asterisk-. I’ve just downloaded it and looked. It does follow that convention. It should extract to asterisk-11.2.0 in the current directory and you should change to asterisk-11.2.0 and run the build commands from there.
Where did you get the tarball from and how did you extract it? Where did you get the build instructions from?
With both DAHDI and LibPRI installed, we can now install Asterisk: $ cd ~/src/asterisk-complete/asterisk/11
If you are running 64-bit RHEL, run the configure script with the libdir option:
$ ./configure --libdir=/usr/lib64 On any other platform, run the configure script without any arguments:
$ ./configure Finally, compile and install Asterisk: $ make
$ sudo make install
$ sudo make config
Assuming the instructions are the same as for version 3 of the book, they assume that you have created the directories mentioned and you have populated them using svn, rather than the downloaded tar balls.
Reading between the lines, I think he has downloaded the tar balls and then not used them. Dahdi worked because the latest versions are in SVN, but he will not be able to do an SVN install for the latest branch 11 version, because the developers now use GIT. I guess he just didn’t understand that he had received an error when he tried to do the svn checkout.
The install instructions from once you have extracted the tar balls are in the README file in the first level extracted directory.
Note that the only slightly non-standard things about the whole process, from tar balls, are the make menuconfig and make samples steps.
As it occurs to me that he might not even have done the extract step but rather tried to use SVN for everything and not seen the error message, see cyberciti.biz/faq/unpack-tgz … mand-line/
The tar command extracts it, assuming you have already downloaded it.
You should not do both extract the tar and used svn.
There should only be one new directory visible in the current directory after running that tar command. cd in that and follow the instructions starting at ./configure.
(If you have run the svn, you will have several GB of files to remove first!)