From user-return-1014-archive-asf-public=cust-asf.ponee.io@arrow.apache.org Mon Feb 22 18:38:16 2021 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mxout1-he-de.apache.org (mxout1-he-de.apache.org [95.216.194.37]) by mx-eu-01.ponee.io (Postfix) with ESMTPS id 3BE64180645 for ; Mon, 22 Feb 2021 19:38:16 +0100 (CET) Received: from mail.apache.org (mailroute1-lw-us.apache.org [207.244.88.153]) by mxout1-he-de.apache.org (ASF Mail Server at mxout1-he-de.apache.org) with SMTP id 6B74B64192 for ; Mon, 22 Feb 2021 18:38:15 +0000 (UTC) Received: (qmail 17925 invoked by uid 500); 22 Feb 2021 18:38:14 -0000 Mailing-List: contact user-help@arrow.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@arrow.apache.org Delivered-To: mailing list user@arrow.apache.org Received: (qmail 17914 invoked by uid 99); 22 Feb 2021 18:38:14 -0000 Received: from spamproc1-he-de.apache.org (HELO spamproc1-he-de.apache.org) (116.203.196.100) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 Feb 2021 18:38:14 +0000 Received: from localhost (localhost [127.0.0.1]) by spamproc1-he-de.apache.org (ASF Mail Server at spamproc1-he-de.apache.org) with ESMTP id AA4791FF39A for ; Mon, 22 Feb 2021 18:38:13 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamproc1-he-de.apache.org X-Spam-Flag: NO X-Spam-Score: 0.251 X-Spam-Level: X-Spam-Status: No, score=0.251 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, HTML_MESSAGE=0.2, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamproc1-he-de.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-ec2-va.apache.org ([116.203.227.195]) by localhost (spamproc1-he-de.apache.org [116.203.196.100]) (amavisd-new, port 10024) with ESMTP id 1DP2Rhef6Zns for ; Mon, 22 Feb 2021 18:38:13 +0000 (UTC) Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=209.85.160.178; helo=mail-qt1-f178.google.com; envelope-from=ajtulenko123@gmail.com; receiver= Received: from mail-qt1-f178.google.com (mail-qt1-f178.google.com [209.85.160.178]) by mx1-ec2-va.apache.org (ASF Mail Server at mx1-ec2-va.apache.org) with ESMTPS id CC699BCE61 for ; Mon, 22 Feb 2021 18:38:12 +0000 (UTC) Received: by mail-qt1-f178.google.com with SMTP id w1so3165615qto.2 for ; Mon, 22 Feb 2021 10:38:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=sp5k7nzVA2vALEpL9LtpneGrF96PeiQ2EY7kqeQHIW0=; b=fy0cTemVA3CRp7Lg+vBzBifY/8baJc2sa1HIghVbefMQM1haEPhID+6pRyMZtD++XO 4xH2Ny0979rdY34UyEOppaf4t6Jz6ckdpNEgyzUs7LetKZvD4bjrKovhcCtc7XqiVU+N oXJ+FKPhgxOl6pbdzjaGWFtzEdcpInWrdnjTtq6lhQdQvmV8twdBb7uVZn1V2SzPFUgQ QqxH1rdmy3T2TNeeYVqu7VR1ZAODBLSbV+Io3fcbSfKdZssb0V6ynaR+unbvEufY0Mp1 zgKp0+NwHgegkg2R4kQoRz4HyaLzE53wbcIPTZte5ybdUz8ZBzmFaRbupB+8ICQrTI4X +1+A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=sp5k7nzVA2vALEpL9LtpneGrF96PeiQ2EY7kqeQHIW0=; b=uf3uzyTE74oN6y9Knzah3zUxJsG1yjw/FlETOQECR6xkAPq5VaNZc0Q29dR8lO/qjR oUhIAC6immtfkSYwA43FCpNa9huWr0LQ7GMAvZPwSqVueAhTgEXliHB2KjyLViyXQI73 PsuxZs5p7ZytwM3G+QYy2KGdjWbmRERPxhYcBwSTFDqam157NKa183sMwlWolfi2crgI o5OGcll/57+lqm+s+L+Q8DDpMgv12n6GQo8NzmFjwvWK4f/ELKpslr/1PlntAkFwpsYO hFlKYKfisb3drt9etptoJ587RLylVsghsxxYYqg/NPzifOkvO/lwvFxar9GuDC0RIWnK OYfw== X-Gm-Message-State: AOAM5317U8q8Pm/0rMxZX3CBuij0awTf3IzU/Zn89YyCsuS8crB+5i7d jF+Z4S7/Bpc8NzCK21eL6MDHIn+JIfurT9tRWIY+3zZMOvo= X-Google-Smtp-Source: ABdhPJw1m8N76FZpKTvp8qiY9n509Ky2epc9Vg8c4T0dyhl7E82hmJY8t1kth2X3Bpsq6KDJj7issb4u9gyQqEMWR+Q= X-Received: by 2002:aed:2fa1:: with SMTP id m30mr911047qtd.65.1614019092237; Mon, 22 Feb 2021 10:38:12 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Alex Tulenko Date: Mon, 22 Feb 2021 13:37:54 -0500 Message-ID: Subject: Re: [pyarrow] Pyarrow=2.0.0 without boost-cpp dependancy To: user@arrow.apache.org Content-Type: multipart/alternative; boundary="000000000000a74eae05bbf11a69" --000000000000a74eae05bbf11a69 Content-Type: text/plain; charset="UTF-8" Hi Uwe, I apologize for taking your time and thank you for confirming that boost-cpp is no longer a runtime dependency. I see now that the issue was that our .condarc file placed the conda/anaconda channel about conda/conda-forge channel causing it to download from that channel which for some reason must still list boost-cpp as a dependency. Explicitly using conda-forge as the channel via "conda install -c conda-forge pyarrow=2.0.0" now no longer pulls in boost-cpp. Thanks again, Alex On Mon, Feb 22, 2021 at 11:53 AM Uwe L. Korn wrote: > Hello Alex, > > continuing this here instead of StackOverflow. Can you share your source > of conda packages: Do you use conda-forge? Can you share the output of > `conda list` of your current environment? > > What stucks me is that we have never built pyarrow on conda-forge against > boost-cpp 1.73, only 1.72 and 1.74. We though have removed boost-cpp as a > runtime dependency so I suspect the boost-cpp version change comes from > packages that aren't from conda-forge but from conda-forge. > > Best, > Uwe > > On Mon, Feb 22, 2021, at 1:48 AM, Alex Tulenko wrote: > > Hi, > > I am in the process of upgrading a project from pyarrow 0.8.0 to 2.0.0. As > part of this upgrade I see boost-cpp 1.63 is installed into the > environment. I have a number of libraries that were linked against an older > version of boost-cpp and so I would like to avoid pulling in this new > version of boost-cpp. > > I am generally looking for guidance on how to best handle this situation. > Running ldd on the libarrow*.so's installed into our conda env I can't > actually see any references to the libboost*.so's. > > This leads to my first question: is boost-cpp is a runtime requirement for > pyarrow 2.0.0? (maybe only for certain components?) If it is a runtime > requirement is there a recipe for building pyarrow/arrow-cpp with static > linkings or any version of pyarrow that can be built without boost-cpp? > > I am open to any suggestions on how to get around the boost-cpp dependency. > > Thanks! > Alex > > > --000000000000a74eae05bbf11a69 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Uwe,

