|
From: | GNU bug Tracking System |
Subject: | bug#54400: closed (Emacs error in Ubuntu) |
Date: | Thu, 14 Jul 2022 04:17:01 +0000 |
Your message dated Thu, 14 Jul 2022 00:15:55 -0400 with message-id <874jzkxrb8.fsf@gmail.com> and subject line Re: bug#54400: Emacs error in Ubuntu has caused the debbugs.gnu.org bug report #54400, regarding Emacs error in Ubuntu to be marked as done. (If you believe you have received this mail in error, please contact help-debbugs@gnu.org.) -- 54400: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=54400 GNU Bug Tracking System Contact help-debbugs@gnu.org with problems
--- Begin Message ---Subject: Emacs error in Ubuntu Date: Tue, 15 Mar 2022 17:09:23 +0100 (CET) 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
Best regards,
Vicente Mataix Ferrándiz
--- End Message ---
--- Begin Message ---Subject: Re: bug#54400: Emacs error in Ubuntu Date: Thu, 14 Jul 2022 00:15:55 -0400 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/28.1 (gnu/linux) Hi, Ludovic Courtès <ludo@gnu.org> writes: > Hi, > > Vicente Mataix ferrandiz <vicente.mataix-ferrandiz@inria.fr> skribis: > >> 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 > > Could you check whether the ‘LD_LIBRARY_PATH’ environment variable is > defined, for instance by running: > > env | grep LD_LIBRARY_PATH > > If it is, please unset it: > > unset LD_LIBRARY_PATH > > Does it help? Since we haven't heard back from Vicente, I presume their problem has been resolved somehow. Closing. Maxim
--- End Message ---
[Prev in Thread] | Current Thread | [Next in Thread] |