dbTalk Databases Forums  

Re: [BUGS] [PATCHES] BUG #2600: dblink compile with SSL missing libraries

mailing.database.pgsql-bugs mailing.database.pgsql-bugs


Discuss Re: [BUGS] [PATCHES] BUG #2600: dblink compile with SSL missing libraries in the mailing.database.pgsql-bugs forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Albe Laurenz
 
Posts: n/a

Default Re: [BUGS] [PATCHES] BUG #2600: dblink compile with SSL missing libraries - 09-07-2006 , 10:46 AM






Chris Browne wrote:
Quote:
I also seem to recall, in past discussions about "library matters,"
that AIX is more sticky about requiring that libraries be named
expressly.

ecpglib has

SHLIB_LINK =3D -L../pgtypeslib -lpgtypes $(libpq) \
$(filter -lintl -lssl -lcrypto -lkrb5 -lcrypt -lm, $(LIBS))=20
$(PTHREAD_LIBS)

ifeq ($(PORTNAME), win32)
# Link to shfolder.dll instead of shell32.dll
SHLIB_LINK +=3D -lshfolder
endif

Presumably the same would be necessary everywhere else libpq is used.
=20
I replaced:
SHLIB_LINK =3D $(libpq)
=20
with
SHLIB_LINK =3D $(libpq) $(LIBS)
=20
which allowed the compile to get through this.
Do you build static or dynamic?
What is the output of 'ldd psql'?

I am wondering because I had similar problems building on AIX (5.3)
before I told the linker to look for libpq.so BEFORE libpq.a
by giving it LDFLAGS=3D"-Wl,-bdynamic,-brtl" (using gcc).

This is just a thought - triggered by your remark that 'AIX is more
sticky about requiring that libraries be named expressly'.
Because in a static build you'd have to specify all the libraries
whenever you link.

Yours,
Laurenz Albe

---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend


Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.