[Dovecot] Checking for strtoumax and strtoimax

older
[Dovecot] allow_nets overridden by...

J Springer

31 Dec 2008 31 Dec '08

3:13 a.m.

Tru64 5.1b PK6 : dovecot 1.1.7 : cc

Configuration checks for strtoumax and strtoimax are positive but both are unresolved during compilation. strtoq and strtouq checks are negative.

I can modify compat.c to use "unsigned long ret = 0;" in place of strtoumax (does this break anything?) and/but I would like to know how to handle strtoimax.

Thanks in advance.

Show replies by date

Timo Sirainen

31 Dec 31 Dec

3:21 a.m.

On Dec 31, 2008, at 2:13 AM, J Springer wrote:

...

Tru64 5.1b PK6 : dovecot 1.1.7 : cc

Configuration checks for strtoumax and strtoimax are positive but
both are unresolved during compilation. strtoq and strtouq checks are negative.

In what header file are strtoumax and strtoimax declared? How are they
declared? (grep -r strtoumax /usr/include) Perhaps you'd just need to
link with some extra library to be able to use them.

...

I can modify compat.c to use "unsigned long ret = 0;" in place of
strtoumax (does this break anything?)

That'd work.

...

and/but I would like to know how to handle strtoimax.

If you're not using quota plugin you won't need it. If you're going to
use quota plugin it would have to be implemented somehow..

J Springer

4:46 a.m.

...

They're not declared at all which was why I was puzzled at the positive check.

...

Quota won't be used. Any problem with just removing that section from compat.c?

Timo Sirainen

11:13 a.m.

On Dec 31, 2008, at 3:46 AM, J Springer wrote:

...

It shows in config.log why exactly it thought they were working.
Copy&paste those parts of it?

...

You shouldn't need to remove anything, since the default
implementation is i_panic().

Actually easiest way for you would probably to just remove the
HAVE_STRTOIMAX and HAVE_STRTOUMAX from config.h.in and config.h
without modifying compat.c at all.

J Springer

7:28 p.m.

...

It shows in config.log why exactly it thought they were working. Copy&paste those parts of it?

configure:23169: checking for strtoimax configure:23196: cc -c -g conftest.c >&5 configure:23202: $? = 0 configure:23213: result: yes configure:23228: checking for strtoumax configure:23255: cc -c -g conftest.c >&5 configure:23261: $? = 0 configure:23272: result: yes

I am running the bash shell and I have found where bash compiles in definitions for strtoimax and strtoumax. So, even if the shell is changed, the environmental variable for the shell is not. Could this be the problem?

...

Yes, this works, as well. At this point I realize that it is a system and/or shell problem and not a dovecot problem. Is there a work around (not that you need more work) or do I just need to remember to undefine these for the Tru64 systems that I still support?