Fix OSS build failures #572
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Without these changes, the build fails with unresolved symbol failures.
Presumably, this is because
dns/CAresResolver.cpp
anddns/CachingDNSResolver.cpp
are referenced in other files that arebeing compiled.
We then need to link
cares
because it is used in the two files addedto
PROXYGEN_CORO_SOURCES
.Finally, we need to replace the
#error
macro with astatic_assert
,because (at least as of
c-ares
version1.34.5
)ARES_SUCCESS
andARES_EREFUSED
areenum
constants, and therefore not visible to thepreprocessor.
We also drop the reference to
TraceFieldType::TXT
because thisreference doesn't seem to be generated at build time, presumably because
this is not a type included in
lib/utils/samples/TraceFieldType.txt
.Fixes #573