>Adam, trust me, I went through this three months ago, I got involved
>in some significant discussion on rtr's forum, and the best possible
>solution, the one that rtr itself recommends, is the one I described
>above. Put the special libraries in a special place, and let apache
>know about it usin
On 9 Apr 1997, Michael Alan Dorman wrote:
> Dale Scheetz <[EMAIL PROTECTED]> writes:
> > You are confusing ld.so with gcc. The compiler/linker doesn't search
> > /usr/local, you would need to direct it to look there. What you need to
> > put into /usr/local/lib is the shared libraries used by ld.s
On 8 Apr 1997, Manoj Srivastava wrote:
> Hi,
> >>"Dale" == Dale Scheetz <[EMAIL PROTECTED]> writes:
>
> Dale> On Tue, 8 Apr 1997, Steffen R. Mueller wrote:
>
> Dale> One way to deal with this would be to downgrade to the old
> Dale> library, then copy the installed libraries, by hand, into
> Dal
-BEGIN PGP SIGNED MESSAGE-
On 09-Apr-97 Michael Alan Dorman wrote:
>Dale Scheetz <[EMAIL PROTECTED]> writes:
>> You are confusing ld.so with gcc. The compiler/linker doesn't search
>> /usr/local, you would need to direct it to look there. What you need to
>> put into /usr/local/lib is the
Dale Scheetz <[EMAIL PROTECTED]> writes:
> You are confusing ld.so with gcc. The compiler/linker doesn't search
> /usr/local, you would need to direct it to look there. What you need to
> put into /usr/local/lib is the shared libraries used by ld.so during
> program loading. This path is on the lis
On Wed, 9 Apr 1997, Adam Shand wrote:
> >One way to deal with this would be to downgrade to the old library, then
> >copy the installed libraries, by hand, into /usr/local/lib. You can then
> >upgrade back to the current libraries and everything should work without
> >the need for the LD_PRELOAD.
Hi,
>>"Dale" == Dale Scheetz <[EMAIL PROTECTED]> writes:
Dale> On Tue, 8 Apr 1997, Steffen R. Mueller wrote:
Dale> One way to deal with this would be to downgrade to the old
Dale> library, then copy the installed libraries, by hand, into
Dale> /usr/local/lib. You can then upgrade back to the curr
>One way to deal with this would be to downgrade to the old library, then
>copy the installed libraries, by hand, into /usr/local/lib. You can then
>upgrade back to the current libraries and everything should work without
>the need for the LD_PRELOAD.
I'm very new to this but couldn't you end up w
On Tue, 8 Apr 1997, Steffen R. Mueller wrote:
> Thus spake Adam Shand ([EMAIL PROTECTED]):
>
> > Hi.
>
> Hi Adam,
>
> >
> > Sorry for the follow-up post so soon after. I managed to find a copy of
> > the old libg++ 2.7.1 that I needed on the September 1996 Infomagic CD.
> >
> > For anyone in
>> For anyone interested if you want the FP97 extensions to work with Debian
>> linux all you need to do is is *downgrade* libg++ to version 2.7.1 and it
>> all becomes easy. If anyone needs help I'll be happy to provide what help
>> I can.
>
>Was it really necessary to downgrade the complete syst
Thus spake Adam Shand ([EMAIL PROTECTED]):
> Hi.
Hi Adam,
>
> Sorry for the follow-up post so soon after. I managed to find a copy of
> the old libg++ 2.7.1 that I needed on the September 1996 Infomagic CD.
>
> For anyone interested if you want the FP97 extensions to work with Debian
> linux
Hi.
Sorry for the follow-up post so soon after. I managed to find a copy of
the old libg++ 2.7.1 that I needed on the September 1996 Infomagic CD.
For anyone interested if you want the FP97 extensions to work with Debian
linux all you need to do is is *downgrade* libg++ to version 2.7.1 and it
a
12 matches
Mail list logo
