<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Keep [C]*(od&#124;do)ing &#187; bluehost</title>
	<atom:link href="http://liwen.name/tag/bluehost/feed/" rel="self" type="application/rss+xml" />
	<link>http://liwen.name</link>
	<description>Grow with the flow</description>
	<lastBuildDate>Fri, 10 Jul 2009 19:37:56 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Save Subversion Server on BlueHost</title>
		<link>http://liwen.name/2009/06/save-subversion-server-on-bluehost/</link>
		<comments>http://liwen.name/2009/06/save-subversion-server-on-bluehost/#comments</comments>
		<pubDate>Mon, 15 Jun 2009 14:30:03 +0000</pubDate>
		<dc:creator>Liwen</dc:creator>
				<category><![CDATA[Tools]]></category>
		<category><![CDATA[software]]></category>
		<category><![CDATA[bluehost]]></category>
		<category><![CDATA[subversion]]></category>

		<guid isPermaLink="false">http://liwen.name/?p=336</guid>
		<description><![CDATA[The first command I typed in Emacs this morning was “svn up“. Two seconds later, the unexpected unwelcome stranger “svnserve: error while loading shared libraries: libpq.so.3: cannot open shared object file: No such file or directory” popped into my screen, I felt my heart jumped up into my throat and my blood pressure went up [...]]]></description>
			<content:encoded><![CDATA[<p>The first command I typed in Emacs this morning was “<code>svn up</code>“. Two seconds later, the unexpected unwelcome stranger “<code>svnserve: error while loading shared libraries: libpq.so.3: cannot open shared object file: No such file or directory</code>” popped into my screen, I felt my heart jumped up into my throat and my blood pressure went up a bit. This is no good***@#^&#038; :&#8211;(</p>
<p>Checked on BlueHost support site and was informed that they have upgraded PostgreSQL and have recompiled Apache. I suppose I couldn’t ask BlueHost tech support regarding the issue since Subversion is not something included in the hosting package.</p>
<p>Found <a href="http://www.nabble.com/svn:-error-while-loading-shared-libraries:-libpq.so.3:-cannot-open-shared-object-file:-No-such-file-or-directory-td23891720.html#a24017347" rel="external">this thread</a> on Google suggesting to ‘rebuild apt-util’ but without giving any solution, so I decided to roll my sleeves and solve the problem on my own.</p>
<p>Here was my installation hosting environment:<br />
1.	Bluehost 64bit box<br />
2.	subversion 1.5.5</p>
<p>And here is <a href="http://liwen.name/2009/02/bluehost-subversion-windows-cmd/">how I installed subversion in the first place</a>, you may want to check this post (referring as <em>post #1</em> form now on) first as the following steps are partially in the same context with it.</p>
<p><strong>Failed trying to reconfigure</strong></p>
<p>Tried to install all subversion dependencies downloaded in post #1, it ignores the installation and says the libraries have been installed.<br />
Tried to reconfigure and link, got lots of &#8216;<code>cannot read symbols</code>&#8216; error. One of the errors seems to be version related problem which I encountered before while doing apache upgrading.</p>
<p>I guess I may need higher version of <code>apr</code> and <code>apr-util</code> and hope they will still work with subversion 1.5.5, otherwise I’ll have to upgrade my svn on the server as well. </p>
<p><strong>Download apr and apr-util</strong></p>
<p><code>cd src<br />
wget http://www.apache.org/dist/apr/apr-1.3.5.tar.gz<br />
wget http://www.apache.org/dist/apr/apr-util-1.3.7.tar.gz<br />
tar -xzvf apr-1.3.5.tar.gz<br />
tar -xzvf apr-util-1.3.7.tar.gz</code></p>
<p><strong>Install apr</strong></p>
<p><code>cd apr-1.3.5<br />
./configure --enable-shared --prefix=$HOME LDFLAGS="-L/lib64"<br />
make &#038;&#038; make install</code></p>
<p><strong>Install apr-util</strong></p>
<p><code>cd ../apr-util-1.3.7<br />
./configure --enable-shared --prefix=$HOME --with-apr=$HOME --without-berkeley-db LDFLAGS="-L/lib64"<br />
make &#038;&#038; make install</code></p>
<p><strong>Install neon</strong></p>
<p>Since <code>neon</code> depends on <code>apr</code> and <code>apr-util</code>, I&#8217;d better reinstall it as well, tried to install the <code>neon</code> comes with <code>subversion-dep-1.5.5.tar.gz</code> and this time it succeeded, great!</p>
<p><code>cd ../subversion-1.5.5/neon<br />
EXTRA_CFLAGS="-L/lib64 -fPIC"<br />
CFLAGS="-L/lib64 -fPIC"<br />
./configure --prefix=$HOME --enable-shared LDFLAGS="-L/lib64" --with-libs=$HOME<br />
make &#038;&#038; make install</code></p>
<p><strong>Reinstall Subversion</strong></p>
<p><code>cd ..<br />
./configure --prefix=$HOME --without-berkeley-db --with-apr=$HOME --with-apr-util=$HOME --with-neon=$HOME -without-apxs --without-apache<br />
make &#038;&#038; make install</code></p>
<p>Something you might want to know if you are going to follow my steps to save your svn server on BlueHost. As the information in this weblog is provided “AS IS” with no warranties : )</p>
<p>1.Check your BlueHost hosting environment (32 bit or 64 bit)<br />
2.Check your subversion version (a new repository schema has been introduced since version 1.4.?, you may want to download all repositories and upgrade them locally)<br />
3.Backup all repositories.<br />
4.If you are not sure about what those steps are all about please do read post #1, don&#8217;t replicate them blindly &#8211; for your server&#8217;s safety, although BlueHost backs up your home directory in daily and weekly intervals.<br />
5.There might be a better solution beyond my knowledge and you can wait for someone to find out – I am just a brave armature :)</p>
]]></content:encoded>
			<wfw:commentRss>http://liwen.name/2009/06/save-subversion-server-on-bluehost/feed/</wfw:commentRss>
		<slash:comments>10</slash:comments>
		</item>
		<item>
		<title>Install Subversion 1.5.5 on Bluehost 64bit Box</title>
		<link>http://liwen.name/2009/02/bluehost-subversion-windows-cmd/</link>
		<comments>http://liwen.name/2009/02/bluehost-subversion-windows-cmd/#comments</comments>
		<pubDate>Sat, 14 Feb 2009 23:55:18 +0000</pubDate>
		<dc:creator>Liwen</dc:creator>
				<category><![CDATA[Tools]]></category>
		<category><![CDATA[software]]></category>
		<category><![CDATA[bluehost]]></category>
		<category><![CDATA[ssh]]></category>
		<category><![CDATA[subversion]]></category>

		<guid isPermaLink="false">http://localhost/wordpress/?p=20</guid>
		<description><![CDATA[The first thing I do before start typing code at home is to put it under version control system; the first thing I tried to do when had a SSH enabled reliable hosting, of course, was to set up Subversion server on it. There are already several tutorials in the Internet, why I am writing [...]]]></description>
			<content:encoded><![CDATA[<p>The first thing I do before start typing code at home is to put it under version control system; the first thing I tried to do when had a SSH enabled reliable hosting, of course, was to set up Subversion server on it.</p>
<p>There are already several tutorials in the Internet, why I am writing this again? Well, I just wanted to prove that I too, can write blog!  Among all those tutorials, none of them worked for me, I guess either I was trying to install the newest version of SVN or the BlueHost hosting environment has changed, or they just hate me. So I am constructing this and hope to contribute something I learned along the frustrating process of setting up SVN on 64bit shared hosting so you don’t need to smash your keyboard.</p>
<p>Once you enabled SSH on BlueHost control panel with a photo ID, it’s time to set up Subversion.</p>
<p>1. Open a terminal, type in:<br />
<code>ssh username@yourdomain.com</code><br />
and hit enter, then input your hosting password.</p>
<p>2. It’s better to create a separate folder for all the operations, in case our home directories got messed up by any mistakes.</p>
<p><code>mkdir src<br />
cd src</code></p>
<p>3. Download Subversion and dependencies:</p>
<p><code>wget http://subversion.tigris.org/downloads/subversion-1.5.5.tar.gz<br />
wget http://subversion.tigris.org/downloads/subversion-deps-1.5.5.tar.gz<br />
tar -xzvf subversion-1.5.5.tar.gz<br />
tar -xzvf subversion-deps-1.5.5.tar.gz<br />
cd subversion-1.5.5</code></p>
<p>4. Install <code>apr</code> and <code>apr-util</code>, notice the var <code>LDFLAGS</code> , it&#8217;s 64 bit, it&#8217;s m-A-g-I-c.</p>
<p><code>cd apr<br />
./configure --enable-shared --prefix=$HOME LDFLAGS="-L/lib64"<br />
make &#038;&#038; make install</code></p>
<p><code>cd ../apr-util<br />
./configure --enable-shared --prefix=$HOME<br />
--with-apr=$HOME --without-berkeley-db LDFLAGS="-L/lib64"<br />
make &#038;&#038; make install</code></p>
<p>5. Install <code>neon</code>, I had been stuck here for an hour because of the 64 bit mode problem, remember to explicitly enable compilation of shared libraries and prefix the files into home directory.</p>
<p><code>cd ../neon<br />
EXTRA_CFLAGS="-L/lib64 -fPIC"<br />
CFLAGS="-L/lib64 -fPIC"<br />
./configure --prefix=$HOME --enable-shared LDFLAGS="-L/lib64" --with-libs=$HOME<br />
make &#038;&#038; make install</code></p>
<p>6. Install Subversion, pass <code>--without-apxs</code> and -<code>-without-apache</code> to prevent svn installing Apach modules, also you need to explicitly specify the dependencies.</p>
<p><code>cd ../<br />
./configure --prefix=$HOME --without-berkeley-db --with-apr=$HOME --with-apr-util=$HOME --with-neon=$HOME<br />
-without-apxs --without-apache<br />
make &#038;&#038; make install</code></p>
<p>7. Modify <code>.bash_profile</code> and <code>.bashrc</code> file</p>
<p><code>nano -w .bash_profil</code>e (pico is always my favourite.)<br />
add <code>$HOME/system/bin</code> to <code>PATH</code> variable, it should look like this:<br />
<code>PATH=$PATH:$HOME/bin:$HOME/system/bin</code><br />
Also add this line to your <code>.bashrc</code> file, after the &#8216;<code>fi</code>&#8216;<br />
PATH=$PATH:$HOME/bin</p>
<p>8. Logout the current session and log on again, let’s try:<br />
<code>mkdir ~/repos<br />
cd repos<br />
svnadmin create topsecrets007plus</code></p>
<p>now you can access your repository like this:<br />
<code>svn+ssh://username@host/home/username/repos/topsecrets007plus/</code><br />
just replace username with your 8-character user name given by BlueHost.</p>
]]></content:encoded>
			<wfw:commentRss>http://liwen.name/2009/02/bluehost-subversion-windows-cmd/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>
