From: Stephen Berman <stephen.berman@gmx.net>
To: "Рабочая Почта" <work.mail.for.me.tgg@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: Porting Emacs on new platform.
Date: Thu, 16 Sep 2021 00:49:02 +0200 [thread overview]
Message-ID: <877dfhfo9t.fsf@gmx.net> (raw)
In-Reply-To: <CAFPVqnR34GuVvhQF=U+08sTm32bykJnS_5kG4BjOT6CxcKUtyw@mail.gmail.com> ("Рабочая Почта"'s message of "Thu, 16 Sep 2021 01:20:46 +0300")
On Thu, 16 Sep 2021 01:20:46 +0300 Рабочая Почта <work.mail.for.me.tgg@gmail.com> wrote:
> Thanks for answering.
>
> Thanks for pointing out where places dumper in.
> Yes, E2K, when Linux is installed, is a common Posix platform.
> No important messages around, only in/out directory and compiling. But
> i can send this btw, then will
> be working with the machine again.
> Could you say, how to compile emacs with debugging information? I mean
> proper building with scripts like this:
> ./autogen.sh
> ./configure --with-x-toolkit=no --with-xpm=no --with-jpeg=no
> --with-png=no --with-gif=no --with-tiff=no
> make
> make install
<emacs>/etc/DEBUG say this:
*** Configuring Emacs for debugging
It is best to configure and build Emacs with special options that will
make the debugging easier. Here are the configure-time options we
recommend (they are in addition to any other options you might need,
such as --prefix):
./configure --enable-checking='yes,glyphs' --enable-check-lisp-object-type \
CFLAGS='-O0 -g3'
The -O0 flag is important, as debugging optimized code can be hard.
If the problem happens only with optimized code, you may need to
enable optimizations. If that happens, try using -Og first instead of
-O2, as -Og disables some optimizations that make debugging some code
exceptionally hard.
> And how do you advise debugging Elisp code?
See the above mentioned file for more details.
> And where to send the patches? To this mail?
Probably best to send to the debbugs issue tracker; using `M-x
submit-emacs-patch' might be helpful for that.
> Thanks for helping.
Steve Berman
next prev parent reply other threads:[~2021-09-15 22:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-14 22:27 Porting Emacs on new platform Рабочая Почта
2021-09-15 1:15 ` Po Lu
2021-09-15 21:32 ` Рабочая Почта
2021-09-16 3:14 ` Po Lu
2021-09-16 5:22 ` Eli Zaretskii
2021-09-15 6:05 ` Eli Zaretskii
2021-09-15 22:20 ` Рабочая Почта
2021-09-15 22:49 ` Stephen Berman [this message]
2021-09-16 7:30 ` Andreas Schwab
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=877dfhfo9t.fsf@gmx.net \
--to=stephen.berman@gmx.net \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=work.mail.for.me.tgg@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/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).