1. Open Automator application
2. Create a new Service when prompted to “Choose a type for your document”
3. In the right pane configure the service so that it has “No Input” for the “Service Receives” pull down and select “Mail” in the pull down next to it (see the screen shot below)
4. In the Library select Mail and drag the action “Get Selected Mail Messages” into the workflow window (on the right)
5. In the Library select Utilities and drag the action “Run AppleScript” (NOT the “Execute AppleScript”) into the workflow window below the “Get Selected Mail Messages” Action
6. Copy the following code into the “Run AppleScript” Action window

   on run {input, parameters}
        tell application "Mail"
             repeat with eachMessage in input
                  bounce eachMessage
                  delete eachMessage
             end repeat
        end tell
   end run 

7. Your final screen should look like below
8. Save the workflow with a name like “Bounce Message”. This will save the workflow in the Library folder under your home directory in a subfolder called Services (not that you need to worry about this).

Now assuming you have two email accounts setup in Mail, send a test email from one account to the other. Then in the receiving account check for the new mail, select it, go to the “Mail” menu, under “Services” and select “Bounce Message”. This should bounce your test message back to it’s original sender (your other account) and delete it from your inbox. If you want to get really fancy you can even assign a keyboard shortcut to the “Bounce Message” Service. If for some reason you need to get rid of it, just delete the file under your personal Library directory (in finder hold down option while going to the “Go” menu and select “Library”), under Services folder.

find . -name "@eaDir" -type d -print |while read FILENAME; do echo "${FILENAME}"; done

Make sure you login via ssh first and “cd” to where your files are stored. This command starts looking for “@eaDir” folders recursively from the current directory.

I came across numerous sites that suggested adding a rule like:

RewriteCond %{REQUEST_URI} !=/server-status

This didn’t work for me. I’m not sure if the multisite version of wordpress (which I’m using) is causing this. The rule that worked beautifully is the following:

RewriteRule ^(server-info|server-status) - [L]

This rule stops the rewrite engine whenever server-info or server-status is parsed as part of the URL. So my .htaccess looks like this now:

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
# Stop Processing if you see server-info or server-status
RewriteRule ^(server-info|server-status) - [L]
# The Rewrite Condition below did not work
# RewriteCond %{REQUEST_URI} !=/server-status
RewriteCond %{REQUEST_FILENAME} -f
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule . index.php [L]
</IfModule>
# END WordPress

1.) Grab a copy of the Screen Capture DirectShow source filter from Unreal Streaming Technologies. It’s about half way down that page. They have both the UScreenCapture X86 Edition and the X64 Edition (depending on your OS installation). I used the 64 bit filter on a Windows 7 64 bit installation.

2.) Install the filter and make sure you make the following changes to your windows registry using regedit. The default frame rate for UScreenCapture filter is 10 f/s and we need to boost this to 30 frames/sec. You need to find the key HKLM\SOFTWARE\UNREAL\Live\UScreenCapture and insert a DWORD value of 30 for FrameRate (You have to create FrameRate, it does not exist by default). Once you’ve done the registry tweak, reboot.

3.) Install the latest greatest version of ffmpeg for your windows version from Zeranoe. I grabbed the 64 bit Static build since I didn’t want to deal with libraries and such. Extract it and stick it somewhere on your hard drive. Remember the path to this folder since we will need it later.

4.) Open a command line window and cd to the directory where you extracted ffmpeg into, find the bin directory and cd into it. This is were the ffmpeg executable resides. In my case (I extracted the ffmpeg files into “Program Files” directory) it is C:\Program Files\ffmpeg-git-059707e-win64-static\bin.

5.) If you’ve made it this far, hand in there, we’re almost home. Now you need to issue the command that gets the screen streaming going. But first we need to find out the name of the Screen filter device. So issue the following command:

ffmpeg -list_devices true -f dshow -i dummy

In the output look for a device called “UScreenCapture“. Hopefully if everything is working with the directshow filter you have a entry in the list. That’s the name of our device that we need to pass onto ffmpeg. While you’re there also look for your audio device entry as well. Mine was the truncated word “Stereo Mix (Realtek High Defini” (Yes mine was missing the end of that line). Jot that down somewhere as well. I will show you how to get audio going as well.

6.) So first step is to get video going. Assuming you have a “UScreenCapture” device (You could use another directshow filter if you like, this will work with most of them. I just used the Unreal filter for the heck of it), here is the command to start encoding and sending video:

