unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "andrés ramírez" <rrandresf@hotmail.com>
To: Yuri Khan <yuri.v.khan@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, help-gnu-emacs@gnu.org
Subject: Re: compiling emacs 29.3 "--without-makeinfo" and texinfo 4.13
Date: Sun, 26 May 2024 04:53:15 +0000	[thread overview]
Message-ID: <SJ1PR12MB63634F4CD894D4D5C2DC3D35A6F72@SJ1PR12MB6363.namprd12.prod.outlook.com> (raw)
In-Reply-To: <CAP_d_8VYjQ9iFxzUjS2BDaMKh2YZvpizYv6_XQ1kV8ExqCMP7Q@mail.gmail.com>

Hi Yuri.
>>>>> "Yuri" == Yuri Khan <yuri.v.khan@gmail.com> writes:

    Yuri> On Sun, 26 May 2024 at 14:49, andrés ramírez <rrandresf@hotmail.com> wrote:
    >> No idea. This is a chroot for doing cross compilation. on my distro (archlinux) cmp is
    >> provided by diffutils. I do not know if the package has the same name on debian. Perhaps I
    >> could install It and I could see if that makes a difference.

    Yuri> On Debian, cmp is provided by diffutils and diffutils is classified as Essential, which in
    Yuri> Debian parlance means other packages can count on them being always installed and skip
    Yuri> declaring them as a runtime or build dependency. If your deb building environment lacks
    Yuri> Essential packages, it’s horribly broken and you should get it fixed.

Actually the package was installed on /usr/bin/gnu. The reason for that
is for giving space on /usr/bin for the busybox symlinks. But those
links where not present on the chroot. So I solved it adding
'/usr/bin/gnu' to the PATH var.

And That solved the issue. Emacs compilation with the 29.3 release
tarball did NOT call makeinfo. 

Thanks for all your help guys.
Best Regards
Andrés Ramírez



  reply	other threads:[~2024-05-26  4:53 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-25  5:18 compiling emacs 29.3 "--without-makeinfo" and texinfo 4.13 Andrés Ramírez
2024-05-25 16:56 ` Eli Zaretskii
2024-05-25 15:24   ` andrés ramírez
2024-05-26  4:51     ` Eli Zaretskii
2024-05-25 20:13       ` andrés ramírez
2024-05-25 21:06         ` andrés ramírez
2024-05-26  7:13           ` Eli Zaretskii
2024-05-25 21:47             ` andrés ramírez
2024-05-26  8:14               ` Eli Zaretskii
2024-05-26  8:16               ` Yuri Khan
2024-05-26  4:53                 ` andrés ramírez [this message]
2024-05-26  8:24               ` Stefan Monnier via Users list for the GNU Emacs text editor
2024-05-26  5:33                 ` andrés ramírez
2024-05-26  1:50 ` Po Lu
2024-05-25 17:03   ` andrés ramírez
2024-05-26  3:19   ` Po Lu
2024-05-25 17:23     ` andrés ramírez
2024-05-25 18:54     ` andrés ramírez
2024-05-26  5:37       ` Po Lu
2024-05-25 19:42         ` andrés ramírez
2024-05-26  6:56         ` Eli Zaretskii

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://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=SJ1PR12MB63634F4CD894D4D5C2DC3D35A6F72@SJ1PR12MB6363.namprd12.prod.outlook.com \
    --to=rrandresf@hotmail.com \
    --cc=eliz@gnu.org \
    --cc=help-gnu-emacs@gnu.org \
    --cc=yuri.v.khan@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.
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).