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

go/adbc: macOS builds need to link libresolv #962

Closed
lidavidm opened this issue Aug 3, 2023 · 2 comments · Fixed by #971
Closed

go/adbc: macOS builds need to link libresolv #962

lidavidm opened this issue Aug 3, 2023 · 2 comments · Fixed by #971

Comments

@lidavidm
Copy link
Member

lidavidm commented Aug 3, 2023

https://github.com/golang/go/issues/58159, https://github.com/golang/go/issues/58416

Only affects macOS, Go 1.20+. It looks like our R CI jobs don't explicitly install Go and so just pick up Go from the base image, so that would explain it (our other jobs explicitly install Go 1.18).

Causes issues like this:

❯ checking dependencies in R code ... NOTE
  Error: unable to load shared object '/Users/runner/work/arrow-adbc/arrow-adbc/r/adbcsnowflake/check/adbcsnowflake.Rcheck/adbcsnowflake/libs/adbcsnowflake.so':
    dlopen(/Users/runner/work/arrow-adbc/arrow-adbc/r/adbcsnowflake/check/adbcsnowflake.Rcheck/adbcsnowflake/libs/adbcsnowflake.so, 0x0006): symbol not found in flat namespace (_res_9_nclose)
  Call sequence:
  3: dyn.load(file, DLLpath = DLLpath, ...)
  2: library.dynam(lib, package, package.lib)
  1: loadNamespace(package, lib.loc)
  Execution halted
@paleolimbot
Copy link
Member

I ran into this when building documentation using docker compose run docs on Ubuntu, so it may not be specific to MacOS. This was updated/maybe fixed in the R documentation PR ( https://github.com/apache/arrow-adbc/pull/977/files#diff-fdf92781420c6b0ea091d62c80657009e21923c0651955f0aa4c7f4636495640 ) but I'm surprised that it was an issue on MacOS so perhaps there is something else going on.

@lidavidm
Copy link
Member Author

The linked issues show that it's related to a Go-side change, and not all our pipelines pinned the Go version, so I think that explains it.

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.

2 participants