ffmpeg -f dshow  -i video="UScreenCapture"  -r 30 -vcodec mpeg4 -q 12 -f mpegts udp://aaa.bbb.ccc.ddd:6666?pkt_size=188?buffer_size=65535

• -f dshow specifies that you’re going to be using a directshow device as your input.
• -i video=”UScreenCapture” is the name of the input directshow device which we picked up in step 5.
• -r 30 is the frame rate.
• -vcodec mpeg4 is our video codec of choice.
• -q 12 is a quality measure for the encoding process (1 is the best and 30 the worst). We’re doing VBR encoding so this measures the compression ratio vs. picture quality.
• -f mpegts is our output filetype. In this case mpeg-2 transport stream. Yes, we’re encapsulating mpeg4 video inside a mpeg-2 transport stream…..why?….google it.
• udp://aaa.bbb.ccc.ddd:6666?pkt_size=188?buffer_size=65535 this last bit specifies the address and port number of the recipient machine (aaa.bbb.ccc.ddd is the ip address of that machine and 6666 is my arbitrary port number). We’re also instructing ffmpeg to create smaller 188 byte size udp packets (which is the size of the transport stream packets) to decrease latency and our buffer size is 64kb.

7.) On the receiving machine you should be able to use vlc, ffmpeg or mplayer to catch the stream. In vlc simply open the Network stream rtp://@:6666 , in ffmpeg you can use the command ffplay -i udp://:6666 or using mplayer you can issue the command mplayer -framedrop -double udp://:6666 .

8.) Now to optionally add sound to the whole thing we can use this command on the encoding machine (instead of step 6). You need to know the device name for your sound card and you probably want to turn the volume down (at least initially) on the decoding machine.

ffmpeg -f dshow  -i video="UScreenCapture" -f dshow -i audio="Stereo Mix (Realtek High Defini" -r 30 -vcodec mpeg4 -q 20 -acodec libmp3lame -ab 128k -f mpegts udp://141.117.224.74:6666?pkt_size=188?buffer_size=65535

• -f dshow specifies that you’re going to be using a directshow device as your input (VIDEO).
• -i video=”UScreenCapture” is the name of the input directshow video device which we picked up in step 5.
• -f dshow specifies that you’re going to be using a directshow device as your input (AUDIO).
• -i audio=”Stereo Mix (Realtek High Defini” is the name of the input directshow audio device which we picked up in step 5.
• -r 30 is the frame rate.
• -vcodec mpeg4 is our video codec of choice.
• -q 20 is a quality measure for the encoding process (1 is the best and 30 the worst). We’re doing VBR encoding so this measures the compression ratio vs. picture quality. I went with 20 instead of 12 from step 6 since the audio encoding slows the machine down a bit.
• -acodec libmp3lame is our video codec of choice
• -f mpegts is our output filetype. In this case mpeg-2 transport stream. Yes, we’re encapsulating mpeg4 video inside a mpeg-2 transport stream…..why?….google it.
• udp://aaa.bbb.ccc.ddd:6666?pkt_size=188?buffer_size=65535 this last bit specifies the address and port number of the recipient machine (aaa.bbb.ccc.ddd is the ip address of that machine and 6666 is my arbitrary port number). We’re also instructing ffmpeg to create smaller 188 byte size udp packets (which is the size of the transport stream packets) to decrease latency and our buffer size is 64kb.

So here is how you take advantage of this. Once you’ve turned on the feature in the preferences panel, you open up Finder. Hold down the “option/alt” key and from the finder menus choose “Go/Library“. This should land you in your not so secret Library directory. You need to hold down the option key to see this, since OSX Lion hides the users Library directory by default. Now in the Finder window find the “Mobile Documents” folder (and if you like) drag it to the favourites list in Finder (in the left pane). Done. Now whatever file you save into “Mobile Documents” folder from any application will “sync” with all the other mac’s you’ve setup with this feature. You can treat it like your “free” 5GB dropbox account.

1. Use a Sharpie marker and sign your name on a plain piece of paper. Make sure it’s a plain sheet of paper with nothing written on either side.
2. Open the Preview App and go to Preferences>Signatures and Press the small + button to add a new signature.
3. A new window will pop up with your webcam video inside.
4. Hold up the paper with your signature in front of the camera and make sure there is enough light in the room for the camera to get a clean image
5. Align the signature — by moving it back and forth — with the blue line and wait for the machine to give you the clean scan of it in the window beside it.
6. Press Enter to accept the signature when you’re ready.

I had to do this twice, but it’s very easy and quick to do. You can even have multiple pics taken of your signatures (or other peoples sig in your household).

1) You now have the ability to select multiple files in a folder and right click on them to choose “New Folder with X Selections”. This will create a new folder and move the selected files into that folder. Kinda neat and makes the process of moving large number of files a bit simpler.

