Skip to content
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

Add support for glibc > 2.34 #39

Closed
Newbie012 opened this issue Dec 26, 2023 · 3 comments · Fixed by #40
Closed

Add support for glibc > 2.34 #39

Newbie012 opened this issue Dec 26, 2023 · 3 comments · Fixed by #40

Comments

@Newbie012
Copy link

It seems like the current build doesn't support GLIBC 2.35 (and later versions).

I believe updating to at least libpg_query@15-4.2.3 would fix it (or to the latest release 16-5.0.0)

related ts-safeql/safeql#196

@karlhorky
Copy link
Contributor

karlhorky commented Jan 9, 2024

@darora is this worked around by your publish of Node.js 20.x binaries for linux/amd64, linux/arm64, darwin/arm64?

Having it resolved fully will be eventually necessary as well, but maybe the publishes linked above will work around it for now.

@fkaempfer
Copy link

I still get

WARN Hit error response status 404 Not Found on https://supabase-public-artifacts-bucket.s3.amazonaws.com/libpg-query-node/queryparser-v15.0.2-node-v115-linux-x64.tar.gz 

With Node 20.11. Anyone has an idea whats wrong?

@wale wale mentioned this issue Feb 20, 2024
Merged
@pyramation
Copy link
Collaborator

should all work with latest!

we're using the new windows supported, latest v16 from libpg_query:
pganalyze/libpg_query@1ec3894

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants