No, it is perfectly right. But I would bet, from your screen
dump, that you still have an older (pre-1.1.2) version lying
somewhere on your system and being linked against... What is
the result of this, under bash (I assumed you had a
glibc-based system)?
ls -l $(dirname $(gcc -Wl,-t $(imlib2-config --libs) 2>&1 | sed -n '/Imlib2/{s/.*(\(.*\))/\1/;p}'))/libImlib2*
I ran all imlib2-1.2.0.xxx version, as I am keeping myself up
to date on cvs, and I never experienced this... If we cannot
find the problem from previous suggestions, I am ready to
investigate things further, but we will need to set up
something privately. Just drop me an email if you are
interested (syfou@users.sourceforge.net).