I apologize for taking your tim= e and thank you for confirming that boost-cpp is no longer a runtime depend= ency. I see now that the issue was that our .condarc file placed the conda/= anaconda channel about conda/conda-forge channel causing it to download fro= m that channel which for some reason must still list boost-cpp as a depende= ncy. Explicitly using conda-forge as the channel via "conda install -c= conda-forge pyarrow=3D2.0.0" now no longer pulls in boost-cpp.
<= div>
Thanks again,
Alex

On Mon, Feb 22, 2021 at 11:53= AM Uwe L. Korn <u= welk@xhochy.com> wrote:
Hello Alex,

co= ntinuing this here instead of StackOverflow. Can you share your source of c= onda packages: Do you use conda-forge? Can you share the output of `conda l= ist` of your current environment?

What stucks = me is that we have never built pyarrow on conda-forge against boost-cpp 1.7= 3, only 1.72 and 1.74. We though have removed boost-cpp as a runtime depend= ency so I suspect the boost-cpp version change comes from packages that are= n't from conda-forge but from conda-forge.

Bes= t,
Uwe

On Mon, Feb 22, 2021, at 1:48= AM, Alex Tulenko wrote:
Hi,

I am in the proce= ss of upgrading a project from pyarrow 0.8.0 to 2.0.0. As part of this upgr= ade I see boost-cpp 1.63 is installed into the environment. I have a number= of libraries that were linked against an older version of boost-cpp and so= I would like to avoid pulling in this new version of boost-cpp.
<= div>
I am generally looking for guidance on how to best handl= e this situation. Running ldd on the libarrow*.so's installed into our = conda env I can't actually see any references to the libboost*.so's= .

This leads to my first question: is boost-cp= p is a runtime requirement for pyarrow 2.0.0? (maybe only for certain compo= nents?) If it is a runtime requirement=C2=A0is there a recipe for building = pyarrow/arrow-cpp with static linkings or any version of pyarrow that can b= e built without boost-cpp?

I am open to any su= ggestions on how to get around the boost-cpp dependency.

=
Thanks!
Alex

=
--000000000000a74eae05bbf11a69--