BF Failure on Bandicoot

Bandicoot is currently failing on HEAD with the following error shown in
a message box during make check:

---------------------------
postgres.exe - Entry Point Not Found
---------------------------
The procedure entry point ldap_start_tls_sA could not be located in the
dynamic link library wldap32.dll.
---------------------------
OK
---------------------------

The failure hangs up the build farm run so it doesn't report back. It
appears to occur in initdb, which subsequently cannot be killed :-(

Regards, Dave.

Hi All

I am looking for a C/C++ library which can talk to postgresql/postgis other
than libpqxx!!

thanx in advance

sandeep

Ühel kenal päeval, R, 2006-07-21 kell 17:14, kirjutas Sandeep
Jakkaraju(Navolve):
> Hi All
>
>
> I am looking for a C/C++ library which can talk to postgresql/postgis
> other than libpqxx!!

Why ?

> thanx in advance
>
> sandeep
--
----------------
Hannu Krosing
Database Architect
Skype Technologies OÜ
Akadeemia tee 21 F, Tallinn, 12618, Estonia

Skype me: callto:hkrosing
Get Skype for free: http://www.skype.com

"Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> writes:
> Bandicoot is currently failing on HEAD with the following error shown in
> a message box during make check:

> The procedure entry point ldap_start_tls_sA could not be located in the
> dynamic link library wldap32.dll.

Just guessing from the function name, but does this go away if you don't
configure --with-ldap?

If so it's presumably a portability issue in this recent patch:

2006-03-06 12:41 momjian

* configure, configure.in, src/backend/libpq/auth.c,
src/backend/libpq/hba.c, src/backend/libpq/pg_hba.conf.sample,
src/include/pg_config.h.in, src/include/libpq/hba.h: This patch
adds native LDAP auth, for those platforms that don't have PAM
(such as Win32, but also unixen without PAM). On Unix, uses
OpenLDAP. On win32, uses the builin WinLDAP library.

Magnus Hagander

I'd counsel just leaving --with-ldap off until Magnus gets back from
vacation. We can always revert the patch later if he can't fix it.
(There's some fairly ugly stuff going on at lines 69-89 of
backend/libpq/auth.c, which I bet is the root of the trouble, but
I'm not going to dig further --- I've wasted more than enough time
on Windows this week ;-))

regards, tom lane

> -----Original Message-----
> From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
> Sent: 21 July 2006 15:20
> To: Dave Page
> Cc: pgsql-hackers(at)postgresql(dot)org
> Subject: Re: [HACKERS] BF Failure on Bandicoot
>
> "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> writes:
> > Bandicoot is currently failing on HEAD with the following
> error shown in
> > a message box during make check:
>
> > The procedure entry point ldap_start_tls_sA could not be
> located in the
> > dynamic link library wldap32.dll.
>
> Just guessing from the function name, but does this go away
> if you don't
> configure --with-ldap?
>
> If so it's presumably a portability issue in this recent patch:
>
> 2006-03-06 12:41 momjian
>
> * configure, configure.in, src/backend/libpq/auth.c,
> src/backend/libpq/hba.c, src/backend/libpq/pg_hba.conf.sample,
> src/include/pg_config.h.in, src/include/libpq/hba.h: This patch
> adds native LDAP auth, for those platforms that don't have PAM
> (such as Win32, but also unixen without PAM). On Unix, uses
> OpenLDAP. On win32, uses the builin WinLDAP library.
>
> Magnus Hagander
>
> I'd counsel just leaving --with-ldap off until Magnus gets back from
> vacation. We can always revert the patch later if he can't fix it.
> (There's some fairly ugly stuff going on at lines 69-89 of
> backend/libpq/auth.c, which I bet is the root of the trouble, but
> I'm not going to dig further --- I've wasted more than enough time
> on Windows this week ;-))

Yeah, I spotted that ugliness. I'll turn it off for now, and CC this to
Magnus so he has no excuse for forgetting :-p

Regards, Dave.

> Just guessing from the function name, but does this go away if you
> don't configure --with-ldap?
>
> If so it's presumably a portability issue in this recent patch:
>
> 2006-03-06 12:41 momjian
>
> * configure, configure.in, src/backend/libpq/auth.c,
> src/backend/libpq/hba.c,
> src/backend/libpq/pg_hba.conf.sample,
> src/include/pg_config.h.in, src/include/libpq/hba.h: This
> patch
> adds native LDAP auth, for those platforms that don't have
> PAM
> (such as Win32, but also unixen without PAM). On Unix, uses
> OpenLDAP. On win32, uses the builin WinLDAP library.
>
> Magnus Hagander
>
> I'd counsel just leaving --with-ldap off until Magnus gets back
> from vacation. We can always revert the patch later if he can't
> fix it.
> (There's some fairly ugly stuff going on at lines 69-89 of
> backend/libpq/auth.c, which I bet is the root of the trouble, but
> I'm not going to dig further --- I've wasted more than enough time
> on Windows this week ;-))

Looking at the MSDN documentation it seems this function only exists on
Windows 2003 and Windows XP. Which is very interesting, because I have
it working on one of my 2000 boxes. But I guess I got it through some
patch or other.

I'm going to have to redo it to dynamically load that function and exit
with a proper error message if it's not found. Shouldn't be too hard,
I'll get to it as soon as I can get down for a coding session.

The ugly stuff I assume is the stuff about the mingw broken headers? If
so, no, not related in any way.

//Magnus

> > Just guessing from the function name, but does this go away if you
> > don't configure --with-ldap?
> >
> > If so it's presumably a portability issue in this recent patch:
> >
> > 2006-03-06 12:41 momjian
> >
> > * configure, configure.in, src/backend/libpq/auth.c,
> > src/backend/libpq/hba.c,
> > src/backend/libpq/pg_hba.conf.sample,
> > src/include/pg_config.h.in, src/include/libpq/hba.h: This patch
> > adds native LDAP auth, for those platforms that don't have PAM
> > (such as Win32, but also unixen without PAM). On Unix, uses
> > OpenLDAP. On win32, uses the builin WinLDAP library.
> >
> > Magnus Hagander
> >
> > I'd counsel just leaving --with-ldap off until Magnus gets
> back from
> > vacation. We can always revert the patch later if he can't fix it.
> > (There's some fairly ugly stuff going on at lines 69-89 of
> > backend/libpq/auth.c, which I bet is the root of the
> trouble, but I'm
> > not going to dig further --- I've wasted more than enough time on
> > Windows this week ;-))

Attached is a patch that fixes this issue at least in my test machine
(yes, I found one 2000 machine that was broken as well)

//Magnus

"Magnus Hagander" <mha(at)sollentuna(dot)net> writes:
> Attached is a patch that fixes this issue at least in my test machine
> (yes, I found one 2000 machine that was broken as well)

Applied. Dave, would you re-enable the LDAP option on bandicoot so
we can verify this fixes it?

regards, tom lane

> -----Original Message-----
> From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
> Sent: 21 August 2006 20:24
> To: pgsql-hackers(at)postgresql(dot)org; Magnus Hagander
> Cc: Dave Page; pgsql-patches(at)postgresql(dot)org
> Subject: Re: [PATCHES] [HACKERS] BF Failure on Bandicoot
>
> "Magnus Hagander" <mha(at)sollentuna(dot)net> writes:
> > Attached is a patch that fixes this issue at least in my
> test machine
> > (yes, I found one 2000 machine that was broken as well)
>
> Applied. Dave, would you re-enable the LDAP option on bandicoot so
> we can verify this fixes it?

Done. I think the next run is in a few hours on that box.

Regards, Dave.