pg.ddx.io  pgsql-php@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Peter De Muer (Work) <peter.demuer@inter-networks.be>
To: pgsql-php@postgresql.org
Cc: Jules Alberts <jules.alberts@arbodienst-limburg.nl>
Subject: Re: 7.3.1 update gives PHP libpq.so.2 problem
Date: Tue, 4 Feb 2003 14:06:04 +0100
Message-ID: <007701c2cc4e$2fc5e910$ce1611ac@ElBorbah> (raw)
References: <20030204123715.06E9C1CB1DA@koshin.dsl.systemec.nl>

try making a soft link  libpq.so.2 to the libpq.so.3 file  that comes with
PHP 7.3.1.

regards,

pt3r

----- Original Message -----
From: "Jules Alberts" <jules.alberts@arbodienst-limburg.nl>
To: <pgsql-php@postgresql.org>; <pgsql-admin@postgresql.org>
Sent: Tuesday, February 04, 2003 1:36 PM
Subject: [PHP] 7.3.1 update gives PHP libpq.so.2 problem


> Hello everyone,
>
> After upgrading to pg 7.3.1 on a RH 7.3 box with php 4.1.2 PHP won't
> work anymore, it misses libpq.so.2.
>
> This is a known issue, but the only solution I could google was
> compiling a recent PHP from source or creating a softlink from
> libpq.so.3 to libpq.so.2. I read that the link is a bad solution, but I
> really don't like compiling and installing PHP from source.
>
> I normally do all my packages with RPM and I'm afraid doing PHP from
> source will mess this up. What will happen if I install PHP 4.3.0 from
> source now, and later do an update on a more recent version with rpm?
> Would I have to deinstall 4.3.0 first? How?
>
> Thanks for any tips!
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly
>
>





view thread (5+ messages)  latest in thread

Message-ID: <007701c2cc4e$2fc5e910$ce1611ac@ElBorbah>
Permalink:  ../007701c2cc4e$2fc5e910$ce1611ac@ElBorbah/
Also on:    postgresql.org/message-id/007701c2cc4e$2fc5e910$ce1611ac@ElBorbah

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-php@postgresql.org
  Cc: peter.demuer@inter-networks.be, jules.alberts@arbodienst-limburg.nl
  Subject: Re: 7.3.1 update gives PHP libpq.so.2 problem
  In-Reply-To: <007701c2cc4e$2fc5e910$ce1611ac@ElBorbah>
  References: <20030204123715.06E9C1CB1DA@koshin.dsl.systemec.nl> <007701c2cc4e$2fc5e910$ce1611ac@ElBorbah>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox