So I now own a new machine for a bit more than a week. I've installed leopard and decided to go with mac ports to give it a try instead of using fink.
I kind like mac ports and for the usage I have of such tools, using fink or mac ports doesn't really make a difference. Since I now have a decent machine I decided to have a look and try to participate to some nice open source project, as my new hobby is photography - I've figured I could maybe be useful somewhere in that area. So I started having a few peaks at libopenraw and exempi which are being developed by a friend of mine. The project aims to bring proper support for the raw file format used by camera makers to linux.
So after installing the dev tools and trying to configure and compile, I was able to achieve it for exempi after hub updated the autoconf/automake files and scripts. This helped configure not to fail so early for libopenraw. It now fails with :
checking for jpeglib.h... yes
./configure: line 20023: syntax error near unexpected token `EXEMPI,'
./configure: line 20023: `PKG_CHECK_MODULES(EXEMPI, exempi-2.0 >=
$EXEMPI_REQUIRED)'
Googling does not really help. What I did though was to use another machine which runs 10.4 instead of 10.5 and uses Fink to manage dependencies instead of Mac ports. On that machine I had no issues due to tooling - a few issues at compile time but they where solved. So I now need to figure out if my issues come from 10.5 or mac ports - good thing I get some vacation time next week.
Yesterday I realized I had fucked up my dns data , and wanted to ssh to my box which gave me :
percent_expand: NULL replacement
Which according to google is macports issue :-( I got on my box using my older laptop (the one running 10.3) and fixed the issue, but I'm being annoyed by those issues I'm encountering.
Last issue I had was getting pictures out of my Nokia 73. Launched the bluetooth browser and was unable to connect to my phone. Killed the app and tried to pair the phone and the machine which failed (console.app is empty ) so I might retry tonight after a reboot to see if the first kill didn't leave the bluetooth hardware in a unknown state that prevented the pairing afterwards.
Only thing I'm not complaining too much is civ IV (except that I don't see the point of having 3D graphics for that game, it does not bring much to it.)

Leave a comment