That was my fault --- I had a gmime 2.0 version installed in the confusion of all that I was doing last week.
I uninstalled the 2.0 version, compiled 2.1.15 , used the same symlink from /usr/lib/pkconfig to /usr/local/lib/pkcconfig. One think that threw me earlier was that my Postgres install was creating databases with UNICODE encoding which caused some errors. I found somewhere in a mailing list archive that the encoding should be SQL_ASCII, which fixed the problem. Should this be in documentation? Everything is happy now. --- Paul J Stevens <[EMAIL PROTECTED]> wrote: > > > > Brian Neu wrote: > > The compile error is below. I don't know if this > is > > relevant or not, but I had trouble getting gmime > to > > compile, so I just grabbed someone's RPM from -- > well, > > somewhere. > > > ]# rpm -qa |grep gmime > > gmime-2.1.9-5 > > Mmm. Try 2.1.14 or better. I'm not sure when > g_mime_shutdown appeared, but I'm > tracking gmime pretty closely, and I use the > cvs.gnome.org for documentation a > lot. It's a fast moving target. > > > > -- > > ________________________________________________________________ > Paul Stevens > mailto:[EMAIL PROTECTED] > NET FACILITIES GROUP PGP: > finger [EMAIL PROTECTED] > The > Netherlands________________________________http://www.nfg.nl > _______________________________________________ > Dbmail-dev mailing list > Dbmail-dev@dbmail.org > http://twister.fastxs.net/mailman/listinfo/dbmail-dev >
