public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Alexander Epaneshnikov <aarnaarn2@gmail.com>
To: Didier Spaier <didier@slint.fr>
Cc: Janina Sajka <janina@rednote.net>, speakup@linux-speakup.org
Subject: Re: Now Fixed: Archlinux Speakup problems after alsa package upgrade
Date: Wed, 29 Dec 2021 00:13:23 +0300	[thread overview]
Message-ID: <20211228211323.3f2uhc6hblud4h3a@alex-pc> (raw)
In-Reply-To: <86d02e30-71fc-50bd-2408-6c658ec2da29@slint.fr>

On Tue, Dec 28, 2021 at 09:15:07PM +0100, Didier Spaier wrote:
> On 28/12/2021 20:50, Janina Sajka wrote:
> > Didier Spaier writes:
> >> Hi Janina and all,
> >>
> >> On 28/12/2021 17:26, Janina Sajka wrote:
> >>> ...
> >>>
> >>> Apparently there must be some kind of reason why Espeakup can't be
> >>> agnostic between espeak and espeak-ng?
> >>
> >> espeakup is linked against the shared library installed at time of building it.
> >>
> >> Here:
> >> dance[~]$ ldd /usr/bin/espeakup | grep libespeak
> >> 	libespeak-ng.so.1 => /usr/lib64/libespeak-ng.so.1 (0x00007f290df83000)
> >>
> > Thanks, Didier. This does make sense.
> >
> >> My guess is you will find libespeak.so.1 instead running the same command.
> >>
> >> So you need to rebuild espeakup-0.90 after having removed espeak and installed
> >> espeak-ng only.
> >>
> > Are you saying I need to run ldd by hand? I thought the installation
> > process upgrading from 80 to 90 would take care of the ldd?
>
> ldd just gives an information about the dependencies. As its man page says:
>
> ldd  prints the shared objects (shared libraries) required by each program or
> shared object specified on the command line.
>
> During the installation process maybe the program in Arch that performs the
> installation checks the presence of the required dependency (probably not using
> ldd but rather according to the information recorded in some file by the packager).
>
> If so and if my assumption is correct:
> 1) When the packager built espeakup, espeak (not espeak-ng) was installed.
> 2) you can check this running the above ldd command
> 3) therefore espeakup can't use easpeak-ng, only easpeak.

espeakup 0.90 linked with espeak-ng in arch.

> > It's true I did not run an ldd when I tried to upgrade my older machine
> > to espeak-ng and espeakup-0.90.
>
> In any case you need to rebuild espeakup-0.90 against espeak-ng. How to do that

no need to do that.
Janina are you using pipewire on box with not working espeakup?
currently espeakup hasn't work with pw. I haven't found time to debug this yet.
sorry.

--
Sincerely, Alexander

  parent reply	other threads:[~ UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Kelly Prescott
     [not found] ` <20210609072927.3igbp7jvopq3c6f7@begin>
   ` Kelly Prescott
     ` Janina Sajka
     [not found]     ` <20210609110828.kpo76f2zmbixjran@begin>
       ` Kelly Prescott
         ` Janina Sajka
           ` Alexander Epaneshnikov
     [not found]             ` <YNMr0Pathc/mqx1L@rednote.net>
     [not found]               ` <20210819205617.l76b7fxume3lrf67@begin>
                 ` Alexander Epaneshnikov
                   ` Janina Sajka
     [not found]                   ` <20210820155212.rlj4addvh726cgbb@begin>
                     ` Janina Sajka
     [not found]                       ` <20210821121814.vbyw4vxysowqf7as@begin>
                         ` Janina Sajka
                           ` Didier Spaier
                             ` Janina Sajka
                               ` Didier Spaier
                                 ` Janina Sajka
     [not found]                           ` <20210821125234.onaxd4ccrrh5oiyq@begin>
                             ` Janina Sajka
               ` Now Fixed: " Janina Sajka
                 ` Jason White
                   ` Janina Sajka
                     ` Janina Sajka
                     ` Didier Spaier
                       ` Janina Sajka
                         ` Didier Spaier
                           ` Didier Spaier
                           ` Alexander Epaneshnikov [this message]
                             ` Janina Sajka
                               ` Alexander Epaneshnikov
                                 ` Janina Sajka
           ` captcha revisited, just a little Karen Lewellen
 ` Archlinux Speakup problems after alsa package upgrade Chris Brannon
   ` Kelly Prescott
     ` Jude DaShiell
       ` Jude DaShiell
     ` Chris Brannon

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=20211228211323.3f2uhc6hblud4h3a@alex-pc \
    --to=aarnaarn2@gmail.com \
    --cc=didier@slint.fr \
    --cc=janina@rednote.net \
    --cc=speakup@linux-speakup.org \
    /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).