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

v14.17.5 fails to build if configured with --shared-cares #39747

Closed
asavah opened this issue Aug 12, 2021 · 3 comments
Closed

v14.17.5 fails to build if configured with --shared-cares #39747

asavah opened this issue Aug 12, 2021 · 3 comments
Labels
cares Issues and PRs related to the c-ares dependency or the cares_wrap binding.

Comments

@asavah
Copy link

asavah commented Aug 12, 2021

Version

v14.17.5

Platform

Linux kross-1910 5.11.0-25-generic #27-Ubuntu SMP Fri Jul 9 23:06:29 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Subsystem

No response

What steps will reproduce the bug?

configure node with --shared-cares which most linux distros use, try building it

How often does it reproduce? Is there a required condition?

always

What is the expected behavior?

Clean build

What do you see instead?

Build failure

In file included from ../src/cares_wrap.cc:25:
../src/cares_wrap.h:25:11: fatal error: ares_nameser.h: No such file or directory
   25 | # include <ares_nameser.h>
      |           ^~~~~~~~~~~~~~~~

Additional information

ares_nameser.h is a private header which is not installed to the system include dir.

4923b59 shouldn't have landed in LTS in its current state ...

@richardlau richardlau linked a pull request Aug 12, 2021 that will close this issue
@dilyanpalauzov
Copy link

dilyanpalauzov commented Aug 26, 2021

The same applies to v16.8.0 . libcares does not install ares_nameser.h , so the declarations from this file are not public.

@dilyanpalauzov
Copy link

I see now at c-ares/c-ares@b9845b8 that the headers are now installed.

@Mesteery Mesteery added the cares Issues and PRs related to the c-ares dependency or the cares_wrap binding. label Sep 25, 2021
@richardlau
Copy link
Member

This should now be fixed with the c-ares 1.18.1 in Node.js 12, 14, 16 and 17.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cares Issues and PRs related to the c-ares dependency or the cares_wrap binding.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants