Doug Laidlaw wrote:
> I am one of the fortunate few who has been able to run IBM's ViaVoice on
> Linux right up to Mandriva 2006. Now the crunch seems to have arrived.
>
> ViaVoice for Linux hasn't been developed since 2000, and it has severe
> dependency problems. These usually relate to the version of glibc.
> Various attempts have been made to operate ViaVoice in its own environment,
> but sooner or later, it has to make contact with the real world.
>
> Mandriva 2006 used glibc 2.3.5, Mandriva 2007 uses glibc 2.4. This seems to
> mean that I have run out of luck.
>
> Are there any other suggestions for a dual glibc system?
>
> Doug.

Red Hat distribute older libraries for Enterprise Linux. For example on my
RHEL 3 system, I have:

compat-libstdc++-7.3-2.96.128
compat-gcc-7.3-2.96.128
compat-gcc-c++-7.3-2.96.128
compat-libstdc++-devel-7.3-2.96.128
compat-glibc-7.x-2.2.4.32.6
compat-db-4.0.14-5.3

and on my CentOS 4.4 (clone of RHEL4) system I have:

compat-libstdc++-33-3.2.3-47.3
java-1.4.2-gcj-compat-1.4.2.0-27jpp
compat-libstdc++-296-2.96-132.7.2
compat-db-4.1.25-9

There may be others.

--
.~. Jean-David Beyer Registered Linux User 85642.
/V\ PGP-Key: 9A2FC99A Registered Machine 241939.
/( )\ Shrewsbury, New Jersey http://counter.li.org
^^-^^ 08:55:01 up 9 days, 11:22, 3 users, load average: 3.41, 3.41, 3.71

Jean-David Beyer wrote:

> Doug Laidlaw wrote:
>> I am one of the fortunate few who has been able to run IBM's ViaVoice on
>> Linux right up to Mandriva 2006. Now the crunch seems to have arrived.
>>
>> ViaVoice for Linux hasn't been developed since 2000, and it has severe
>> dependency problems. These usually relate to the version of glibc.
>> Various attempts have been made to operate ViaVoice in its own
>> environment, but sooner or later, it has to make contact with the real
>> world.
>>
>> Mandriva 2006 used glibc 2.3.5, Mandriva 2007 uses glibc 2.4. This seems
>> to mean that I have run out of luck.
>>
>> Are there any other suggestions for a dual glibc system?
>>
>> Doug.
>
> Red Hat distribute older libraries for Enterprise Linux. For example on my
> RHEL 3 system, I have:
>
> compat-libstdc++-7.3-2.96.128
> compat-gcc-7.3-2.96.128
> compat-gcc-c++-7.3-2.96.128
> compat-libstdc++-devel-7.3-2.96.128
> compat-glibc-7.x-2.2.4.32.6
> compat-db-4.0.14-5.3
>
> and on my CentOS 4.4 (clone of RHEL4) system I have:
>
> compat-libstdc++-33-3.2.3-47.3
> java-1.4.2-gcj-compat-1.4.2.0-27jpp
> compat-libstdc++-296-2.96-132.7.2
> compat-db-4.1.25-9
>
> There may be others.
>
Thanks. That is worth knowing. There is an "Enterprise" version of
Mandriva as well. The real question is: will the two versions coexist on
one system?

Doug.
--
It is your privilege to smoke (tobacco company leaflet); is it my privilege
to pay for your cancer or stroke treatment?

