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

AF_LOCAL does not exist on Solaris #4328

Closed
dago opened this issue Sep 11, 2019 · 4 comments
Closed

AF_LOCAL does not exist on Solaris #4328

dago opened this issue Sep 11, 2019 · 4 comments
Labels

Comments

@dago
Copy link
Contributor

dago commented Sep 11, 2019

When building the latest curl 7.66.0 on Solaris 10 the build fails with

gmake[2]: Entering directory '/home/dam/mgar/pkg/curl/trunk/work/solaris10-sparc/build-isa-sparcv8plus-features-minimal/curl-7.66.0/lib'
  CC       libcurl_la-asyn-thread.lo
"asyn-thread.c", line 248: undefined symbol: AF_LOCAL
cc: acomp failed for asyn-thread.c

This is because AF_LOCAL does not exist on Solaris. As a suggested workaround AF_UNIX could be used.

@dago
Copy link
Contributor Author

dago commented Sep 11, 2019

I wonder why this did not pop up on the continuous build environment.

@bagder bagder added the build label Sep 11, 2019
@bagder
Copy link
Member

bagder commented Sep 11, 2019

why this did not pop up on the continuous build environment

That's indeed a mystery!

So does it work for you if we simply use AF_UNIX there instead?

bagder added a commit that referenced this issue Sep 11, 2019
Reported-By: Dagobert Michelsen
Fixes #4328
@dago
Copy link
Contributor Author

dago commented Sep 12, 2019

Yes, this seems to work and the compilation and testsuite passes.

@bagder bagder closed this as completed in e34ec7d Sep 12, 2019
@bagder
Copy link
Member

bagder commented Sep 12, 2019

Thanks!

@lock lock bot locked as resolved and limited conversation to collaborators Dec 11, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Development

Successfully merging a pull request may close this issue.

2 participants