-
-
Notifications
You must be signed in to change notification settings - Fork 10.1k
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
Improve HOMEBREW_INSTALL_FROM_API failure messaging #13824
Comments
Build from source isn't supported yet when installing from the API and the glibc bottle can only be used from the default prefix. Though even with a default prefix, postinstall also isn't supported so you won't be able to install glibc fully through the API currently. |
Ah, that'll do it. Is there an issue/PR to watch for either of those, so I can try again later? |
Postinstall is included as a point in #13794. Build from source I don't think is explicitly tracked anywhere, but it has been discussed as something that may be mostly covered by the postinstall work. |
I'm not sure we're planning on ever supporting installs from source with Regardless, I think the messaging should be improved here so it's clear that |
That's too bad, but here's hoping. It does seem like the messaging or behavior could be improved, because this error doesn't really point to the root cause or solution/workaround.
In any case, it sounds like brew could make that determination from the package metadata, before most of the download & install work. |
Probably this. |
This is why we ask you to do this 😉
Agreed.
Agreed 👍🏻 |
@jacktose would you mind posting the output of the |
@Rylan12 Sure. Fresh install as described above and then:
|
@MikeMcQuaid I've replicated it on a fresh Ubuntu 22.04.1 on WSL. When Homebrew is installed in the default directory, To replicate this, I had to reinstall Homebrew without sudo, i.e. in Fresh install
|
Note that it shouldn't be necessary to install glibc on 22.04. It's only needed on earlier versions. |
I can redo that in 18, 20, or another distro, if it makes a difference. Or with some other formula with no or non-relocatable linux bottle. |
brew config
outputbrew doctor
outputsee gist
Verification
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)?
Fresh install of brew 3.6.0 (on CentOS 7, no sudo, non-default path) with
HOMEBREW_INSTALL_FROM_API
set.To test the setting as suggested in the blog and hopefully shrink my linuxbrew directory size.
What happened (include all command output)?
brew install gcc
failed on its first dependency,glibc
:With
HOMEBREW_INSTALL_FROM_API
unset,brew install gcc
(cloned homebrew/core and then) succeeded.I'd guess this has to do with the new handling of
glibc
in glibc-bootstrap, but I don't understand how all that works.Installation
brew install gcc
from APIbrew install gcc
traditionally (from clone)Note that there's another problem with
xz
, but at leastglibc
succeeded. One problem at a time.What did you expect to happen?
Successful installation of
gcc
and its dependencies, includingglibc
, from the API.Step-by-step reproduction instructions (by running
brew
commands)The text was updated successfully, but these errors were encountered: