Could not install Emacs 28 #466
Assignees
Labels
Comments
|
Hey, Looks like this one has the same root cause as #465. In this case it's related to Meanwhile will think about better solution. |
|
Good call, I added Brew-installing |
|
😮 so many things to install; thank you for sharing |
|
next build failure involves Apple |
jidicula
added a commit
to jidicula/dotfiles
that referenced
this issue
May 17, 2022
|
So I've prepared a (possible) fix - #468. I would be grateful if you test it locally after you revert you changes to
Thank you in advance :) |
|
Since that PR makes sense in general and the build is green, I will merge it in ~12 hours, so I have more room for being responsive if this change breaks someone. Still, your testing results would be much appreciated 🙏 |
|
Hmm, no luck - it still fails with the |
|
Thanks for giving it a try. I guess with In case you feel bored, you can try to install |
|
Oh ok, I just tried on your patch with |
|
Really strange. In this case I am not sure what's wrong. Gonna read some brew sources to better understand how they bake P.S. Not merging that PR yet. |
|
Ok, got another idea. TL;DR - please try building with 542f0c0. In case it doesn't work, run with So there were two mistakes.
While I was playing with this, I added few debug lines in various places: p ENV['PATH']
system "which", "tar"
system "which", "ls"Basically, I want to see what these binaries resolve to. If you build with Before my changes, The current code is quite dirty, just want to see if that works. |
|
Still fails. Very odd, it looks like it's still grabbing macOS |
|
I see. Thanks for testing. Not sure why it picks incorrect |
|
The thing is that I can't reproduce the error. What I tried:
To help with that, I've created the following script: #!/usr/bin/env bash
export PATH=/opt/homebrew/opt/llvm/bin:/opt/homebrew/bin:/opt/homebrew/sbin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Library/Apple/usr/bin
./build 28 --verboseAnd then after running it I see the following output: I wonder if brew somehow resolves |
|
So basically, this is what I tried with different (notice that I changed How does it work for you? Also, what is your |
|
Ah, I also checked man of |
|
Just FYI, I've updated the PR a little bit. But I still have not managed to reproduce the issue. |
3 tasks
Sorry for the delay, some stuff came up and I couldn't devote any time to this. Ok so running both of those commands (
My shell is |
No luck with this either, very mystifying. It's odd that it's not being surfaced in CI either :/ I can't seem to google when the error message is emitted either - do you have any idea? It doesn't look like what and |
Sure, no worries. Plus I understand that it requires uninstalling Emacs and messing around with your environment. That's why I really advice you to use Also you can create a script like this: That will help you with testing in specific
That's interesting observation. I have no ideas right now, but might be a good lead. Will take a look later. |
|
Was closed automatically because I've merged that PR since it makes sense to have it anyways. But we know that your issue is not fixed yet. Will continue investigation. |
3 tasks
|
Just had this exact same issue. I commented everything I was adding to |
|
I know it's an old issue, but in 2024 I still have the same issue.
|
|
@FledgeXu you can try removing the following line by Let me know if it helps. |
|
Ah als, @FledgeXu please share the log of installing with |
|
@d12frosted |
|
After I commented the Here is the full log: [email protected] |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Please make sure to follow these steps (and mark the checkboxes):
brew updateand try to reproduce the issue againbrew doctor, fix all issues and try to reproduce your issue againbrew configandbrew doctorand include their outputWhat you were trying to do
Install emacs 28. Note that this is unrelated to the other issue I submitted.
What happened (include command output)
Command output
Output of
brew configOutput of
brew doctorThe text was updated successfully, but these errors were encountered: