On Thu, Jul 12, 2007 at 09:54:28AM -0400, Tom Lane wrote:
> Magnus Hagander <[EMAIL PROTECTED]> writes:
> > 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.
>
> Looks reasonable to me.
Thanks, applied and bac
Magnus Hagander <[EMAIL PROTECTED]> writes:
> 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.
Looks reasonable to me.
regards, tom lane
---(end of broadcast)---
On Wed, Jul 11, 2007 at 01:41:56PM -0400, Tom Lane wrote:
> Magnus Hagander <[EMAIL PROTECTED]> writes:
> > Tom Lane wrote:
> >> Magnus Hagander <[EMAIL PROTECTED]> writes:
> >>> I'm simply using
> >>> AC_CHECK_FUNC([krb5_free_unparsed_name])
> >>> which works fine on unix, but breaks on win32. Bec
Magnus Hagander <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> Magnus Hagander <[EMAIL PROTECTED]> 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
Tom Lane wrote:
> Magnus Hagander <[EMAIL PROTECTED]> 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 w
Magnus Hagander <[EMAIL PROTECTED]> 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 oth
Hi!
I'm trying to write an autoconf macro to figure out if the function
krb5_free_unparsed_name exists (because it exists in MIT but not Heimdal),
to fix a rather nasty bug in our Kerberos implementation.
However, I'm failing :(
I'm simply using
AC_CHECK_FUNC([krb5_free_unparsed_name])
which wo
