Skip Navigational Links
LISTSERV email list manager
LISTSERV - COMMUNITY.EMAILOGY.COM
LISTSERV Menu
Log In
Log In
LISTSERV 17.5 Help - LSTSRV-L Archives
LISTSERV Archives
LISTSERV Archives
Search Archives
Search Archives
Register
Register
Log In
Log In

LSTSRV-L Archives

LISTSERV Site Administrators' Forum

LSTSRV-L

Menu
LISTSERV Archives LISTSERV Archives
LSTSRV-L Home LSTSRV-L Home

Log In Log In
Register Register

Subscribe or Unsubscribe Subscribe or Unsubscribe

Search Archives Search Archives
Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
Re: Compiling Listserv 15.0
From:
Liam Kelly <[log in to unmask]>
Reply To:
LISTSERV site administrators' forum <[log in to unmask]>
Date:
Mon, 4 Dec 2006 11:02:55 -0500
Content-Type:
TEXT/PLAIN
Parts/Attachments:
TEXT/PLAIN (32 lines)
> I have successfully compiled with LD_LIBRARY_PATH set to include the
> unixODBC and gnu libraries but when running lsv_amin (and I assume
> the other binaries) as the listserv user--who does not have that env
> variable set--I get a fatal error as the library cannot be located.
> ldd indicates as much when LD_LIB_PATH is unset:
> 	libodbc.so.1 =>         (file not found)
>          libgcc_s.so.1 =>         (file not found)

There isn't any need to have lsv_amin linked against the ODBC libraries.
I would recommend unsetting the ODBC flag in the makefile and rebuilding a
new lsv_amin ('make lsv_amin') or just doing 'gcc -o lsv_amin lsv_amin.c'.

As for the LD_LIBRARY_PATH, if you want LISTSERV to use ODBC, you're going
to have to tell the dynamic linker where to find the libraries, which
means that you either need to add the library path on a system-wide basis,
or you need to at least add it for the 'listserv' user.  The quick way to
do so would be to export it from go.user, which sets the other environment
variables for LISTSERV.  Note that this will afffect the main 'lsv'
process and sub-processes, but *not* lsv_amin (which isn't spawned by lsv
and doesn't read go.user).

-- 
Liam Kelly
Senior Consulting Analyst
L-Soft international
[log in to unmask]


------------------------------------
Interested in other L-Soft products?  See what else we have
to offer here <http://www.lsoft.com/products/products.asp>

ATOM RSS1 RSS2

COMMUNITY.EMAILOGY.COM CataList Email List Search Powered by LISTSERV