Doug Laidlaw wrote:
> Jean-David Beyer wrote:
>
>> Doug Laidlaw wrote:
>>> I am one of the fortunate few who has been able to run IBM's ViaVoice on
>>> Linux right up to Mandriva 2006. Now the crunch seems to have arrived.
>>>
>>> ViaVoice for Linux hasn't been developed since 2000, and it has severe
>>> dependency problems. These usually relate to the version of glibc.
>>> Various attempts have been made to operate ViaVoice in its own
>>> environment, but sooner or later, it has to make contact with the real
>>> world.
>>>
>>> Mandriva 2006 used glibc 2.3.5, Mandriva 2007 uses glibc 2.4. This seems
>>> to mean that I have run out of luck.
>>>
>>> Are there any other suggestions for a dual glibc system?
>>>
>>> Doug.
>> Red Hat distribute older libraries for Enterprise Linux. For example on my
>> RHEL 3 system, I have:
>>
>> compat-libstdc++-7.3-2.96.128
>> compat-gcc-7.3-2.96.128
>> compat-gcc-c++-7.3-2.96.128
>> compat-libstdc++-devel-7.3-2.96.128
>> compat-glibc-7.x-2.2.4.32.6
>> compat-db-4.0.14-5.3
>>
>> and on my CentOS 4.4 (clone of RHEL4) system I have:
>>
>> compat-libstdc++-33-3.2.3-47.3
>> java-1.4.2-gcj-compat-1.4.2.0-27jpp
>> compat-libstdc++-296-2.96-132.7.2
>> compat-db-4.1.25-9
>>
>> There may be others.
>>
> Thanks. That is worth knowing. There is an "Enterprise" version of
> Mandriva as well. The real question is: will the two versions coexist on
> one system?
>
> Doug.
Sure they will. Some of my stuff will run only with the new stuff (most of
it), and one or two applications will run only with the old stuff.

--
.~. Jean-David Beyer Registered Linux User 85642.
/V\ PGP-Key: 9A2FC99A Registered Machine 241939.
/( )\ Shrewsbury, New Jersey http://counter.li.org
^^-^^ 07:50:01 up 10 days, 10:17, 3 users, load average: 4.19, 4.12, 3.94

Jean-David Beyer writes:

>Doug Laidlaw wrote:
>> Jean-David Beyer wrote:
>>
>>> Doug Laidlaw wrote:
>>>> I am one of the fortunate few who has been able to run IBM's ViaVoice on
>>>> Linux right up to Mandriva 2006. Now the crunch seems to have arrived.
>>>>
>>>> ViaVoice for Linux hasn't been developed since 2000, and it has severe
>>>> dependency problems. These usually relate to the version of glibc.
>>>> Various attempts have been made to operate ViaVoice in its own
>>>> environment, but sooner or later, it has to make contact with the real
>>>> world.
>>>>
>>>> Mandriva 2006 used glibc 2.3.5, Mandriva 2007 uses glibc 2.4. This seems
>>>> to mean that I have run out of luck.
>>>>
>>>> Are there any other suggestions for a dual glibc system?
>>>>
>>>> Doug.
>>> Red Hat distribute older libraries for Enterprise Linux. For example on my
>>> RHEL 3 system, I have:
>>>
>>> compat-libstdc++-7.3-2.96.128
>>> compat-gcc-7.3-2.96.128
>>> compat-gcc-c++-7.3-2.96.128
>>> compat-libstdc++-devel-7.3-2.96.128
>>> compat-glibc-7.x-2.2.4.32.6
>>> compat-db-4.0.14-5.3
>>>
>>> and on my CentOS 4.4 (clone of RHEL4) system I have:
>>>
>>> compat-libstdc++-33-3.2.3-47.3
>>> java-1.4.2-gcj-compat-1.4.2.0-27jpp
>>> compat-libstdc++-296-2.96-132.7.2
>>> compat-db-4.1.25-9
>>>
>>> There may be others.
>>>
>> Thanks. That is worth knowing. There is an "Enterprise" version of
>> Mandriva as well. The real question is: will the two versions coexist on
>> one system?
>>
>> Doug.
>Sure they will. Some of my stuff will run only with the new stuff (most of
>it), and one or two applications will run only with the old stuff.

What you can do is to put the old version of glibc into some special
directory. Then you start the program from a script, in which you have
export LD_LIBRARY_PATH=/that/special/directory
so that the loader finds that glibc first and uses it.

