From: Ihor Radchenko <yantar92@posteo.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 75292@debbugs.gnu.org, eggert@cs.ucla.edu
Subject: bug#75292: 31.0.50; igc: (file-error "Doing vfork" "Bad address")
Date: Thu, 02 Jan 2025 20:45:57 +0000 [thread overview]
Message-ID: <874j2h0wsa.fsf@localhost> (raw)
In-Reply-To: <86msg9hspa.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
> I think you just need to recompile callproc.c and then relink. Like
> this:
>
> $ cd src
> $ make callproc.o -W callproc.c MYCPPFLAGS='-DUSABLE_POSIX_SPAWN=0'
> $ cd .. && make
Done.
I will run this version for a couple of days and see if the error
re-surface.
[yantar92:~/Git/emacs] scratch/igc+* 1h3m1s 1 ±
> cd src
[yantar92:~/Git/emacs/src] scratch/igc+* 2s ±
> make callproc.o -W callproc.c MYCPPFLAGS='-DUSABLE_POSIX_SPAWN=0'
GEN globals.h
CC callproc.o
callproc.c:47:10: warning: "USABLE_POSIX_SPAWN" redefined
47 | # define USABLE_POSIX_SPAWN 1
| ^~~~~~~~~~~~~~~~~~
<command-line>: note: this is the location of the previous definition
[yantar92:~/Git/emacs/src] scratch/igc+* 7s ±
> cd .. && make
...
--
Ihor Radchenko // yantar92,
Org mode maintainer,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2025-01-02 20:45 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-02 17:54 bug#75292: 31.0.50; igc: (file-error "Doing vfork" "Bad address") Ihor Radchenko
2025-01-02 18:37 ` Eli Zaretskii
2025-01-02 18:42 ` Ihor Radchenko
2025-01-02 19:29 ` Eli Zaretskii
2025-01-02 19:37 ` Ihor Radchenko
2025-01-02 20:22 ` Eli Zaretskii
2025-01-02 20:45 ` Ihor Radchenko [this message]
2025-01-02 21:07 ` Eli Zaretskii
2025-01-03 17:56 ` Ihor Radchenko
2025-01-03 19:33 ` Eli Zaretskii
2025-01-04 14:12 ` Ihor Radchenko
2025-01-04 14:20 ` Eli Zaretskii
2025-01-07 17:40 ` Ihor Radchenko
2025-01-07 17:50 ` Eli Zaretskii
2025-01-03 20:21 ` Eli Zaretskii
2025-01-04 14:13 ` Ihor Radchenko
2025-01-04 14:22 ` Eli Zaretskii
2025-01-04 15:21 ` Ihor Radchenko
2025-01-02 19:41 ` Paul Eggert
2025-01-02 20:35 ` Eli Zaretskii
2025-01-02 20:45 ` Pip Cet via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-03 17:58 ` Ihor Radchenko
2025-01-03 18:24 ` Pip Cet via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-03 19:47 ` Eli Zaretskii
2025-01-03 19:51 ` Pip Cet via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-03 19:11 ` Pip Cet 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=874j2h0wsa.fsf@localhost \
--to=yantar92@posteo.net \
--cc=75292@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
/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).