Re: libotf.so.1, libotf.so.0, Fedora 39, and Emacs 30.0.50

Re: libotf.so.1, libotf.so.0, Fedora 39, and Emacs 30.0.50

[Frederick Bartlett]

Michael,

Thanks for that suggestion. make bootstrap worked like a charm: it even
compiled in under 30 minutes.

Fred

On Thu, Nov 2, 2023 at 12:01 PM <help-gnu-emacs-request@gnu.org> wrote:

>
> Message: 1
> Date: Thu, 2 Nov 2023 02:41:32 -0400
> From: Frederick Bartlett <frederick.bartlett@gmail.com>
> To: help-gnu-emacs@gnu.org
> Subject: libotf.so.1, libotf.so.0, Fedora 39, and Emacs 30.0.50
> Message-ID:
>         <
> CAJr-wt15SKFzTx4XtRhrjT6Gz4VDPQ+VU8JEYxBG5jEhksLbzg@mail.gmail.com>
> Content-Type: text/plain; charset="UTF-8"
>
> After testing on another machine, I updated to F39 on my main one.
>
> And Emacs failed with the message "emacs: error while loading shared
> libraries: libotf.so.0: cannot open shared object file: No such file or
> directory"
>
> This did not happen on my older and slower test machine.
>
> The same library caused trouble about a dozen years ago, but this is a
> different problem.
>
> F39 has updated to libotf.so.1.0.0, while Emacs still wants libotf.so.0.
>
> So I added a symlink in /lib64 from libotf.so.0 to libotf.so.1.0.0.
>
> This actually works (for now), but I expect something to break soon ...
>
> Whose problem is this, though? Fedora or Emacs?
>
> Thanks!
> Fred
>
>
> ------------------------------
>
> Message: 2
> Date: Thu, 02 Nov 2023 09:20:06 +0100
> From: Michael Albinus <michael.albinus@gmx.de>
> To: Frederick Bartlett <frederick.bartlett@gmail.com>
> Cc: help-gnu-emacs@gnu.org
> Subject: Re: libotf.so.1, libotf.so.0, Fedora 39, and Emacs 30.0.50
> Message-ID: <87zfzwsh1l.fsf@gmx.de>
> Content-Type: text/plain
>
> Frederick Bartlett <frederick.bartlett@gmail.com> writes:
>
> Hi Fred,
>
> > After testing on another machine, I updated to F39 on my main one.
> >
> > And Emacs failed with the message "emacs: error while loading shared
> > libraries: libotf.so.0: cannot open shared object file: No such file or
> > directory"
> >
> > This did not happen on my older and slower test machine.
> >
> > The same library caused trouble about a dozen years ago, but this is a
> > different problem.
> >
> > F39 has updated to libotf.so.1.0.0, while Emacs still wants libotf.so.0.
> >
> > So I added a symlink in /lib64 from libotf.so.0 to libotf.so.1.0.0.
> >
> > This actually works (for now), but I expect something to break soon ...
>
> Same seen here. "make bootstrap" did solve.
>
> > Whose problem is this, though? Fedora or Emacs?
>
> I wouldn't call it a problem. Something you could expect after OS upgrade.
>
> > Thanks!
> > Fred
>
> Best regards, Michael.
>
>
>

Re: libotf.so.1, libotf.so.0, Fedora 39, and Emacs 30.0.50

[Michael Heerdegen]

Frederick Bartlett <frederick.bartlett@gmail.com> writes:

> Thanks for that suggestion. make bootstrap worked like a charm: it
> even compiled in under 30 minutes.

If possible use multiple jobs by specifying the -j command line arg to
make.  Then it will build faster.


(Some other) Michael.

Re: libotf.so.1, libotf.so.0, Fedora 39, and Emacs 30.0.50

[Emanuel Berg]

Michael Heerdegen wrote:

>> Thanks for that suggestion. make bootstrap worked like
>> a charm: it even compiled in under 30 minutes.
>
> If possible use multiple jobs by specifying the -j command
> line arg to make. Then it will build faster.

If you have a multicore CPU - you can use htop(1) to find out
- and want to prevent compilation from making your computer
nonresponsive by monopolizing the CPU - you can use
taskset(1) on Linux.

It works very well! For example, if you have a quad-core you
can do

  $ taskset -c 0,1 make

to only use cores one and two for the compilation business.

-- 
underground experts united
https://dataswamp.org/~incal

libotf.so.1, libotf.so.0, Fedora 39, and Emacs 30.0.50

[Frederick Bartlett]

After testing on another machine, I updated to F39 on my main one.

And Emacs failed with the message "emacs: error while loading shared
libraries: libotf.so.0: cannot open shared object file: No such file or
directory"

This did not happen on my older and slower test machine.

The same library caused trouble about a dozen years ago, but this is a
different problem.

F39 has updated to libotf.so.1.0.0, while Emacs still wants libotf.so.0.

So I added a symlink in /lib64 from libotf.so.0 to libotf.so.1.0.0.

This actually works (for now), but I expect something to break soon ...

Whose problem is this, though? Fedora or Emacs?

Thanks!
Fred

Re: libotf.so.1, libotf.so.0, Fedora 39, and Emacs 30.0.50

[Michael Albinus]

Frederick Bartlett <frederick.bartlett@gmail.com> writes:

Hi Fred,

> After testing on another machine, I updated to F39 on my main one.
>
> And Emacs failed with the message "emacs: error while loading shared
> libraries: libotf.so.0: cannot open shared object file: No such file or
> directory"
>
> This did not happen on my older and slower test machine.
>
> The same library caused trouble about a dozen years ago, but this is a
> different problem.
>
> F39 has updated to libotf.so.1.0.0, while Emacs still wants libotf.so.0.
>
> So I added a symlink in /lib64 from libotf.so.0 to libotf.so.1.0.0.
>
> This actually works (for now), but I expect something to break soon ...

Same seen here. "make bootstrap" did solve.

> Whose problem is this, though? Fedora or Emacs?

I wouldn't call it a problem. Something you could expect after OS upgrade.

> Thanks!
> Fred

Best regards, Michael.