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

Re: Regresstion Tests do not find PGLIB directory

From: Emily Carl <emilyac(at)wanet(dot)net>
To: pgsql-bugs(at)postgresql(dot)org
Cc: emilyac(at)seada(dot)com
Subject: Re: Regresstion Tests do not find PGLIB directory
Date: 2001-02-16 21:29:29
Message-ID: 200102162129.NAA10596@sd-hst-1.wanet.net (view raw or flat)
Thread:
Lists: pgsql-bugs
-----BEGIN PGP SIGNED MESSAGE-----


> Emily Carl writes:
> 
> > The output of a src/test/regress/'make runtest' command puts out:
> 
> > installing PL/pgSQL .. createlang: missing required argument PGLIB
> > directory
> > (This is the directory where the interpreter for the procedural
> > language is stored. Traditionally, these are installed in whatever
> > 'lib' directory was specified at configure time.)
> > failed
> > ACTUAL RESULTS OF REGRESSION TEST ARE NOW IN FILE regress.out
> 
> > The src/test/regress/run_check.sh sets PGLIB="$LIBDIR" but I have not
> > been able to figure out how $LIBDIR should have been set, whereas now
> > it seems not to be set.  I have not been able to find any reference to
> > PGLIB
> > in the postgresql documentation.
> 

Peter Eisentraut wrote:

> LIBDIR should be in src/Makefile.global.  What does it say there?
> 

src/Makefile.global contains:

>>POSTGRESDIR= /export/home/postgres/postgresql-7.0.3
>>
>># Where the postgres executables live (changeable by just putting them
>># somewhere else and putting that directory in your shell PATH)
>>BINDIR= $(POSTGRESDIR)/bin
>>
>># Where libpq.a gets installed.  You must put it where your loader will
>># look for it if you wish to use the -lpq convention.  Otherwise you
>># can just put the absolute pathname to the library at the end of your
>># command line.
>>LIBDIR= $(POSTGRESDIR)/lib

Does this definition come in to play in the make done down 
in the src/test/regress directory?  src/test/regress/README 
Instructions state:
" To prepare for regression testing, do "make all" in the regression test
  directory.  This compiles a 'C' program with PostgreSQL extension functions
 ..."

- From what I am seeing, it does not.  I have not added any 
definitions of LD_LIBRARY_PATH or LIBDIR elsewhere such as in the 
/etc/profile file (did make the suggested entry in the /etc/ld.so.conf).

Thomas Lockhart wrote:

>You need to run ldconfig to actually update the shared library database.
>Or reboot, since usually ldconfig is run at boot time.

Did run ldconfig.

>
>Did the instructions mention /etc/ld.so.conf but not ldconfig? Perhaps
>you can suggest where in the docs we can make it clearer, or better yet,
>perhaps you can send patches for the doc/src/sgml/*.sgml files.

Instructions correctly say to run ldconfig after editing /etc/ld.so.conf.
No doc changes on ldconfig are needed.


Emily.
Software Design Associates, Inc.


-----BEGIN PGP SIGNATURE-----
Version: 2.6.2

iQCVAwUBOo2bubqabQcdIDyxAQGuMgP/bnVl4DqZMLEujZnpFp1Ai2ESRHRP32cJ
vT7ArcR+JzVI3ms+hx7joWX60CVW5ViiKmspmv5At8B3+At0o/C1P3tO3SRWRoN0
pOuQMCgiyob6V65wgsol7G1UgdghYRdSN6s8+XEcFpEC1qFaR3o8AGmn3NVfb5sb
dtMOGGobBSY=
=Ul9j
-----END PGP SIGNATURE-----


Responses

pgsql-bugs by date

Next:From: pgsql-bugsDate: 2001-02-17 23:22:36
Subject: No support for int8 sized binary/hex literals
Previous:From: Peter EisentrautDate: 2001-02-16 21:04:37
Subject: Re: Regresstion Tests do not find PGLIB directory

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