-
-
Notifications
You must be signed in to change notification settings - Fork 14.2k
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
Build failure: timescaledb 2.14.2 #341408
Comments
Given the following output....
... yes, because I introduced that error message. Will look into what happens there. |
This fixes some build systems which look up the location of pg_config via the location of the postgres binary itself, e.g. timescaledb, instead of calling pg_config which is on PATH. Since the -dev output is correctly placed before the default output of postgresql in PATH, we can rely on that and call "pg_config" from the default output's fake script. Only do that, when the one on PATH is actually a different file, though, to prevent infinite loops. Resolves NixOS#341408
This fixes some build systems which look up the location of pg_config via the location of the postgres binary itself, e.g. timescaledb, instead of calling pg_config which is on PATH. Since the -dev output is correctly placed before the default output of postgresql in PATH, we can rely on that and call "pg_config" from the default output's fake script. Only do that, when the one on PATH is actually a different file, though, to prevent infinite loops. Resolves NixOS#341408
@wolfgangwalther was it supposed to be fixed be above linked PR? While it was merged timescaledb build still fails on master at 5fe89a8 EDIT: oh I see it was merged to master yet |
Yeah, it's currently in staging-next: https://nixpk.gs/pr-tracker.html?pr=341421 |
Steps To Reproduce
Steps to reproduce the behavior:
Build log
Additional context
Notify maintainers
@wolfgangwalther (I hope it's ok to tag you)
Metadata
Please run
nix-shell -p nix-info --run "nix-info -m"
and paste the result.Add a 👍 reaction to issues you find important.
The text was updated successfully, but these errors were encountered: