Re: [HACKERS] OS X 7.4 failure

2005-11-21 Thread Jim C. Nasby
On Thu, Nov 17, 2005 at 12:51:47AM -0500, Tom Lane wrote: > "Jim C. Nasby" <[EMAIL PROTECTED]> writes: > > http://pgbuildfarm.org/cgi-bin/show_log.pl?nm=cuckoo&dt=2005-11-15%2023:56:22 > > I took a closer look at this, and noticed something interesting: > > ccache gcc -no-cpp-precomp -O2 -fno-str

Re: [HACKERS] OS X 7.4 failure

2005-11-16 Thread Tom Lane
"Jim C. Nasby" <[EMAIL PROTECTED]> writes: > http://pgbuildfarm.org/cgi-bin/show_log.pl?nm=cuckoo&dt=2005-11-15%2023:56:22 I took a closer look at this, and noticed something interesting: ccache gcc -no-cpp-precomp -O2 -fno-strict-aliasing -g -Wall -Wmissing-prototypes -Wmissing-declarations -b

Re: [HACKERS] OS X 7.4 failure

2005-11-16 Thread Tom Lane
"Jim C. Nasby" <[EMAIL PROTECTED]> writes: > [EMAIL PROTECTED]:13]~/buildfarm/source:39%otool -L `which perl` > /opt/local/bin/perl: > /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current > version 71.1.3) These aren't particularly relevant: you need to look at the shared libr

Re: [HACKERS] OS X 7.4 failure

2005-11-16 Thread Jim C. Nasby
On Wed, Nov 16, 2005 at 11:50:51AM -0500, Tom Lane wrote: > "Jim C. Nasby" <[EMAIL PROTECTED]> writes: > > I do have perl, python, tcl and nls enabled, could one of them > > be trying to pull libssl and libcrypto in for some reason? > > Perhaps --- try "otool -L" (local equivalent of ldd) on them

Re: [HACKERS] OS X 7.4 failure

2005-11-16 Thread Tom Lane
"Jim C. Nasby" <[EMAIL PROTECTED]> writes: > I do have perl, python, tcl and nls enabled, could one of them > be trying to pull libssl and libcrypto in for some reason? Perhaps --- try "otool -L" (local equivalent of ldd) on them to find out. regards, tom lane ---

Re: [HACKERS] OS X 7.4 failure

2005-11-16 Thread Jim C. Nasby
On Tue, Nov 15, 2005 at 10:27:06PM -0600, Jim C. Nasby wrote: > On Tue, Nov 15, 2005 at 11:04:59PM -0500, Tom Lane wrote: > > "Jim C. Nasby" <[EMAIL PROTECTED]> writes: > > > So the recent thread about getting 7.4 compiling on OS X inspired me. > > > But what I can't understand is that I've yanked

Re: [HACKERS] OS X 7.4 failure

2005-11-16 Thread Andrew Dunstan
Tom Lane wrote: Andrew Dunstan <[EMAIL PROTECTED]> writes: Tom Lane wrote: "Jim C. Nasby" <[EMAIL PROTECTED]> writes: So the recent thread about getting 7.4 compiling on OS X inspired me. But what I can't understand is that I've yanked --with-ssl, but it's still looking for l

Re: [HACKERS] OS X 7.4 failure

2005-11-16 Thread Tom Lane
Andrew Dunstan <[EMAIL PROTECTED]> writes: > Tom Lane wrote: >> "Jim C. Nasby" <[EMAIL PROTECTED]> writes: >>> So the recent thread about getting 7.4 compiling on OS X inspired me. >>> But what I can't understand is that I've yanked --with-ssl, but it's >>> still looking for libssl: >> Tad hard to

Re: [HACKERS] OS X 7.4 failure

2005-11-16 Thread Andrew Dunstan
Tom Lane wrote: "Jim C. Nasby" <[EMAIL PROTECTED]> writes: So the recent thread about getting 7.4 compiling on OS X inspired me. But what I can't understand is that I've yanked --with-ssl, but it's still looking for libssl: Tad hard to believe. Maybe you missed a "make distclean" o

Re: [HACKERS] OS X 7.4 failure

2005-11-15 Thread Jim C. Nasby
On Tue, Nov 15, 2005 at 11:04:59PM -0500, Tom Lane wrote: > "Jim C. Nasby" <[EMAIL PROTECTED]> writes: > > So the recent thread about getting 7.4 compiling on OS X inspired me. > > But what I can't understand is that I've yanked --with-ssl, but it's > > still looking for libssl: > > Tad hard to be

Re: [HACKERS] OS X 7.4 failure

2005-11-15 Thread Jim C. Nasby
On Tue, Nov 15, 2005 at 11:04:59PM -0500, Tom Lane wrote: > "Jim C. Nasby" <[EMAIL PROTECTED]> writes: > > So the recent thread about getting 7.4 compiling on OS X inspired me. > > But what I can't understand is that I've yanked --with-ssl, but it's > > still looking for libssl: > > Tad hard to be

Re: [HACKERS] OS X 7.4 failure

2005-11-15 Thread Tom Lane
"Jim C. Nasby" <[EMAIL PROTECTED]> writes: > So the recent thread about getting 7.4 compiling on OS X inspired me. > But what I can't understand is that I've yanked --with-ssl, but it's > still looking for libssl: Tad hard to believe. Maybe you missed a "make distclean" or so? (BTW, the flag is -