-
-
Notifications
You must be signed in to change notification settings - Fork 12.3k
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
On Linux: running fish
and gcc
get exec: Bad address
after brew upgrade
#115895
Comments
I think this is where the problems start. Homebrew ships its own libgcc_s.so.1, albeit in a different place ( I would remove that symlink and try If it doesn't work, can you check the output of:
|
I have completely remove the Output for your command:
|
Which error do you see when running If it's the same with a clean install, I suspect it might be one of many WSL1 issues. We recommend WSL2, is it possible for you to use that? |
It was using WSL1, and I have just converted to WSL2. However,
|
I'm also receiving a segmentation fault ( When running
I got:
So, a segfault when trying to run |
I've not been able to reproduce under this setup:
Does anything interesting appear when run through a debugger? |
One more thing: This wsl image was originally running Ubuntu 18.04 LTS with WSL 1, and then I ran |
I could not get any output when running the broken |
What is the output of Does |
|
I've had this issue in the past few days on both my WSL2 instances with some recently updated bottles like A WSL Kernel Upgrade ( |
Thank you, this solution works on my WSL2 instance too. I wonder if I need to close this issue, as the exact reason has not been figured out yet. |
Ok so I guess the latest WSL2 (now issued via the Microsoft Store, which I do recommend using the latest WSL2, but I'll look into the older one to see if there's anything we can do or if it's a WSL2 bug then maybe print some messaging. Just to check, what precise version of Windows were you all using ( |
|
And I'm running |
Can confirm, downloading WSL from the Windows Store resolved the segfaults that I was having. @stocc This required me to update my Windows version to |
I have the exact same problem. Running
winver is 21H2, cannot upgrade as I don't have a permission (work laptop). |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
brew gist-logs <formula>
link ORbrew config
ANDbrew doctor
outputVerification
brew update
and am still able to reproduce my issue.brew doctor
and that did not fix my problem.What were you trying to do (and why)?
brew upgrade
since the Ubuntu image on my WSL has been untouched for a long time.What happened (include all command output)?
I ran
brew upgrade
today and suddenly the running fish shell at/home/linuxbrew/.linuxbrew/bin/fish
terminated with error:libstdc++.so.6
not found. And then I changed my shell to/usr/bin/fish
which was installed byapt
on the Ubuntu. I ransudo apt install libstdc++6
and solve the problem. However, after that, thebrew
installedfish
said thelibgcc_s.so.1
was not found.I check the
/home/linuxbrew/.linuxbrew/lib
and thelibgcc_s.so.1
was indeed missing. At this moment, other kegs installed by homebrew and rely on this shared library object could not run either. For example,ripgrep
raised the same error. After I didsudo ln -s /usr/lib/libgcc_s.so.1 /home/linuxbrew/.linuxbrew/lib/libgcc_s.so.1
, theripgrep
can work without problem. I then ranbrew reinstall fish
but after the process completed, it raised the error:And then I also found the
gcc
installed bybrew
(version 12.2.0) stop working with the same error information.The
brew install gcc --build-from-source
fails after logs ofpatching file ...
:If I ran
brew install gcc
, it warned that the post-install was not completed. Thebrew postinstall --debug gcc
gave:What did you expect to happen?
All things go smoothly without any error.
One more thing: The bug that the
fish
shell suddenly terminated withlibstdc++.so.6
has ruined my WSL images with CentOS 8.0, since I cannot fetch that lib withdnf
any longer. And the same case has also happened on my another Ubuntu 20.04 LTS image.Step-by-step reproduction instructions (by running
brew
commands)`brew upgrade`
The text was updated successfully, but these errors were encountered: