Hey Douglas, To install from source =======================
Step 1. Build makefile. autoreconf -if ./configure Step 2. Add yum repository for dependencies There are libraries that are not available in common repositories that you'll need to to install. There's a file you can add to your system that will allow it to pull dependecies from the sipfoundry sudo 'make repofile > /etc/yum.repos.d/sipxecs.repo' Step 3. Install missing dependencies make sipx.list-missings-deps | xargs sudo yum install Step 4. Build and install. Make sure you have permission to directory listed in --prefix= sudo mkdir -p /usr/local/sipx sudo chown $USER:$USER /usr/local/sipx make all-install Step 5. To run. NOTE: This will run as the user you are currently looged-in as, even though you are starting w/root permissions sudo /usr/local/sipx/bin/sipxecs-setup sudo /usr/local/sipx/etc/init.d/sipxecs start Problems: - make repofile doesn't work (wget http://download.sipfoundry.org/pub/sipXecs/sipxecs-0.0.4.5.2-centos.repo) - make sipx.list-missing-deps should be make sipx.deps-missing-build-list - the yum install should then make sipx.deps-missing-build-list | xargs yum -y install - make all-install = make sipx - make app is not in there - one should not compile as root, no methioning about that Fixed Readme. It's a start… Can you give me access to the tree Douglas? Then I will change this for you. To install from source ======================= Building will work on Fedora or CentOS. Don't compile as root. Step 1. Build makefile. autoreconf -if ./configure Step 2. Add yum repositories for dependencies There are libraries that are not available in common repositories that you'll need to to install. There are repo files for several versions of Fedora en CentOS you can add to your system that will allow it to pull dependecies from the sipfoundry (download.sipfoundry.org). Depending on your OS you might also need RPMforge. Step 3. Install missing dependencies, first for building, then for running. make sipx.deps-missing-build-list | xargs sudo -y yum install make sipx.deps-missing | grep -v sipx | xargs sudo -y yum install Step 4. Build and install. Make sure you have permission to directory listed in --prefix= sudo mkdir -p /usr/local/sipx sudo chown $USER:$USER /usr/local/sipx make sipx Step 5. Add optional packages. You will need public key github access for this to work. To include all optional packages: make app Step 6. To run. NOTE: This will run as the user you are currently looged-in as, even though you are starting w/root permissions sudo /usr/local/sipx/bin/sipxecs-setup sudo /usr/local/sipx/etc/init.d/sipxecs start Op 6 okt. 2011, om 12:21 heeft Douglas Hubler het volgende geschreven: > On Thu, Oct 6, 2011 at 5:47 AM, Niek Vlessert <[email protected]> wrote: >> Then I tried to use sipx-setup-system to setup stuff. But that gave me that >> /var/named not exists. So I was like, ah no DNS, ok, I'll install. > > I don't use sipxecs-setup-system, just sipxecs-setup. > DNS/DHCP/FTP/TFTP will/should be up to you for source installs. > >> So then I used make sipx.deps-missing which should List all dependencies to >> run a package(s) that are not currently installed on this system. That gave >> me a list. But in that list there is a bunch of SipX RPMs > > you're right. Ignore the "sipx" ones for now. > > FYI: I think the deps management needs to be reconsidered. Parsing the > spec files can be problematic and prone to incorrect results but it > was all I had time for at the moment. We may need to invent a > explicit specification to declare project dependencies independent of > the spec files. > >> . That's not what I need, i just want the required dependencies and then use >> my current install. Am I thinking the wrong way? > > I think you're ok. Dependencies should be installed via rpms when > they are available, which luckily they now are for centos 6 on > sipfoundry. if ever you need to install a deps via source and not the > RPM, that should be possible too. In those case you often have to run > ./configure --help in each project to see if it accepts directory > paths to find where you installed a particular dependency. > >> Right now I'm compiling again (because I just learned about the git >> submodule init thing) and then I will try to manually add what i need. > > sorry, I didn't realize you were trying to build/install source. Yes > the README needs updating and although I would welcome an updated > README, I suspect I would need to go thru it myself to ensure best > practices are followed. There are only placeholders for > instructions on wiki as well. > > Thanks for speaking up, helps me realize what pieces are missing. > _______________________________________________ > sipx-dev mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev/
_______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
