public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Doug Sutherland" <doug@proficio.ca>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: ttsynth help: download problem
Date: Sun, 24 Jun 2007 22:30:22 -0500	[thread overview]
Message-ID: <006401c7b6d9$29d398c0$ab00a8c0@tenstac> (raw)
In-Reply-To: <Pine.LNX.4.63.0706241804070.7220@desktop.localnet>

Regarding libstdc++-libc6.2-2.so.3

Mike wrote:
> So how do I find gcc-2.95 and build it without damaging my machine?

It's more complicated that needing a compiler. That library contains
runtimes created with an old glibc that stopped being used on most
linux systems a few years ago.

> You mentioned a discussion on this list regarding doing that.

This is old, but I made it work three years ago on slackware 9.1 by
building an old glibc from source

http://www.cs.vassar.edu/~priestdo/emacspeak/list.archive.2004/msg00128.html

That might be difficult if you've never built any toolchains. Since
time has passed and we're using newer gcc, you might have to
install an old gcc to compile the glibc without the build choking.
And it can get worse, there is certain combinations of the gcc,
glibc, and binutils that will build together, other combinations
break, and they are moving targets. If I still had the old ibm tts
files I'd have another go at trying to make it work the hard way,
but I have lost my viavoice files somewhere along the way.

> Would it be possible for someone just to email the library to me?  I'm
> using the 2.6.13 kernel under Slackware 10.1.

You may find that even if you can locate a binary library and put
it on your system, it may be incompatible and when you execute
programs that need it you may get unresolved symbol errors or
the dreaded segmentation error. That error is almost as useful
as the three possible errors shown on my first computer, which
were: what? how? and sorry. LOL I am not kidding. That was
the only thing the computer could tell you if it didn't understand
what you typed.

This, however, looks interesting
http://www.digitalsanctum.com/2007/01/28/libstdc-libc62-2so3-on-ubuntu/

It states that on ubuntu, installing libstdc++2.10-glibc2.2 gives you
compatibility with libstdc++-libc6.2-2.so.3

Slackware may be a different story, but what I did before is surely
doable again, if you're willing to build toolchains.

  -- Doug



  reply	other threads:[~ UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Mike Keithley
 ` Luke Yelavich
     [not found]   ` <Pine.LNX.4.63.0706232011230.6171@desktop.localnet>
     ` Luke Yelavich
       ` Mike Keithley
         ` Doug Sutherland [this message]
           ` Mike Keithley
             ` Christopher Moore
             ` Doug Sutherland

Reply instructions:

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

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

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='006401c7b6d9$29d398c0$ab00a8c0@tenstac' \
    --to=doug@proficio.ca \
    --cc=speakup@braille.uwo.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).