Skip site navigation (1) Skip section navigation (2)

Re: Problem configuring pgadmin3

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "Adam H(dot) Pendleton" <fmonkey(at)fmonkey(dot)net>
Cc: "Pauly" <adsl490440(at)tiscali(dot)nl>, <pgadmin-support(at)postgresql(dot)org>
Subject: Re: Problem configuring pgadmin3
Date: 2004-07-27 14:56:32
Message-ID: E7F85A1B5FF8D44C8A1AF6885BC9A0E41A748E@ratbert.vale-housing.co.uk (view raw or flat)
Thread:
Lists: pgadmin-support
 

> -----Original Message-----
> From: Adam H. Pendleton [mailto:fmonkey(at)fmonkey(dot)net] 
> Sent: 27 July 2004 15:43
> To: Dave Page
> Cc: Pauly; pgadmin-support(at)postgresql(dot)org
> Subject: Re: [pgadmin-support] Problem configuring pgadmin3
> 
> 
> >
> > Adam; is there any reason why ssl is needed to detect 
> libpq, even if 
> > we are configuring without ssl support?
> 
> No, no reason, really, except that without the flag the 
> configure script failed on some of our developers machines.  
> What I would recommend is adding a --with-ssl option to our 
> configure script.  How does that sound?

I thought we already had one, but of course, we simply rely on libpq to
have it or not.

Can we keep it automated, but first check for the existance of libpq
regardless of ssl, and then check to see whether it has ssl support or
not and define SSL appropriately?

Regards, Dave.

pgadmin-support by date

Next:From: Duane WinnerDate: 2004-07-27 17:46:47
Subject: Re: pgadmin3 on freebsd
Previous:From: Adam H.PendletonDate: 2004-07-27 14:42:45
Subject: Re: Problem configuring pgadmin3

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group