unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: cinnaroll45 <cinnaroll45@proton.me>
Cc: 55741@debbugs.gnu.org
Subject: bug#55741: Getting an error when running the Emacs 28.1 binary that I built from source
Date: Thu, 02 Jun 2022 10:02:42 +0300	[thread overview]
Message-ID: <83h753fsz1.fsf@gnu.org> (raw)
In-Reply-To: <94gtya64sCqC5hvsMyWmvdXzDf-1vLD94qgNaDyqxZvVKdu6Gfp3XW-seCKlrE5kQXOQPCR6uOOc7g4JOfHSgFqTgIO_rw04bCzvfxE3V4E=@proton.me> (message from cinnaroll45 on Tue, 31 May 2022 19:50:42 +0000)

> Date: Tue, 31 May 2022 19:50:42 +0000
> From: cinnaroll45 <cinnaroll45@proton.me>
> Cc: 55741@debbugs.gnu.org
> 
> > The --bindir switch could be the problem: as you see from the error
> > message, Emacs 28.1 thinks its binary is in /home/user/emacs/bin, not
> > in /home/user/bin. So my suggestion is to reconfigure without the
> > --bindir switch, as I don't think this is currently supported for the
> > build with native-compilation.
> 
> Removing the --bindir switch solved the issue for me. Everything gets installed to the
> expected location and the Emacs binary runs.
> 
> > And in addition, please show the full absolute file name of the
> > emacs.pdmp file, so we could know in which directory it is installed on your system.
> 
> The location of the pdmp file was:
> /home/user/emacs/libexec/emacs/28.1/x86_64-pc-linux-gnu/emacs.pdmp
> 
> > Can you show the full absolute file name of the file window-0d1b8b93-7ef4271a.eln with
> > this installation?  In which directory is it installed by "make install"?
> 
> I couldn't expand the absolute location of `window-0d1b8b93-7ef4271a.eln`. The error message seemed to
> indicate that it was looking for it under the directory where `emacs.pdmp` is, however there were no
> directories present in that path. Just the pdmp file and three other binaries.
> 
> Thank you for helping out!

Thanks, but could you please test a possible fix for the original
problem?  I'd like us to keep supporting the --bindir configure-time
option, as we didn't intend dropping its support in Emacs 28.

So could you please re-configure Emacs 28.1 with your original
options, including the separate --bindir, and then rebuild it with the
patch below, install it by "make install", and see if Emacs now starts
up correctly?  If it doesn't start (or doesn't build), please show any
error messages you see.  TIA.

diff --git a/src/emacs.c b/src/emacs.c
index ccc0dd2..0a90b09 100644
--- a/src/emacs.c
+++ b/src/emacs.c
@@ -940,20 +940,24 @@ load_pdump (int argc, char **argv)
   sprintf (dump_file, "%s%c%s%s",
            path_exec, DIRECTORY_SEP, argv0_base, suffix);
 #if !defined (NS_SELF_CONTAINED)
-  /* Assume the Emacs binary lives in a sibling directory as set up by
-     the default installation configuration.  */
-  const char *go_up = "../../../../bin/";
-  needed += (strip_suffix ? strlen (strip_suffix) : 0)
-    - strlen (suffix) + strlen (go_up);
-  if (exec_bufsize < needed)
-    {
-      xfree (emacs_executable);
-      emacs_executable = xpalloc (NULL, &exec_bufsize, needed - exec_bufsize,
-				  -1, 1);
-    }
-  sprintf (emacs_executable, "%s%c%s%s%s",
-	   path_exec, DIRECTORY_SEP, go_up, argv0_base,
-	   strip_suffix ? strip_suffix : "");
+  if (!(emacs_executable && *emacs_executable))
+    {
+      /* If we didn't find the Emacs binary, assume that it lives in a
+	 sibling directory as set up by the default installation
+	 configuration.  */
+      const char *go_up = "../../../../bin/";
+      needed += (strip_suffix ? strlen (strip_suffix) : 0)
+	- strlen (suffix) + strlen (go_up);
+      if (exec_bufsize < needed)
+	{
+	  xfree (emacs_executable);
+	  emacs_executable = xpalloc (NULL, &exec_bufsize,
+				      needed - exec_bufsize, -1, 1);
+	}
+      sprintf (emacs_executable, "%s%c%s%s%s",
+	       path_exec, DIRECTORY_SEP, go_up, argv0_base,
+	       strip_suffix ? strip_suffix : "");
+    }
 #endif
   result = pdumper_load (dump_file, emacs_executable);
 





  reply	other threads:[~2022-06-02  7:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-31 13:01 bug#55741: Getting an error when running the Emacs 28.1 binary that I built from source cinnaroll45 via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-31 15:58 ` Eli Zaretskii
     [not found]   ` <RKVYjycV9vhF-w_P2jZl06F_xdQXNTPAE8q9YTBR2day91p9qWwBo93JnKMApdg4BE_Uqhkk1BpMQEHKPQVuMWoujvnk5yC6Jsh3Y28whLE=@proton.me>
2022-05-31 19:10     ` Eli Zaretskii
2022-05-31 16:29 ` Eli Zaretskii
2022-05-31 16:57   ` Eli Zaretskii
2022-05-31 19:50     ` cinnaroll45 via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-02  7:02       ` Eli Zaretskii [this message]
2022-06-11 10:54         ` Eli Zaretskii
2022-06-20 16:05           ` 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=83h753fsz1.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=55741@debbugs.gnu.org \
    --cc=cinnaroll45@proton.me \
    /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/emacs.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).