Emacs 29.3; suspicious error message from compile command in Emacs 29.3
The following error message appears in the terminal from which emacs was started every time I use the 'compile' command:
> emacs: writing to child signal FD: Invalid argument The compilation itself (via make) works perfectly fine. Only this new message is a bit annoying. And so cryptic, isn't it? It did not appear up until the latest update. This error message (or whatever it is) appears also, when I start emacs from a non-X tty (Ctrl + Alt + F2) and with '-Q' option. To be precise, it appears when I use 'M-x compile' and for longer compilation processes it appears at the end of the compilation, not at the beginning. I asked for help with that at the GNU bugtracker and got the following answer: > On 4/22/24 21:40, Eli Zaretskii wrote: >> When a sub-process exits, Emacs writes to file descriptor which it >> monitors with pselect. This is so we don't miss SIGCHLD for some >> reason. Why in your case this write errors out with EINVAL, I don't >> know. Perhaps Paul (CC'ed) could have some ideas. >> >> If this could happen for benign reasons, maybe we should silently >> ignore these errors. And then: My question here: Gets anyone the same message when using the M-x compile command in Emacs 29.3 on slackware? And if so, where is the correct place for filing a bug report? |
Which emacs is it?
|
Quote:
|
Quote:
|
Quote:
In sum, this error seems to be some quirk in how Emacs is being built on Slackware. |
Quote:
> gpg: Can't check signature: public key not found Searched slackware.com but couldn't find the key. Where can I get it? And then: What does 'native-comp' mean? Is it only the terminal version of emacs invoced with -nw, or does it more than that? I'd like to have it, but it is not essential. I do not understand why an emacs with more functionality (X window etc.) can be build with the gcc from the distro and apperently the part with less functionality requires another version of gcc. Is there a simple explanation for that? I once installed the multilib thing from alienbob on my system and it works well. And there was some recompiling for the mingw that is also on my system. Everything works well, but I've forgotten how everything is interrelated and I don't want to endanger things. Maybe I should stick with my alias emacs=emacs 2>/dev/null "solution" for now. |
Quote:
By all means stick with your alias and get used to the fact that things that work might bellyache like mad because the developers like that feedback. It helps them find faults. If you think emacs is bad, wait until you start wine from a terminal! |
Quote:
Code:
gpg2 --verify emacs-29.3.tar.xz.sig Quote:
Quote:
Quote:
|
solved in a sense
Quote:
Finally I found the key (is is on savannah.org what makes sense..) but decided to stick with the alias. |
slackware64-15.0/ChangeLog.txt
Code:
Tue Apr 23 19:48:05 UTC 2024 |
Quote:
|
Thanks Petri, the error-messages are gone!
|
Ah nice, fixed in the main branch, thanks Pat!
|
All times are GMT -5. The time now is 02:36 PM. |