--- aaron g [EMAIL PROTECTED] wrote:
I do beleive the OpenSSL library has moved to a new
default
location. I could be wrong.
- aarong
--
I don't think it has been moved as of yestersday.
Regards,
shizuka# ls -al /usr/include/openssl/ssl.h
-r--r--r-- 1 root wheel 60914 Jun 9 02:30
On Mon, Jun 10, 2002 at 02:52:02AM -0700, Shizuka Kudo wrote:
--- aaron g [EMAIL PROTECTED] wrote:
I do beleive the OpenSSL library has moved to a new
default
location. I could be wrong.
- aarong
--
I don't think it has been moved as of yestersday.
OpenSSL has not moved (and
On Wed, Jun 05, 2002 at 04:35:40AM -0700, Shizuka Kudo wrote:
snip/
checking for readline/readline.h... no
checking for readline.h... no
checking for readline/history.h... no
checking for history.h... no
checking for openssl/ssl.h... no
configure: error: header file openssl/ssl.h is
Stanislav Grozev wrote:
actually that is a problem with the autoconf version used by postgresql.
the new gcc 3.1 gives out a warning if one of the system include directories
is also given as a -I argument (in this case -I/usr/include).
the autoconf, when compiling the test program, mistakenly
On Mon, Jun 10, 2002 at 07:02:14AM -0700, Terry Lambert wrote:
Stanislav Grozev wrote:
That's ugly.
well, i _did_ mention that it's a messy and a temporary solution,
but at least it gets postgresql (and many others) to compile and run
fine.
Since it's jamming in includes anyway:
On Mon, Jun 10, 2002 at 07:02:14AM -0700, Terry Lambert wrote:
one messy and temporary solution is to compile with
make CFLAGS=-Wp,-w CXXFLAGS=-Wp,-w
which tells gcc to pass -w to the preprocessor, and -w means inhibit
all warnings. with this, postgresql compiles and works fine.
for
--- David O'Brien [EMAIL PROTECTED] wrote:
*sigh*, why not a *real* fix?
--- configure.in.orig Thu Sep 27 01:03:56 2001
+++ configure.in Mon Apr 29 13:20:27 2002
@@ -200,7 +200,9 @@
done
if test $ac_found_openssl_lib_dir != no;
then
echo found in
David O'Brien wrote:
*sigh*, why not a *real* fix?
Feel free to submit this to the Postgres project... they may
even incorporate it.
You'll note that they bother with this kind of check for other headers,
but for some reason didn't consider it for openssl headers.
Mostly the reason that
Shizuka Kudo wrote:
--- David O'Brien [EMAIL PROTECTED] wrote:
*sigh*, why not a *real* fix?
[ ... ]
Which version of postgresql that you are using? I have
cvsupped the postgresql7 ports and didn't find what
you referred here. However, I didn't manage to patch
configure not to
--- Terry Lambert [EMAIL PROTECTED] wrote:
Shizuka Kudo wrote:
--- David O'Brien [EMAIL PROTECTED] wrote:
*sigh*, why not a *real* fix?
[ ... ]
Which version of postgresql that you are using? I
have
cvsupped the postgresql7 ports and didn't find
what
you referred here.
Shizuka Kudo wrote:
I don't think autoconf was called in postgresql7 port,
and patching configure is necessary.
It's derived data, and the patches will likely not remain valid
after the next release/upgrade. That basically means that the
way to correct your complaint about autoconf not being
I do beleive the OpenSSL library has moved to a new default
location. I could be wrong.
- aarong
--
___
Download the free Opera browser at http://www.opera.com/
Powered by Outblaze
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe
--- Alfred Perlstein [EMAIL PROTECTED] wrote:
Getting a traceback to both us (FreeBSD) and the
Postgresql
developers would be very helpful.
Alfred,
Today, I rebuilt -current postgresql with latest
cvsup, the core dump did not occurred. However, I
still have to specify WITHOUT_SSL=yes.
Hi,
I cvsupped my current and rebuilt the system about an
hours ago. After that I rebuilt the postgresql7 port.
First, it failed with
problem finding openssl/ssl.h and I had to build
with WITHOUT_SSL=yes. It finally built, but the new
postgres core dumpped when running initdb command.
I have to
14 matches
Mail list logo
