On Wed, 2008-12-31 at 10:28 -0600, J Springer wrote:
> > 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:
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
On Dec 31, 2008, at 3:46 AM, J Springer wrote:
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.
They're not declared at all which was why I was pu
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.
They're not declared at all which was why I was puzzled at the positive check.
and/but I would like
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
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