2) You can now “move” files and folders from one place to another. First “copy” the file/folder in question by selecting it and using the command-c shortcut. Then find the place you want to move them to and instead of using the usual command-v (which copies the files/folders) use command-option-v instead. Yeaaaaa, we can finally be just like our windows cousins .

3) To remove something from the finder sidebar, hold the command key as you drag it out.

4) In the Finder’s “Go” menu hold the option key to reveal a “Go to Library” menu item.

Although not strictly a new finder gem, Window resizing now supports standard modifier keys, so holding Shift while resizing a window constrains it to its existing aspect ratio, while holding Option resizes the window from its center point.

The session continues with a demonstration of a potential application to control a small arduino based robot over bluetooth using gestures. Following this the ICAD staff show the use of Kinect as a tracking and control mechanism for a Point-Tilt-Zoom (PTZ) camera. This approach allows them to track up to five people without active trackers. The data from the Kinect camera is used to instruct the PTZ camera where to “look”. Once a person is identified (by putting up their hand) the kinect will try to track the person around the room and make sure the PTZ camera follows the person as well. Switching the tracked person is done by raising ones hand.

Their last demo will show a gestural based keyboard that will eventually be tied into a interactive phonebook application where the user can type the name of a contact using gestures and automatically dial the number through a voip application (ie: google talk).

Individual project videos below….

1) Kinect Windows Mouse Interface

2) Kinect Google Earth Interface

3) Kinect Second Life Interface

4) Kinect Bluetooth Robot Interface

5) Kinect Tracker-Cam Interface

6) Kinect Interactive Phonebook

The Canyons were as awesome as usual. We had a late lunch/dinner and (surprisingly) ended up seeing a lot of wildlife around the place.

Next, we went through NAB, which is always fun. On thursday (last day) we took off around 2:30pm and started our trip around the sierras. We had intended to get to Tonopah, NV by around 18:00′ish, but had a bit of run in with a flying carpet on I-95 North. This thing flew off the back of the pickup (in picture) and shattered/cracked the front windshield. You can see the glass shards on the dashboard. It all turned out okay, we stopped the guy, got his info, went back to the car rental and swapped the van. We got to Tonopah around 21:00 and pretty much had dinner and slept right through the night.

Next day (Friday), we drove up to Mono Lake, CA. One of my favourite places of all time (aside from Yosemite and Bryce NPs). I’d been there before a couple of years ago, but this time there was snow in the mountains and the lake was really calm. Since it was a nice sunny day with lots of puffy clouds in the sky I figured I try my luck with some HDR images, for that “out of this world” look.

We then left Mono Lake and since the Tioga Pass into Yosemite was still closed, we drove all the way up I-395 to Minden, CA. Next morning (Saturday) we left there and headed south-west on I-88 and eventually made it into Yosemite through the west entrance via CA-120.

We left Yosemite and stayed the night in Oakhurst, CA. On Sunday we drove through the foggy Sequoia NP.

We stayed Sunday night in Bakersfield and headed out the next day (Monday) with the intention of visiting the northern parts of Death Valley. We kinda made it down to Baker, CA and decided it might be a wiser idea to drive straight to Vegas (It was really windy and dusty), stay the night and drive back to Death Valley early in the morning. That was a great idea since the next morning was sunny, hot and slightly breazy, but no dust . We drove through the northern part all the way to Scotty’s Castle and drove back to Vegas for the last day of the trip.

As usual the complete flickr set can be found here.

First a sample from our Holiday 2010 shoot (Full flickr set can be viewed here).

Next is the Stroboscopic shoot which was a lot of fun (Full flickr set can be viewed here).

The final set is from a quick get together with a couple of the members to try and produce a sport/jogging commercial photo (Full flickr set can be viewed here).

