pg.ddx.io  pgsql-php@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jules Alberts <jules.alberts@arbodienst-limburg.nl>
To: pgsql-php@postgresql.org
Subject: Re: 7.3.1 update gives PHP libpq.so.2 problem
Date: Wed, 05 Feb 2003 09:24:47 +0100
Message-ID: <20030205082511.D59BD1CB1A5@koshin.dsl.systemec.nl> (raw)
In-Reply-To: <20030204141323.4F84F1CB1A5@koshin.dsl.systemec.nl>
References: <30B1837E-3848-11D7-B773-000393B3A702@canprint.com.au>

Op 4 Feb 2003 (15:12), schreef Jules Alberts <jules.alberts@arbodienst-limburg.nl>:
> Op 5 Feb 2003 (0:54), schreef Matthew Horoschun <mhoroschun@canprint.com.au>:
> > Hi Jules,
> > 
> > On Wednesday, February 5, 2003, at 12:06  AM, Peter De Muer (Work)  
> > wrote:
> > 
> > > try making a soft link  libpq.so.2 to the libpq.so.3 file  that comes  
> > > with
> > > PHP 7.3.1.
> > >>
> > >> 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 think he wanted to avoid the soft link (or hard link for that  
> > matter)... Its not a neat solution. Generally the whole reason for  
> > changing library major numbers it to let the users know that the  
> > exports have changed and that you'll need to recompile your client!
> > 
> > http://www.postgresql.org/news.php?NewsID=105
> > 
> > >> 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?
> > 
> > You're right. Its good practice to use your package system wherever  
> > possible. However, how about using a RPM source package?
> > 
> > ftp://ftp.redhat.com/pub/redhat/linux/7.3/en/os/i386/SRPMS/php-4.1.2- 
> > 7.src.rpm
> 
> Hello Matthew, thanks for your reaction. Would using a src RPM make any 
> difference? I guess I would do a ./configure, make and make install and 
> wonder just as much where alle the binaries etc. have ended up as if 
> when I had used a tarball source install (pardon my Dutch :-).
> 
> Are applications made ("maked") from source RPMs easier to deinstall as 
> apps made from tarball sources?
> 
> TIA!

I tried to do a source install (what I don't really want) of PHP. It 
doesn't work, complains about not finding libpq-fe.h, even when I 
specify the correct postgresql path. I know there probably is a 
solution for this too, but what's next?

Well, life's short and there's a lot of work to do. I'm going back to 
7.2 with binary RPMs.



view thread (5+ messages)

Message-ID: <20030205082511.D59BD1CB1A5@koshin.dsl.systemec.nl>
Permalink:  ../20030205082511.D59BD1CB1A5@koshin.dsl.systemec.nl/
Also on:    postgresql.org/message-id/20030205082511.D59BD1CB1A5@koshin.dsl.systemec.nl

 · 

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: jules.alberts@arbodienst-limburg.nl
  Subject: Re: 7.3.1 update gives PHP libpq.so.2 problem
  In-Reply-To: <20030205082511.D59BD1CB1A5@koshin.dsl.systemec.nl>
  References: <30B1837E-3848-11D7-B773-000393B3A702@canprint.com.au> <20030205082511.D59BD1CB1A5@koshin.dsl.systemec.nl>

* 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