PHWinfo - Afficher un message - UW imap-2006b: 64 bit problem

13/10/2006, 00h16

Mark Crispin wrote:
> In general, 64-bit builds are untested and not recommended in UW imapd.

> There is generally not much benefit to a 64-bit build.

Yes, I know. But since I do not want to package each SW twice, and some SW
really benefits from 64bit, but unfortunately one can't mix 32 and 64bit
objects/libs, I decided to make all packages 64bit, only.

> Solaris is SVR4 based,
> which is not a recommended platform due to its deficiencies (Linux and
> BSD are recommended platforms).

Well, have not really a choice ;-)

> However, there may be a simple explanation and fix for your problem.
>
> By default, Solaris builds use IPv4 only code. If getsockname() returns
> an IPv6 socket, that would cause the -1 port that you experienced.
>
> Try adding IP=6 to your make command (you'll need to "make clean"
> first). That'll select the IPv6 code which is also IPv4 savvy.
>
> That may be the magic bullet that solves the problem.

No - same problem. Must be something different...
BTW: What is the easiest way to programatically enable the tcbdebug
stuff, so that I can do some "printf" debugging, when I find the time
for it ?

Regards,
jens.

13/10/2006, 00h16	#3
Jens Elkner Messages: n/a Hébergeur:	Re: UW imap-2006b: 64 bit problem Mark Crispin wrote: > In general, 64-bit builds are untested and not recommended in UW imapd. > There is generally not much benefit to a 64-bit build. Yes, I know. But since I do not want to package each SW twice, and some SW really benefits from 64bit, but unfortunately one can't mix 32 and 64bit objects/libs, I decided to make all packages 64bit, only. > Solaris is SVR4 based, > which is not a recommended platform due to its deficiencies (Linux and > BSD are recommended platforms). Well, have not really a choice ;-) > However, there may be a simple explanation and fix for your problem. > > By default, Solaris builds use IPv4 only code. If getsockname() returns > an IPv6 socket, that would cause the -1 port that you experienced. > > Try adding IP=6 to your make command (you'll need to "make clean" > first). That'll select the IPv6 code which is also IPv4 savvy. > > That may be the magic bullet that solves the problem. No - same problem. Must be something different... BTW: What is the easiest way to programatically enable the tcbdebug stuff, so that I can do some "printf" debugging, when I find the time for it ? Regards, jens.