From: Liliana Marie Prikler <liliana.prikler@ist.tugraz.at>
To: Vicente Mataix ferrandiz <vicente.mataix-ferrandiz@inria.fr>,
54400@debbugs.gnu.org
Subject: bug#54400: Emacs error in Ubuntu
Date: Wed, 16 Mar 2022 09:02:58 +0100 [thread overview]
Message-ID: <d79f7dae9acfd0295dffe38934871ab79d777f5f.camel@ist.tugraz.at> (raw)
In-Reply-To: <6780887.11555111.1647360563972.JavaMail.zimbra@inria.fr>
Hi Vicente,
Am Dienstag, dem 15.03.2022 um 17:09 +0100 schrieb Vicente Mataix
ferrandiz:
> Greetings,
>
> I follow the instructions from:
>
> https://guix.gnu.org/manual/en/guix.html#Binary-Installation
>
> Installation (Ubuntu 20.04):
>
> cd /tmp
> wget
> https://git.savannah.gnu.org/cgit/guix.git/plain/etc/guix-install.sh
> chmod +x guix-install.sh
> ./guix-install.sh
> guix install glibc-utf8-locales
> export GUIX_LOCPATH="$HOME/.guix-profile/lib/locale"
>
> Update:
>
> guix pull
>
> Install emacs:
>
> guix install emacs
>
> Load environment:
>
> GUIX_PROFILE="$HOME/.guix-profile"
> . "$GUIX_PROFILE/etc/profile"
>
> Run emacs:
>
> emacs
>
> /home/vmataixf/.guix-profile/bin/emacs: error while loading shared
> libraries: liblzma.so.5: cannot open shared object file: No such file
> or director
That is an interesting and surprisingly difficult to debug error you
have there. On Guix System, we have
--8<---------------cut here---------------start------------->8---
$ ldd $GUIX_ENVIRONMENT/bin/.emacs-27.2-real | grep lzma
liblzma.so.5 => /gnu/store/c8isj4jq6knv0icfgr43di6q3nvdzkx7-xz-5.2.5/lib/liblzma.so.5 (0x00007f7919fee000)
--8<---------------cut here---------------end--------------->8---
where xz is one of those magic libraries you'd expect to exist in any
distro. However,
--8<---------------cut here---------------start------------->8---
$ guix show emacs | recsel -p dependencies
dependencies: acl@2.3.1 alsa-lib@1.2.4 cairo@1.16.0 coreutils@8.32
+ dbus@1.12.20 ghostscript@9.54.0 giflib@5.2.1 gmp@6.2.1 gnutls@3.7.2 gpm@1.20.7
+ gtk+@3.24.30 gzip@1.10 harfbuzz@2.8.2 jansson@2.13.1 libice@1.0.10
+ libjpeg-turbo@2.0.5 libotf@0.9.16 libpng@1.6.37 librsvg@2.50.7 libsm@1.2.3
+ libtiff@4.3.0 libx11@1.7.3.1 libxft@2.3.3 libxml2@2.9.12 libxpm@3.5.13
+ m17n-lib@1.8.0 mailutils@3.14 ncurses@6.2.20210619 pango@1.48.10
+ pkg-config@0.29.2 poppler@21.07.0 texinfo@6.7 zlib@1.2.11
--8<---------------cut here---------------end--------------->8---
If at all, xz is included as implicit input to unpack Emacs! We should
probably add it as explicit input instead.
Cheers
next prev parent reply other threads:[~2022-03-16 8:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-15 16:09 bug#54400: Emacs error in Ubuntu Vicente Mataix ferrandiz
2022-03-16 8:02 ` Liliana Marie Prikler [this message]
2022-03-16 9:36 ` zimoun
2022-03-16 9:48 ` Liliana Marie Prikler
2022-03-16 10:11 ` zimoun
2022-03-16 10:30 ` Liliana Marie Prikler
2022-03-16 9:23 ` zimoun
2022-03-16 9:32 ` Vicente Mataix ferrandiz
2022-03-16 9:42 ` zimoun
2022-03-16 10:52 ` Ludovic Courtès
2022-07-14 4:15 ` Maxim Cournoyer
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d79f7dae9acfd0295dffe38934871ab79d777f5f.camel@ist.tugraz.at \
--to=liliana.prikler@ist.tugraz.at \
--cc=54400@debbugs.gnu.org \
--cc=vicente.mataix-ferrandiz@inria.fr \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).