unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: <lin.sun@zoom.us>
Cc: 42790@debbugs.gnu.org
Subject: bug#42790: [PATH] 27.1; Add version info into file name "emacs.pdmp" to avoid mismatch pdmp file
Date: Fri, 14 Aug 2020 16:53:29 +0200	[thread overview]
Message-ID: <87d03t5lee.fsf@gnus.org> (raw)
In-Reply-To: <cecc01d66ec5$5aeecb20$10cc6160$@zoom.us> (lin sun's message of "Mon, 10 Aug 2020 11:21:32 +0800")

<lin.sun@zoom.us> writes:

> The pdmp file always named as "emcas.pdmp", this will cause error in my
> local that I build two Emacs with different configuration options and
> different suffix from same source tree. Here are configure lines:
>
> $ cd ~/emacs-min && ~/emacs/configure --program-suffix=m --with-x=no...
> $ cd ~/emacs-nor && ~/emacs/configure # normal build
>
> After installation, run the first installed Emacs binary, there is
> error message as follow:

I'm not sure I understand the use case or the recipe -- if I try
something like that, it just says

gcc: error: fontset.o: No such file or directory
gcc: error: fringe.o: No such file or directory
gcc: error: image.o: No such file or directory
gcc: error: xgselect.o: No such file or directory
gcc: error: terminfo.o: No such file or directory
gcc: error: lastfile.o: No such file or directory
make[1]: *** [Makefile:651: temacs] Error 1
make[1]: Leaving directory '/tmp/em/src'
make: *** [Makefile:424: src] Error 2

after saying "make".

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  parent reply	other threads:[~2020-08-14 14:53 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-10  3:21 bug#42790: [PATH] 27.1; Add version info into file name "emacs.pdmp" to avoid mismatch pdmp file via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-08-10  8:27 ` Andreas Schwab
2020-08-10  9:24   ` via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-11-16  1:03     ` Glenn Morris
2020-11-20 15:07       ` Eli Zaretskii
2021-02-27  1:40         ` Glenn Morris
2021-02-27  7:22           ` Eli Zaretskii
2021-02-27 16:05             ` Daniel Colascione
2021-02-27 18:21             ` Glenn Morris
2021-02-27 18:49               ` Eli Zaretskii
2021-07-21 13:51         ` Lars Ingebrigtsen
2021-09-30  1:33           ` Glenn Morris
2021-09-30  6:47             ` Lars Ingebrigtsen
2021-10-11 12:04               ` Lars Ingebrigtsen
2020-08-14 14:53 ` Lars Ingebrigtsen [this message]
2020-08-15  4:52   ` via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-08-15 10:42     ` Lars Ingebrigtsen
2020-08-15 10:47       ` Lars Ingebrigtsen
2020-08-16  0:30         ` via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=87d03t5lee.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=42790@debbugs.gnu.org \
    --cc=lin.sun@zoom.us \
    /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).