unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Liliana Marie Prikler <liliana.prikler@ist.tugraz.at>
To: zimoun <zimon.toutoune@gmail.com>,
	Vicente Mataix ferrandiz <vicente.mataix-ferrandiz@inria.fr>,
	54400@debbugs.gnu.org
Subject: bug#54400: Emacs error in Ubuntu
Date: Wed, 16 Mar 2022 10:48:25 +0100	[thread overview]
Message-ID: <06777b60013c79b14b29820bfd14b0f947f94353.camel@ist.tugraz.at> (raw)
In-Reply-To: <86tuby44u3.fsf@gmail.com>

Hi simon

Am Mittwoch, dem 16.03.2022 um 10:36 +0100 schrieb zimoun:
> --8<---------------cut here---------------start------------->8---
> $ guix graph --path emacs xz
> emacs@27.2
> libxml2@2.9.12
> xz@5.2.5
> --8<---------------cut here---------------end--------------->8---
Thanks for investigating, I did not consider ‘guix graph’.

> Note that
> 
> --8<---------------cut here---------------start------------->8---
>     (source (origin
>               (method url-fetch)
>               (uri (string-append "mirror://gnu/emacs/emacs-"
>                                   version ".tar.xz"))
> --8<---------------cut here---------------end--------------->8---
> 
> but I do not see ’xz’ in the implicit inputs; only emacs-minimal. 
> Quick look, maybe I miss it.
IIRC, it'd be quite deep in the unpack chain, but maybe I'm mixing
things up as well.

> Well, indeed, something seems unexpected if the Emacs binary is
> linked to liblzma and this liblzma is not an explicit inputs but
> instead comes from a reference to another inputs.
I think that's what you'd observe on other distros as well.  IIRC the
linker ought to correctly resolve/"propagate" such dependencies, so it
shouldn't be a problem.

Vicente, could you check the output of ldd for your Emacs, as well as
libxml2 and also check whether your xz package is perhaps broken and
ought to be repaired?

Cheers




  reply	other threads:[~2022-03-16  9:49 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
2022-03-16  9:36   ` zimoun
2022-03-16  9:48     ` Liliana Marie Prikler [this message]
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=06777b60013c79b14b29820bfd14b0f947f94353.camel@ist.tugraz.at \
    --to=liliana.prikler@ist.tugraz.at \
    --cc=54400@debbugs.gnu.org \
    --cc=vicente.mataix-ferrandiz@inria.fr \
    --cc=zimon.toutoune@gmail.com \
    /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).