1. Turn wifi off on your 3GS and ipad device. I’m testing from home so I wanted to make sure I was NOT using wifi.
2. Turn on Bluetooth on both your 3GS and ipad device. This is under Settings/General
3. On the iphone 3GS turn on “Personal Hotspot”.
4. On the ipad go back to the Bluetooth menu and let it scan for a second. You’ll find a Entry for your iPhone soon. Click on the entry and connect.
5. You’ll be prompted on the iphone and the ipad to make sure you see the same code. Just say Okay/Yes.
6. Viola, you’re tethering your ipad to your iphone 3GS using bluetooth. You should see a Blue throbbing menu bar on top of your iphone 3GS saying “Personal Hotspot: 1 Connection”.

To stop turn Personal Hotspot off on the iphone. If you need to connect again, turn Personal Hotspot on (assuming BT is on already) and click on the iPhone entry in the Bluetooth menu on your ipad.

N.B. The iphone can also “share” it’s wifi connection with the ipad using bluetooth. Neato . Oh and that GPS location transfer thing that people are talking about using wifi tethering doesn’t seem to work when using BT…..Oh well, small price to pay.

UPDATE: After a bit of testing here are some numbers. These were done around midnight on Rogers/Fido Network through bluetooth (iphone 3GS on 3G):

• Ping: ~320ms
• Download: 1.53 Mbps
• Upload: 0.23 Mbps

Not bad for bluetooth I guess.

Yep it’s that time of the year again. Mark February 26 & 27 in your calendars…..PODCAMP TORONTO 2011 IS COMING TO TOWN. PodCamp Toronto 2011 is a FREE “unconference” bringing together professionals and hobbyists from Toronto and the surrounding area to explore the cutting edge of new and social media. If you are an online content creator – hobbyist and professionals – who are building communities online in a variety of ways, then PodCamp Toronto 2011 is for you. Share ideas, discuss theories and learn lessons from an audience of experts.

We’ll be at Ryerson University’s flagship centre for studies in converging communications and interactive media — Rogers Communications Centre. In operation for almost twenty years, the Rogers Communications Centre has grown to become Canada’s premier facility for education in digital media communications.

The Rogers Communications Centre is about design and research in a community employing both current and advancing communications technology. These five themes have placed the Rogers Communications Centre among the best educational communication and design facilities internationally.

Just steps away from Yonge Street and the heart of Toronto, the Centre is located at the core of Canada’s electronic media and digital communications culture.

So have you reserved your seat yet? Why the hell not? .

• Backup your system
• Install (and update) the latest XCode (I’ve got version 3)
• Install X11 client stuff from your server install DVD
• install X11 SDK stuff from your server install DVD
• Ensure you have server 10.5.8 (latest update as of Feb.04.2011)
• Make sure you have not tried to install mcrypt using another method. We need a “virgin” 10.5.8 install (as far as homebrew/local installs)
• BACKUP

Please note that this will add mcrypt support to php. This is NOT the same as compiling mcrypt.

Okay, so now that we have all the requirements, you need to get a command line window opened and get a root shell (sudo -i). The rest of this document assumes you’re typing the commands in a root shell.

There is one dependency that we need to clear before we actually get down and dirty and that is libmcrypt. Follow the instructions below to get this installed:

mkdir /SourceCache
cd /SourceCache
curl http://sourceforge.net/projects/mcrypt/files/Libmcrypt/2.5.8/libmcrypt-2.5.8.tar.bz2/download -o libmcrypt-2.5.8.tar.bz2 -L

This is the latest version as of this writing (Feb.04.2011).

NOTE: If you’re compiling on a G5 machine you’ll need to tell the compiler that you want to build/configure for a ppc64 target so instead of the below configure command you need to use this:

MACOSX_DEPLOYMENT_TARGET=10.5 CFLAGS=" -arch ppc64 -g -Os -pipe -no-cpp-precomp" CCFLAGS=" -arch ppc64 -g -Os -pipe" CXXFLAGS="-arch ppc64 -g -Os -pipe" LDFLAGS="-arch ppc64 -bind_at_load" ./configure --enable-shared

tar -xjvf libmcrypt-2.5.8.tar.bz2
cd libmcrypt-2.5.8/
./configure
make
make -n install

The last command will simulate the installation process. Make sure the stuff is getting installed in /usr/local/lib

make install

At this point you should have a working installation of libmcrypt. This next command prints out the current version of your php engine. In my case under 10.5.8 it’s php 5.2.14.

server:libmcrypt-2.5.8 root# php -v
PHP 5.2.14 (cli) (built: Oct  6 2010 16:57:10)
Copyright (c) 1997-2010 The PHP Group
Zend Engine v2.2.0, Copyright (c) 1998-2010 Zend Technologies

