I don't believe this was intentional. IIRC, we refactored how we deal with 
Abseil in order to support integrating the Google Cloud SDK (since both it and 
gRPC use Abseil) and that (or perhaps some other change?) might have changed 
which libraries we include. Is it workable to explicitly link Abseil into your 
final application?

In general it seems we have some work to do around dependencies, in both the 
Flight SQL C++ PR [1] and this GitHub issue [2] we've seen issues around 
linking gRPC and Protobuf as well (where even if all our tests build and pass, 
it may not be easy to consume the artifacts once installed).

[1]: https://github.com/apache/arrow/pull/11507
[2]: https://github.com/apache/arrow/issues/11657

-David

On Thu, Nov 11, 2021, at 18:50, Teodorescu, Radu (WorldQuant) wrote:
> Hi,
> We are building with arrow as a CMake external project and using 
> arrow_bundled lib for the third party dependencies.
> As of 6.0 we noticed a number of link errors and I tracked it down to a 
> number of absl libraries no longer being included (5.0 has 21 absl libraries 
> in the bundle while 6.0 only 7)
> In particular absl::strings_internal missing is giving us missing symbol for 
> absl::lts_20210324::str_format_internal::FormatPack.
> Is this a bug or a change in the inclusion process coming with 6.0
> Thank you
> Radu
> 
> 
> ###################################################################################
> 
> The information contained in this communication is confidential, may be
> 
> subject to legal privilege, and is intended only for the individual named.
> 
> If you are not the named addressee, please notify the sender immediately and
> 
> delete this email from your system.  The views expressed in this email are
> 
> the views of the sender only.  Outgoing and incoming electronic communications
> 
> to this address are electronically archived and subject to review and/or 
> disclosure
> 
> to someone other than the recipient.
> 
> ###################################################################################
> 

Reply via email to