Unruh wrote:
> Jean-David Beyer writes:
>
>> Doug Laidlaw wrote:
>>> Jean-David Beyer wrote:
>>>
>>>> Doug Laidlaw wrote:
>>>>> I am one of the fortunate few who has been able to run IBM's ViaVoice on
>>>>> Linux right up to Mandriva 2006. Now the crunch seems to have arrived.
>>>>>
>>>>> ViaVoice for Linux hasn't been developed since 2000, and it has severe
>>>>> dependency problems. These usually relate to the version of glibc.
>>>>> Various attempts have been made to operate ViaVoice in its own
>>>>> environment, but sooner or later, it has to make contact with the real
>>>>> world.
>>>>>
>>>>> Mandriva 2006 used glibc 2.3.5, Mandriva 2007 uses glibc 2.4. This seems
>>>>> to mean that I have run out of luck.
>>>>>
>>>>> Are there any other suggestions for a dual glibc system?
>>>>>
>>>>> Doug.
>>>> Red Hat distribute older libraries for Enterprise Linux. For example on my
>>>> RHEL 3 system, I have:
>>>>
>>>> compat-libstdc++-7.3-2.96.128
>>>> compat-gcc-7.3-2.96.128
>>>> compat-gcc-c++-7.3-2.96.128
>>>> compat-libstdc++-devel-7.3-2.96.128
>>>> compat-glibc-7.x-2.2.4.32.6
>>>> compat-db-4.0.14-5.3
>>>>
>>>> and on my CentOS 4.4 (clone of RHEL4) system I have:
>>>>
>>>> compat-libstdc++-33-3.2.3-47.3
>>>> java-1.4.2-gcj-compat-1.4.2.0-27jpp
>>>> compat-libstdc++-296-2.96-132.7.2
>>>> compat-db-4.1.25-9
>>>>
>>>> There may be others.
>>>>
>>> Thanks. That is worth knowing. There is an "Enterprise" version of
>>> Mandriva as well. The real question is: will the two versions coexist on
>>> one system?
>>>
>>> Doug.
>> Sure they will. Some of my stuff will run only with the new stuff (most of
>> it), and one or two applications will run only with the old stuff.
>
> What you can do is to put the old version of glibc into some special
> directory. Then you start the program from a script, in which you have
> export LD_LIBRARY_PATH=/that/special/directory
> so that the loader finds that glibc first and uses it.

I never had to do any of that. The linker or loader manages it
automatically. I never define or use LD_LIBRARY_PATH.

--
.~. Jean-David Beyer Registered Linux User 85642.
/V\ PGP-Key: 9A2FC99A Registered Machine 241939.
/( )\ Shrewsbury, New Jersey http://counter.li.org
^^-^^ 14:05:01 up 10 days, 16:32, 3 users, load average: 4.37, 4.28, 4.23

Jean-David Beyer wrote:

> Unruh wrote:
>> Jean-David Beyer writes:
>>
>>> Doug Laidlaw wrote:
>>>> Jean-David Beyer wrote:
>>>>
>>>>> Doug Laidlaw wrote:
>>>>>> I am one of the fortunate few who has been able to run IBM's ViaVoice
>>>>>> on
>>>>>> Linux right up to Mandriva 2006. Now the crunch seems to have
>>>>>> arrived.
>>>>>>
>>>>>> ViaVoice for Linux hasn't been developed since 2000, and it has
>>>>>> severe
>>>>>> dependency problems. These usually relate to the version of glibc.
>>>>>> Various attempts have been made to operate ViaVoice in its own
>>>>>> environment, but sooner or later, it has to make contact with the
>>>>>> real world.
>>>>>>
>>>>>> Mandriva 2006 used glibc 2.3.5, Mandriva 2007 uses glibc 2.4. This
>>>>>> seems to mean that I have run out of luck.
>>>>>>
>>>>>> Are there any other suggestions for a dual glibc system?
>>>>>>
>>>>>> Doug.
>>>>> Red Hat distribute older libraries for Enterprise Linux. For example
>>>>> on my RHEL 3 system, I have:
>>>>>
>>>>> compat-libstdc++-7.3-2.96.128
>>>>> compat-gcc-7.3-2.96.128
>>>>> compat-gcc-c++-7.3-2.96.128
>>>>> compat-libstdc++-devel-7.3-2.96.128
>>>>> compat-glibc-7.x-2.2.4.32.6
>>>>> compat-db-4.0.14-5.3
>>>>>
>>>>> and on my CentOS 4.4 (clone of RHEL4) system I have:
>>>>>
>>>>> compat-libstdc++-33-3.2.3-47.3
>>>>> java-1.4.2-gcj-compat-1.4.2.0-27jpp
>>>>> compat-libstdc++-296-2.96-132.7.2
>>>>> compat-db-4.1.25-9
>>>>>
>>>>> There may be others.
>>>>>
>>>> Thanks. That is worth knowing. There is an "Enterprise" version of
>>>> Mandriva as well. The real question is: will the two versions coexist
>>>> on one system?
>>>>
>>>> Doug.
>>> Sure they will. Some of my stuff will run only with the new stuff (most
>>> of it), and one or two applications will run only with the old stuff.
>>
>> What you can do is to put the old version of glibc into some special
>> directory. Then you start the program from a script, in which you have
>> export LD_LIBRARY_PATH=/that/special/directory
>> so that the loader finds that glibc first and uses it.
>
> I never had to do any of that. The linker or loader manages it
> automatically. I never define or use LD_LIBRARY_PATH.
>
I haven't either, but this may be the first time. I wouldn't want to use
the old gcc generally.