Grab the appropriate php-5.2.XX.tar.bz2 file from php.net. I just grabbed the stock PHP 5.2.14, since I wanted a perfect match between my php engine and the extension. I transferred the file using sftp to the /SourceCache folder on the server.

NOTE: If you’re compiling on a G5 machine you’ll need to tell the compiler that you want to build/configure for a ppc64 target so instead of the below configure command you need to use this:

MACOSX_DEPLOYMENT_TARGET=10.5 CFLAGS=" -arch ppc64 -g -Os -pipe -no-cpp-precomp" CCFLAGS=" -arch ppc64 -g -Os -pipe" CXXFLAGS="-arch ppc64  -g -Os -pipe" LDFLAGS=" -arch ppc64  -bind_at_load" ./configure --with-php-config=/Developer/SDKs/MacOSX10.5.sdk/usr/bin/php-config

cd /SourceCache
tar xjvf php-5.2.14.tar.bz2
cd /SourceCache/php-5.2.14/ext/mcrypt
phpize
./configure --with-php-config=/Developer/SDKs/MacOSX10.5.sdk/usr/bin/php-config
make
make test
make -n install

The last command will simulate the installation process. Make sure the stuff is getting installed in /usr/lib/php/extensions/no-debug-non-zts-20060613

make install

Now we need to modify our php.ini file and tell the php5 engine of the availability of this new module. To do this you need to copy php.ini.default to php.ini (in /etc directory). For details of why have a look at this article.

cd /etc
cp php.ini.default php.ini

Edit the newly created/copied php.ini using your favourite editor. Add the following line to the appropriate location (read the comments in the file to find the location):

extension=mcrypt.so

Still in the same file find the variable “extension_dir” and change it’s value to “/usr/lib/php/extensions/no-debug-non-zts-20060613″ path instead of “./”. Save the php.ini and use the following command to see if mcrypt extensions are available:

server:etc root# php -i |grep mcrypt
mcrypt
mcrypt support => enabled
mcrypt.algorithms_dir => no value => no value
mcrypt.modes_dir => no value => no value

Done. Restart Apache service from the server manager (just for the sake of completeness).

• Backup your system
• Install (and update) the latest XCode (I’ve got version 3)
• Install X11 client stuff from your server install DVD
• install X11 SDK stuff from your server install DVD
• Ensure you have server 10.5.8 (latest update as of Feb.04.2011)
• Make sure you have not tried to install GD using another method. We need a “virgin” 10.5.8 install (as far as homebrew/local installs)
• BACKUP

Please note that this will add GD support to php. This is NOT the same as compiling the GD graphics library (libgd).

Okay, so now that we have all the requirements, you need to get a command line window opened and get a root shell (sudo -i). The rest of this document assumes you’re typing the commands in a root shell.

There is one dependency that we need to clear before we actually get down and dirty and that is libjpeg (known as jpegsrc). Follow the instructions below to get this installed:

mkdir /SourceCache
cd /SourceCache
curl -O http://www.ijg.org/files/jpegsrc.v8c.tar.gz

This is the latest version as of this writing (Feb.04.2011).

NOTE: If you’re compiling on a G5 machine you’ll need to tell the compiler that you want to build/configure for a ppc64 target so instead of the below configure command you need to use this:

MACOSX_DEPLOYMENT_TARGET=10.5 CFLAGS=" -arch ppc64 -g -Os -pipe -no-cpp-precomp" CCFLAGS=" -arch ppc64 -g -Os -pipe" CXXFLAGS="-arch ppc64 -g -Os -pipe" LDFLAGS="-arch ppc64 -bind_at_load" ./configure --enable-shared

tar -zxvlf jpegsrc.v8c.tar.gz
cd jpeg-8c/
./configure
make
make test
make -n install

The last command will simulate the installation process. Make sure the stuff is getting installed in /usr/local/lib

make install

At this point you should have a working installation of libjpeg. Now we double check our php version.

server:jpeg-8c root# php -v
PHP 5.2.14 (cli) (built: Oct  6 2010 16:57:10)
Copyright (c) 1997-2010 The PHP Group
Zend Engine v2.2.0, Copyright (c) 1998-2010 Zend Technologies

Notice in the output that I have php 5.2.14 installed on the machine (again the latest update as of Feb.04.2011). Apple does not provide source code for this exact version of PHP. On top of that The numbering scheme that they use is weird. On my machine it is “apache_mod_php-44.6″, you can find yours using the following:

server:jpeg-8c root# php -i |more
phpinfo()
PHP Version => 5.2.14

