-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Failed to byte-compile..." #543
Comments
No - packages should get built during init, and then when byte-compilation happens after init, the packages should already be built, and safe mode is set by Radian to enforce that, since otherwise something has gone wrong with the modification detection system. Are your packages getting rebuilt every time you start up? |
My packages are not rebuilt every time I start up. Apologies, but I may have misspoken when I said that I was getting the "Failed to byte-compile: Building straight not allowed in safe mode" without an init.local.el. I may actually have had some init.local.el that I incorrectly believed would be trivial. In any case, when I start with --debug-init now and ... a) no init.local.el, Messages reports: b) the following init.local.el, Messages reports:
Likewise when init.local.el contains only a simple message statement, the byte-compile fails. Thanks, |
Yes, that's correct. It's expected that there are no messages written during init. |
But why would an init.local.el that contains only
fail to byte-compile? |
Hi,
I've been experiencing a number of byte-compile errors with various configurations, so I decided to pare everything down.
I wrote a script that uninstalls emacs (railwaycat's "Mac port"), reinstalls emacs, deletes ~/.emacs.d, clones Radian, and then sets the Radian symlinks so I can report based a "clean" install -- without an
init.local.el
.Running this, I am now experiencing "Failed to byte-compile: Building straight not allowed in safe mode"
Is this expected?
Thanks,
Matthew
The text was updated successfully, but these errors were encountered: