From: Eli Zaretskii <eliz@gnu.org>
To: Jim Dupont <jmikedupont2@gmail.com>
Cc: 66774@debbugs.gnu.org
Subject: bug#66774: master branch profiler.c: In function ‘syms_of_profiler_for_pdumper’: profiler.c:636:7: error: ‘memory’ undeclared (first use in this function)
Date: Fri, 27 Oct 2023 20:47:58 +0300 [thread overview]
Message-ID: <8334xwdkj5.fsf@gnu.org> (raw)
In-Reply-To: <CAAaxPMuL=S-zMR5VGESwitKr8NhzPp=-ZCTLgX_jkBwHPbQMAQ@mail.gmail.com> (message from Jim Dupont on Fri, 27 Oct 2023 13:29:57 -0400)
> From: Jim Dupont <jmikedupont2@gmail.com>
> Date: Fri, 27 Oct 2023 13:29:57 -0400
> Cc: 66774@debbugs.gnu.org
>
> so turning that flag on resulted in the compile working but linking had this
What do you mean by "turning that flag on"? what did you do, exactly?
> ```/usr/bin/ld: profiler.o: in function `Fprofiler_memory_log':
> /mnt/data1/2023/10/23/emacs/src/profiler.c:514: undefined reference to `export_log'
> /usr/bin/ld: profiler.o: in function `malloc_probe':
> /mnt/data1/2023/10/23/emacs/src/profiler.c:524: undefined reference to `add_sample'
> collect2: error: ld returned 1 exit status
> ```
Fixed.
prev parent reply other threads:[~2023-10-27 17:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-27 14:35 bug#66774: master branch profiler.c: In function ‘syms_of_profiler_for_pdumper’: profiler.c:636:7: error: ‘memory’ undeclared (first use in this function) Jim Dupont
2023-10-27 14:42 ` bug#66774: PROFILER_CPU_SUPPORT Jim Dupont
2023-10-27 15:27 ` bug#66774: master branch profiler.c: In function ‘syms_of_profiler_for_pdumper’: profiler.c:636:7: error: ‘memory’ undeclared (first use in this function) Eli Zaretskii
[not found] ` <CAAaxPMtMWz+mT2tE6eQFMNcg05apLANqnPJkuh=xf7_MTEs=3A@mail.gmail.com>
2023-10-27 17:10 ` Eli Zaretskii
2023-10-27 17:29 ` Jim Dupont
2023-10-27 17:39 ` Eli Zaretskii
2023-10-27 17:41 ` Jim Dupont
2023-10-27 17:49 ` Eli Zaretskii
2023-10-27 19:48 ` Jim Dupont
2024-01-10 10:34 ` Stefan Kangas
2023-10-27 17:47 ` Eli Zaretskii [this message]
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=8334xwdkj5.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=66774@debbugs.gnu.org \
--cc=jmikedupont2@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).