Previously, the problem has been that ViaVoice can't find an old version of
gcc. One solution was to create a special directory tree as almost a
chroot jail, but we couldn't keep ViaVoice inside it. As soon as Xvoice
called it, it was back in the present-day world.

Doug.
--
I am a part of all that I have met.
- Lord Tennyson, "Ulysses."

Doug Laidlaw wrote:

> Jean-David Beyer wrote:
>
>> Unruh wrote:
>>> Jean-David Beyer writes:
>>>
>>>> Doug Laidlaw wrote:
>>>>> Jean-David Beyer wrote:
>>>>>
>>>>>> Doug Laidlaw wrote:
>>>>>>> I am one of the fortunate few who has been able to run IBM's
>>>>>>> ViaVoice on
>>>>>>> Linux right up to Mandriva 2006. Now the crunch seems to have
>>>>>>> arrived.
>>>>>>>
>>>>>>> ViaVoice for Linux hasn't been developed since 2000, and it has
>>>>>>> severe
>>>>>>> dependency problems. These usually relate to the version of glibc.
>>>>>>> Various attempts have been made to operate ViaVoice in its own
>>>>>>> environment, but sooner or later, it has to make contact with the
>>>>>>> real world.
>>>>>>>
>>>>>>> Mandriva 2006 used glibc 2.3.5, Mandriva 2007 uses glibc 2.4. This
>>>>>>> seems to mean that I have run out of luck.
>>>>>>>
>>>>>>> Are there any other suggestions for a dual glibc system?
>>>>>>>
>>>>>>> Doug.
>>>>>> Red Hat distribute older libraries for Enterprise Linux. For example
>>>>>> on my RHEL 3 system, I have:
>>>>>>
>>>>>> compat-libstdc++-7.3-2.96.128
>>>>>> compat-gcc-7.3-2.96.128
>>>>>> compat-gcc-c++-7.3-2.96.128
>>>>>> compat-libstdc++-devel-7.3-2.96.128
>>>>>> compat-glibc-7.x-2.2.4.32.6
>>>>>> compat-db-4.0.14-5.3
>>>>>>
>>>>>> and on my CentOS 4.4 (clone of RHEL4) system I have:
>>>>>>
>>>>>> compat-libstdc++-33-3.2.3-47.3
>>>>>> java-1.4.2-gcj-compat-1.4.2.0-27jpp
>>>>>> compat-libstdc++-296-2.96-132.7.2
>>>>>> compat-db-4.1.25-9
>>>>>>
>>>>>> There may be others.
>>>>>>
>>>>> Thanks. That is worth knowing. There is an "Enterprise" version of
>>>>> Mandriva as well. The real question is: will the two versions coexist
>>>>> on one system?
>>>>>
>>>>> Doug.
>>>> Sure they will. Some of my stuff will run only with the new stuff (most
>>>> of it), and one or two applications will run only with the old stuff.
>>>
>>> What you can do is to put the old version of glibc into some special
>>> directory. Then you start the program from a script, in which you have
>>> export LD_LIBRARY_PATH=/that/special/directory
>>> so that the loader finds that glibc first and uses it.
>>
>> I never had to do any of that. The linker or loader manages it
>> automatically. I never define or use LD_LIBRARY_PATH.
>>
> I haven't either, but this may be the first time. I wouldn't want to use
> the old gcc generally.
>
> Previously, the problem has been that ViaVoice can't find an old version
> of
> gcc. One solution was to create a special directory tree as almost a
> chroot jail, but we couldn't keep ViaVoice inside it. As soon as Xvoice
> called it, it was back in the present-day world.
>
> Doug.
Trying to install the older version "on top" of the present one failed. The
installer wouldn't allow two inconsistent versions to coexist. Using
LD_LIBRARY_PATH did work, but other errors followed. For the time being, I
am concentrating on getting the xvoice tarball to install under the new
glibc. I am not sure whether that will be enough.

