From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=unavailable autolearn_force=no version=3.4.4 Path: border1.nntp.ams3.giganews.com!border1.nntp.ams2.giganews.com!border3.nntp.ams.giganews.com!border1.nntp.ams.giganews.com!nntp.giganews.com!feeder.erje.net!us.feeder.erje.net!usenet.blueworldhosting.com!npeer01.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!post02.iad.highwinds-media.com!news.flashnewsgroups.com-b7.4zTQh5tI3A!not-for-mail From: Stephen Leake Newsgroups: comp.lang.ada Subject: Re: Installation problem in Debian 7: gnatcoll-gpl-2013-src References: <1683c2c3-6906-4d54-9321-4e25c7495ecf@googlegroups.com> Date: Sat, 29 Jun 2013 03:54:17 -0400 Message-ID: <8561wxuzbq.fsf@stephe-leake.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (windows-nt) Cancel-Lock: sha1:A0wi5Zzx8pERN1/BfspwGdZW/ko= MIME-Version: 1.0 Content-Type: text/plain X-Complaints-To: abuse@flashnewsgroups.com Organization: FlashNewsgroups.com X-Trace: f3ffd51ce92ade25452d822440 X-Received-Bytes: 1682 X-Original-Bytes: 1868 Xref: number.nntp.dca.giganews.com comp.lang.ada:182155 Date: 2013-06-29T03:54:17-04:00 List-Id: Multiplayer1080 writes: > Hello, good afternoon! I'm trying to install gnatcoll-gpl-2013-src in > my new laptop with Debian and i get this error: > > configure: error: PostgreSQL not found > > And postgresql is already installed in the system! I have tried with > the following options: > > ./configure --prefix=/opt/gnatcoll --enable-gpl > --with-postgresql="/var/lib/postgresql/9.1" --without-gtk > > ./configure --prefix=/opt/gnatcoll --enable-gpl > --with-postgresql="/usr/lib/postgresql/9.1" --without-gtk > > ./configure --prefix=/opt/gnatcoll --enable-gpl > --with-postgresql="/etc/postgresql/9.1/" --without-gtk > > and nothing... The same error. > > Anyone can help me? Do you have the PostgreSQL devel package installed? That's probably separate from the PostgreSQL runtime package. If that's not it, read the config.log to see the exact test that failed; that may give some hints. -- -- Stephe