Spent all afternoon compiling Gaim

Under a whim, I decided that Copland Community Preview should have the latest version of Gaim. After all, the old 1.5 version doesn't really work anymore (maybe it does, but not well!), and I successfully built Beta 6 on my Dapper system. It works a treat.

So, I put the iMac back into the chroot and copied over the Gaim source code. Then I did a ./configure. After about 5 minutes of configuring, it complained about a build dependency. I downloaded it. Another 5 minute configure later, it complained about another build dep. I got it. A 6 minute configure later, it complained about yet another build-dep - this one was a multiple dependency, took up 14 megabytes.

Then finally the configure step completed, and I ran make. About half an hour later, make gave me an error about incorrect ELF files. Then I realised - I had compiled Gaim beta on the x86 before, put the folder with its x86 binaries on the PowerPC, and hadn't done a make clean.

So I did a make clean to get rid of all the x86-compiled stuff. 8 minutes of configure later, I ran make. An hour afterward, make finally finished. Aptitude purge gaim. Sudo checkinstall. It all went okay. So I worked on some other Copland stuff for a little while, had a long break, made a new desktop entry (calling it "Pidgin") and an updated About box picture, deleted all the build-deps for Gaim, then built the CD image.

It's 9:45 pm. I run the disc, and debug the xorg-profiles code. Now I'm at a desktop. I set up my internet connection, start Gaim, and input my MSN details... to find that Gaim won't connect because I don't have the right SSL libraries installed into Copland. Furthermore, I find that the SSL development libraries were needed at compile time. Doh!

Luckily, I did keep a copy of the /var/apt/cache directory, so I probably have all the build dependencies for Gaim. But they are there as debs, which I must now install manually in the correct order into the chroot. Then compile Gaim again. Lucky me. Lucky little me.

And I was planning to probably release this disc image! It certainly won't happen now, until these bugs get ironed out - and then I'll have the fun of migrating to Feisty's base with the same problems! But no, I will release an Edgy-based disc image.