On Wed, Jul 11, 2007 at 01:41:56PM -0400, Tom Lane wrote:
> Magnus Hagander <magnus@hagander.net> writes:
> > Tom Lane wrote:
> >> Magnus Hagander <magnus@hagander.net> writes:
> >>> I'm simply using
> >>> AC_CHECK_FUNC([krb5_free_unparsed_name])
> >>> which works fine on unix, but breaks on win32. Because autoconf tries the
> >>> function with no parameters, which doesn't work due to win32 decorations.
> >>
> >> Doesn't work why? We have dozens of other functions we check for
> >> without needing any special windoze hacks. Is it a macro?
>
> > No, it actually depends on how the library is compiled. Functions can
> > either be exported decorated or not. This one is exported decorated.
>
> It's still not apparent to me how this function is different from every
> other one we check for; but I'd suggest you write a check that looks
> like the ones we use for functions that might be macros, eg sigsetjmp.
Thanks for the pointer. Attached is what I came up with. If someone
autoconfy can sign off on that it seems correct, I'll apply that.
(It passes my tests on both linux and win32 now..)
//Magnus
