The compiler warnings in mm_blocknotify() are completely harmless.
For various reasons, a small value (which originates as an int) is
transported as a void*, and an explicit cast is used so the compiler
should not be issuing a warning even though the sizes are different.
The value carried is so small that it doesn't matter what truncation
happens; it will always fit.
However, it is a known issue that UW IMAP generally will not compile to a
good binary in 64-bit mode. There are other issues, such as the I/O calls
used, which need to be resolved prior to using 64-bit mode. Also, I
suspect that not all pointers are 64-bits in a 64-bit mode compile.
Thus you are correct; it is necessary to compile UW IMAP in 32-bit mode.
There is no particular advantage to having imapd run in 64-bit mode (other
than, perhaps, a cosmetic one).
-- Mark --
http://staff.washington.edu/mrc
Science does not emerge from voting, party politics, or public debate.
Si vis pacem, para bellum.
_______________________________________________
Imap-uw mailing list
[email protected]
https://mailman1.u.washington.edu/mailman/listinfo/imap-uw