Doug.
--
If computers get too powerful, we can organize them into
a committee.
-Author Unknown.

Doug Laidlaw wrote:
> Doug Laidlaw wrote:
>
>> Jean-David Beyer wrote:
>>
>>> Unruh wrote:
>>>> Jean-David Beyer writes:
>>>>
>>>>> Doug Laidlaw wrote:
>>>>>> Jean-David Beyer wrote:
>>>>>>
>>>>>>> Doug Laidlaw wrote:
>>>>>>>> I am one of the fortunate few who has been able to run IBM's
>>>>>>>> ViaVoice on
>>>>>>>> Linux right up to Mandriva 2006. Now the crunch seems to have
>>>>>>>> arrived.
>>>>>>>>
>>>>>>>> ViaVoice for Linux hasn't been developed since 2000, and it has
>>>>>>>> severe
>>>>>>>> dependency problems. These usually relate to the version of glibc.
>>>>>>>> Various attempts have been made to operate ViaVoice in its own
>>>>>>>> environment, but sooner or later, it has to make contact with the
>>>>>>>> real world.
>>>>>>>>
>>>>>>>> Mandriva 2006 used glibc 2.3.5, Mandriva 2007 uses glibc 2.4. This
>>>>>>>> seems to mean that I have run out of luck.
>>>>>>>>
>>>>>>>> Are there any other suggestions for a dual glibc system?
>>>>>>>>
>>>>>>>> Doug.
>>>>>>> Red Hat distribute older libraries for Enterprise Linux. For example
>>>>>>> on my RHEL 3 system, I have:
>>>>>>>
>>>>>>> compat-libstdc++-7.3-2.96.128
>>>>>>> compat-gcc-7.3-2.96.128
>>>>>>> compat-gcc-c++-7.3-2.96.128
>>>>>>> compat-libstdc++-devel-7.3-2.96.128
>>>>>>> compat-glibc-7.x-2.2.4.32.6
>>>>>>> compat-db-4.0.14-5.3
>>>>>>>
>>>>>>> and on my CentOS 4.4 (clone of RHEL4) system I have:
>>>>>>>
>>>>>>> compat-libstdc++-33-3.2.3-47.3
>>>>>>> java-1.4.2-gcj-compat-1.4.2.0-27jpp
>>>>>>> compat-libstdc++-296-2.96-132.7.2
>>>>>>> compat-db-4.1.25-9
>>>>>>>
>>>>>>> There may be others.
>>>>>>>
>>>>>> Thanks. That is worth knowing. There is an "Enterprise" version of
>>>>>> Mandriva as well. The real question is: will the two versions coexist
>>>>>> on one system?
>>>>>>
>>>>>> Doug.
>>>>> Sure they will. Some of my stuff will run only with the new stuff (most
>>>>> of it), and one or two applications will run only with the old stuff.
>>>> What you can do is to put the old version of glibc into some special
>>>> directory. Then you start the program from a script, in which you have
>>>> export LD_LIBRARY_PATH=/that/special/directory
>>>> so that the loader finds that glibc first and uses it.
>>> I never had to do any of that. The linker or loader manages it
>>> automatically. I never define or use LD_LIBRARY_PATH.
>>>
>> I haven't either, but this may be the first time. I wouldn't want to use
>> the old gcc generally.
>>
>> Previously, the problem has been that ViaVoice can't find an old version
>> of
>> gcc. One solution was to create a special directory tree as almost a
>> chroot jail, but we couldn't keep ViaVoice inside it. As soon as Xvoice
>> called it, it was back in the present-day world.
>>
>> Doug.
> Trying to install the older version "on top" of the present one failed. The
> installer wouldn't allow two inconsistent versions to coexist. Using
> LD_LIBRARY_PATH did work, but other errors followed. For the time being, I
> am concentrating on getting the xvoice tarball to install under the new
> glibc. I am not sure whether that will be enough.
>
> Doug.
You do not install such stuff "on top", you install it "next to"; i.e.,
install it with rpm -ivh, nor rpm -Uvh.

--
.~. Jean-David Beyer Registered Linux User 85642.
/V\ PGP-Key: 9A2FC99A Registered Machine 241939.
/( )\ Shrewsbury, New Jersey http://counter.li.org
^^-^^ 13:00:01 up 11 days, 15:27, 3 users, load average: 4.37, 4.28, 4.24