Re: [GENERAL] Errors while installing PostGIS by an unusual method
Hi Ankit, Can you please share the generated config.log ? Following works for me i.e. > export > PATH=/work/postgresql/inst/bin:/opt/proj-4.7.0/inst/bin:/opt/gdal-1.9.1/inst/bin:/opt/geos-3.3.5/inst/bin:$PATH > export > LD_LIBRARY_PATH=/work/postgresql/inst/lib:/opt/proj-4.7.0/inst/lib:/opt/gdal-1.9.1/inst/lib:/opt/geos-3.3.5/inst/lib:$LD_LIBRARY_PATH ./configure --prefix=$PWD/inst --with-projdir=/opt/proj-4.7.0/inst &> > configure.log > make &> make.log Regards, Muhammad Asif Naeem On Mon, Oct 24, 2016 at 11:15 AM, Ankit Sablok wrote: > I am trying to install PostGIS on a RHEL_5 system and failing at it > miserably. The way I am trying to install it is as follows. I copy over all > the artifacts of postgresql server as in the bin, lib, share directories of > postgresql server in a directory called pgql and I place it in the root > directory i.e /pgsql is the directory which contains things like pg_config > and all the other libs and bins that one gets by installing postgresql > using the standard installation. All the dependencies of PostGIS get > installed successfully using the standard build process of *./configure > --prefix=/pgsql, make and make install* but when I issue the following > command for building PostGIS using the same process : > > ./configure --with-gdalconfig=/pgsql/bin/gdal-config > --with-geosconfig=/pgsql/bin/geos-config --with-projdir=/pgsql > --with-jsondir=/pgsql --with-pgconfig=/pgsql/bin/pg_config > > I get the following error in the configure step : > > checking PostgreSQL version... PostgreSQL 9.6 > > checking libpq-fe.h usability... no > > checking libpq-fe.h presence... no > > checking for libpq-fe.h... no > > configure: error: could not find libpq-fe.h" > > to remedy this error I tried placing the include files in the include > directory of postgresql by find the appropriate path using > > /pgsql/bin/pg_config --includedir > > and then when I try to install PostGIS, it still fails. Can anyone suggest > some workaround to build PostGIS using this non-standard approach of > building PostGIS? > > Edit: When I try to add all the include files which includes the > libpq-fe.h and libpq headers as well along with other header I get the > following error when configuring PostGIS > > checking for PQserverVersion in -lpq... no > > configure: error: could not find libpq > > > >
Re: [GENERAL] postgresql-9.5.3 compilation on Solaris SPARC
Hi Venkata,
I have't work on solaris sparc system since long but I would like to share
my feedback on this, I hope it might be useful.
On Fri, May 20, 2016 at 10:14 AM, Venkata Balaji N
wrote:
> Hi,
>
> "make" command is generating the following error while compiling
> postgresql-9.5.3 on Solaris SPARC.
>
While working with PG, gmake is more appropriate then make that have
different implementation on different vendor OS.
> I tried compiling 9.2 and 9.3, works fine. This is only happening on 9.5.
>
> ../../src/port/libpgport_srv.a ../../src/common/libpgcommon_srv.a -lnsl
> -lrt -lsocket -lm -o postgres
>
> Undefined first referenced
>
> symbol in file
>
> atomic_cas_64 port/atomics.o
>
> atomic_cas_32 port/atomics.o
>
> ld: fatal: Symbol referencing errors. No output written to postgres
>
> make[2]: *** [postgres] Error 1
>
> make[2]: Leaving directory `/opt/postgresql-9.5.3/src/backend'
>
> make[1]: *** [all-backend-recurse] Error 2
>
> make[1]: Leaving directory `/opt/postgresql-9.5.3/src'
>
> make: *** [all-src-recurse] Error 2
>
Humm .. Interesting. atomic_cas_64 seems suppose to part of standard c
library. There might be something wrong with the configuration. Probably
check "nm libc.so.1 | grep atomic_cas_64".
Any help would be appreciated. Do i need to give any particular CFLAGS ?
>
>
> Below is the *configure *command -
>
>
> ./configure --prefix=/opt/postgres/9.5.3 CC=/opt/SUNWspro/bin/cc
> 'CFLAGS=-xO3 -xarch=v9 -xspace -W0,-Lt -W2,-Rcond_elim -Xa -xildoff
> -xc99=none -xCC' --enable-cassert --without-readline --enable-thread-safety
> LDFLAGS='-L/usr/lib/sparcv9 -L/usr/ucblib/sparcv9'
>
AFAIR I deprived use of -xarch=v9 and used -m64 instead. I wonder why are
you using LDFLAGS='-L/usr/lib/sparcv9 -L/usr/ucblib/sparcv9', when you
provide -xarch=v9 compiler should automatically pick the correct libraries
and headers I think. There seems lot of cflags used, are you using them
because of any recommendation or any issue faced ?.
A few pointers:
1. What is version of SunStudio ?
2. Try
cat atomic_cas_64-test.c
#include
> int main()
> {
> atomic_cas_64(NULL,NULL,NULL);
> }
>
> /opt/SUNWspro/bin/cc -m64 atomic_cas_64-test.c -o atomic_cas_64-test
try ldd to check which library it is resolving atomic_cas_64 symbol i.e.
ldd atomic_cas_64-test
Regards,
Muhammad Asif Naeem
> I tried adding an option CFLAGS_SSE42='-msse4.2'. No luck.
>
> *Operating System*
>
> -bash-3.00$ uname -a
> SunOS sunfire2 5.10 Generic sun4u sparc SUNW,Sun-Fire-V210
>
> *configure command output. Please let me know if you need config.log file*
>
> -checking build system type... sparc-sun-solaris2.10
> checking host system type... sparc-sun-solaris2.10
> checking which template to use... solaris
> checking whether to build with 64-bit integer date/time support... yes
> checking whether NLS is wanted... no
> checking for default port number... 5432
> checking for block size... 8kB
> checking for segment size... 1GB
> checking for WAL block size... 8kB
> checking for WAL segment size... 16MB
> checking whether the C compiler works... yes
> checking for C compiler default output file name... a.out
> checking for suffix of executables...
> checking whether we are cross compiling... no
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... no
> checking whether /opt/SUNWspro/bin/cc accepts -g... yes
> checking for /opt/SUNWspro/bin/cc option to accept ISO C89... none needed
> checking whether the C compiler still works... yes
> checking how to run the C preprocessor... /opt/SUNWspro/bin/cc -Xa -E
> checking allow thread-safe client libraries... yes
> checking whether to build with Tcl... no
> checking whether to build Perl modules... no
> checking whether to build Python modules... no
> checking whether to build with GSSAPI support... no
> checking whether to build with PAM support... no
> checking whether to build with LDAP support... no
> checking whether to build with Bonjour support... no
> checking whether to build with OpenSSL support... no
> checking whether to build with SELinux support... no
> checking for grep that handles long lines and -e... /usr/sfw/bin/ggrep
> checking for egrep... /usr/sfw/bin/ggrep -E
> checking for non-GNU ld... /usr/ucb/ld
> checking if the linker (/usr/ucb/ld) is GNU ld... no
> checking for ranlib... ranlib
> checking for strip... strip
> checking whether it is possible to strip libraries... no
> checking for ar... ar
> checking for a BSD-compatible install... config/install-sh -c
> che
Re: [GENERAL] GCC error and libmpfr.so.4 not found
On Fri, Jun 12, 2015 at 12:29 AM, Tom Lane wrote: > Asma Riyaz writes: > > in bashrc:- > > > LD_LIBRARY_PATH=/seq/annotation/bio_tools/BOOST/boost_1_46_1/lib > > > LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/seq/regev_genome_portal/lib > > If you didn't have an "export LD_LIBRARY_PATH" in there, I don't > think this would do anything. > > But your real problem is you have a broken gcc installation. Basic > tools like that should not need a custom LD_LIBRARY_PATH to work. > +1, don't jump directly to complex script like PG configure, fix your gcc installation first and test it with hello world c program. > > regards, tom lane > > > -- > Sent via pgsql-general mailing list (pgsql-general@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-general >
Re: [GENERAL] Where the core files are generated in running postgres server
Hi Tarkeshwar, If you are using Unix/Linux following link might be useful to you i.e. https://wiki.postgresql.org/wiki/Getting_a_stack_trace_of_a_running_PostgreSQL_backend_on_Linux/BSD#Enabling_core_dumps Regards, Muhammad Asif Naeem On Mon, Aug 4, 2014 at 3:19 PM, M Tarkeshwar Rao < m.tarkeshwar@ericsson.com> wrote: > Hi all, > > I want to know the exact path of the core files generated by Postgres > server during crash? > > Can I configure it or generate it? > > Regards > Tarkeshwar > > -- > Sent via pgsql-general mailing list (pgsql-general@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-general >
Re: [GENERAL] unable to build postgres-9.4 in os x 10.9 with python
Hi Reiner, Latest PG 9.4 source code seems building fine with --with-python option on my OS X 10.9.3 box i.e. pc1dotnetpk:inst asif$ find . | grep -i python > ./lib/plpython2.so > ./share/extension/plpython2u--1.0.sql > ./share/extension/plpython2u--unpackaged--1.0.sql > ./share/extension/plpython2u.control > ./share/extension/plpythonu--1.0.sql > ./share/extension/plpythonu--unpackaged--1.0.sql > ./share/extension/plpythonu.control > pc1dotnetpk:inst asif$ uname -a > Darwin pc1dotnetpk.local 13.2.0 Darwin Kernel Version 13.2.0: Thu Apr 17 > 23:03:13 PDT 2014; root:xnu-2422.100.13~1/RELEASE_X86_64 x86_64 Can you please share config.log and complete make log with failure ?. Regards, Muhammad Asif Naeem On Fri, May 30, 2014 at 9:49 PM, reiner peterke wrote: > Hi, > > has anyone else had this issue and does any one know the solution? > > Since upgrading my mac from os x 10.8 to 10.9, i can no long build > postgres with '--with-python’. > > i get the following error. > > ld: framework not found Python > clang: error: linker command failed with exit code 1 (use -v to see > invocation) > make[3]: *** [plpython2.so] Error 1 > make[2]: *** [all-plpython-recurse] Error 2 > make[1]: *** [all-pl-recurse] Error 2 > make: *** [all-src-recurse] Error 2 > > my full configure command is > > configure '--prefix=/usr/local/postgres/9.4' '--with-perl' '--with-python' > '--with-libxml' '-with-openssl' '--with-includes=/opt/local/include/' > '--with-libraries=/opt/local/lib' > > any help would be appreciated. > > reiner > > > > -- > Sent via pgsql-general mailing list (pgsql-general@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-general >
Re: [GENERAL] Trouble finding libpq on Centos 6.5
On Thu, May 8, 2014 at 5:02 PM, Aqz wrote: > I have devel package installed. > > Centos postgresql package adds file to /etc/ld.so.conf.d with path to > pgsql libraries directory (/usr/pgsql-9.3/lib/) so I don't think that is > the problem. > As you can see in my first message ldconfig -p lists libpq library among > others.. > Also : > $ LD_LIBRARY_PATH="/usr/pgsql-9.3/lib" ld -lpq > ld: cannot find -lpq > I am not sure if Linux linker (ld) pick run time linker/loader paths by default ( AFAIR Solaris compiler/linker can use library search path from LD_LIBRARY_PATH etc ). I would suggest to use -L or add directory /usr/pgsql-9.3/lib to linker (ld) default library search path. you can check current search path via "ld --verbose | grep SEARCH_DIR". > 2014-05-08 13:14 GMT+02:00 Asif Naeem : > >> Hi, >> >> Yes. It seems that /usr/pgsql-9.3/lib is not in linker default library >> search path. You may either require to provide it explicitly via -L option >> while linking or add /usr/pgsql-9.3/lib to the default library search path. >> >> As suggested by Alberto, for development work related devel package is >> required. >> >> Regards, >> Muhammad Asif Naeem >> >> On Thu, May 8, 2014 at 1:06 PM, Alberto Cabello Sánchez >> wrote: >> >>> On Thu, 8 May 2014 08:54:44 +0200 >>> Aqz wrote: >>> >>> > Hi. >>> > >>> > I'm not sure if I should write here, or on a Centos mailing list... >>> > >>> > I have fresh, vanilla Centos 6.5 with postgresql yum repository added. >>> > I've successfully installed postgresql93 and postgresql93-libs >>> packages, >>> > but still : >>> > >>> > $ ld -lpq >>> > ld: cannot find -lpq >>> > >>> > $ ldconfig -p >>> > libpq.so.5 (libc6,x86-64) => /usr/pgsql-9.3/lib/libpq.so.5 >>> > libpq.so (libc6,x86-64) => /usr/pgsql-9.3/lib/libpq.so >>> > >>> > >>> > What did I do wrong? >>> >>> Hi, Wojtek >>> >>> Maybe you need to install postgresql93-devel package? >>> >>> >>> -- >>> Alberto Cabello Sánchez >>> >>> >>> -- >>> Sent via pgsql-general mailing list (pgsql-general@postgresql.org) >>> To make changes to your subscription: >>> http://www.postgresql.org/mailpref/pgsql-general >>> >> >> > > > -- > Wojtek Dziubiński > www.aquaz.eu >
Re: [GENERAL] Trouble finding libpq on Centos 6.5
Hi, Yes. It seems that /usr/pgsql-9.3/lib is not in linker default library search path. You may either require to provide it explicitly via -L option while linking or add /usr/pgsql-9.3/lib to the default library search path. As suggested by Alberto, for development work related devel package is required. Regards, Muhammad Asif Naeem On Thu, May 8, 2014 at 1:06 PM, Alberto Cabello Sánchez wrote: > On Thu, 8 May 2014 08:54:44 +0200 > Aqz wrote: > > > Hi. > > > > I'm not sure if I should write here, or on a Centos mailing list... > > > > I have fresh, vanilla Centos 6.5 with postgresql yum repository added. > > I've successfully installed postgresql93 and postgresql93-libs packages, > > but still : > > > > $ ld -lpq > > ld: cannot find -lpq > > > > $ ldconfig -p > > libpq.so.5 (libc6,x86-64) => /usr/pgsql-9.3/lib/libpq.so.5 > > libpq.so (libc6,x86-64) => /usr/pgsql-9.3/lib/libpq.so > > > > > > What did I do wrong? > > Hi, Wojtek > > Maybe you need to install postgresql93-devel package? > > > -- > Alberto Cabello Sánchez > > > -- > Sent via pgsql-general mailing list (pgsql-general@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-general >