System => Darwin saturn.rcc.ryerson.ca 9.8.0 Darwin Kernel Version 9.8.0: Wed Ju
l 15 16:55:01 PDT 2009; root:xnu-1228.15.4~1/RELEASE_I386 i386
Build Date => Oct  6 2010 16:55:34
Configure Command =>  '/SourceCache/apache_mod_php/apache_mod_php-44.6/php/confi
gure'  '--prefix=/usr' '--mandir=/usr/share/man' '--infodir=/usr/share/info' '--
disable-dependency-tracking' '--with-apxs2=/usr/sbin/apxs' '--with-ldap=/usr' '-
-with-kerberos=/usr' '--enable-cli' '--with-zlib-dir=/usr' '--enable-trans-sid'
'--with-xml' '--enable-exif' '--enable-ftp' '--enable-mbstring' '--enable-mbrege
x' '--enable-dbx' '--enable-sockets' '--with-iodbc=/usr' '--with-curl=/usr' '--w
ith-config-file-path=/etc' '--sysconfdir=/private/etc' '--with-mysql-sock=/var/m
ysql' '--with-mysqli=/usr/bin/mysql_config' '--with-mysql=/usr' '--with-openssl'
 '--with-xmlrpc' '--with-xsl=/usr' '--without-pear'

The thing you’re looking for (“apache_mod_php-44.6″) is under Configure Command. If you go to the following URL (http://www.opensource.apple.com/source/apache_mod_php/) in your browser (safari, firefox) you’ll soon discover these weird directory names with numbers that don’t match the php versions. Again, as of this writing (Feb.04.2011), I can’t find apache_mod_php-44.6 folder in the listing so I grabbed the nearest numbers apache_mod_php-44.2 which is php 5.2.8…….close enough. It seems to work. Follow the steps below to get the file and compile the GD portion of it. Remember we’re not recompiling the entire php, just the GD plugin portion.

UPDATE: You CAN install the exact version of your PHP’s GD extension. Instead of grabbing the file from Apple, figure out the version of your PHP using “php -v” and grab the appropriate file from php.net instead. I just recompiled the GD portion of PHP 5.2.14, since I wanted a perfect match between my php engine and the extension. The instructions below (except curl which needs to be modified) work.

NOTE: If you’re compiling on a G5 machine you’ll need to tell the compiler that you want to build/configure for a ppc64 target so instead of the below configure command you need to use this:

MACOSX_DEPLOYMENT_TARGET=10.5 CFLAGS=" -arch ppc64 -g -Os -pipe -no-cpp-precomp" CCFLAGS=" -arch ppc64 -g -Os -pipe" CXXFLAGS="-arch ppc64  -g -Os -pipe" LDFLAGS=" -arch ppc64  -bind_at_load" ./configure --with-zlib-dir=/usr --with-jpeg-dir=/usr/local/lib --with-png-dir=/usr/X11R6 --with-freetype-dir=/usr/X11R6 --with-xpm-dir=/usr/X11R6

cd /SourceCache
curl -O http://www.opensource.apple.com/source/apache_mod_php/apache_mod_php-44.2/php-5.2.8.tar.bz2
tar xjvf php-5.2.8.tar.bz2
cd /SourceCache/php-5.2.8/ext/gd
phpize
./configure --with-zlib-dir=/usr --with-jpeg-dir=/usr/local/lib --with-png-dir=/usr/X11R6 --with-freetype- dir=/usr/X11R6 --with-xpm-dir=/usr/X11R6
make
make test
make -n install

The last command will simulate the installation process. Make sure the stuff is getting installed in /usr/lib/php/extensions/no-debug-non-zts-20060613

make install

Now we need to modify our php.ini file and tell the php5 engine of the availability of this new module. To do this you need to copy php.ini.default to php.ini (in /etc directory). For details of why have a look at this article.

cd /etc
cp php.ini.default php.ini

Edit the newly created/copied php.ini using your favourite editor. Add the following line to the appropriate location (read the comments in the file to find the location):

extension=gd.so

Still in the same file find the variable “extension_dir” and change it’s value to “/usr/lib/php/extensions/no-debug-non-zts-20060613″ path instead of “./”. Save the php.ini and use the following command to see if GD extensions are available:

server:etc root# php -i |grep GD
GD Support => enabled
GD Version => bundled (2.0.34 compatible)

Done. Restart Apache service from the server manager (just for the sake of completeness).