On 28-01-14 20:40, KT Walrus wrote:
>> http://access.thelounge.net/harry/gmime-2.6.19-1.fc19.20140115.rh.src.rpm
>
> I got exactly the same errors in the build:
>
> .../gmime/.libs/libgmime-2.6.so: undefined reference to `g_mutex_init'
> .../gmime/.libs/libgmime-2.6.so: undefined reference to `g_mutex_clear’
>
> A quick Google search seems to indicate that these were introduced in glibc
> after the version that Redhat 6 uses. Looking at the gmime source for 2.5.3
> and 2.6.19, it looks like gmime didn’t use mutexes in the older version so I
> removed the g_mutex calls in the 2.6.19 source and it built fine.
>
> Does dbmail need gmime to be re-entrant/thread safe?
You are probably better off compiling glib. I did so for CentOS-5:
glib-2.37.5
gmime-2.6.17
libevent-2.0.21
libzdb-2.12
compiling these myself for CentOS-5 gave me a stable platform for
dbmail-3.1 and beyond.
DBMail does not require gmime to be thread-safe. I've never counted on
it being so since Jeff clearly stated gmime probably wasn't. But I've
also always been more than a bit suspicious about memory leaks occurring
because gmime isn't/wasn't thread-safe. So if Jeff decided that gmime is
better off with mutexes to make it thread-safe I wouldn't bet against it.
--
________________________________________________________________
Paul J Stevens pjstevns @ gmail, twitter, github, linkedin
* Premium Hosting Services and Web Application Consultancy *
www.nfg.nl/[email protected]/+31.85.877.99.97
________________________________________________________________
_______________________________________________
DBmail mailing list
[email protected]
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
