From user-return-1015-archive-asf-public=cust-asf.ponee.io@arrow.apache.org  Mon Feb 22 19:20:16 2021
Return-Path: <user-return-1015-archive-asf-public=cust-asf.ponee.io@arrow.apache.org>
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 542AE180645
	for <archive-asf-public@cust-asf.ponee.io>; Mon, 22 Feb 2021 20:20: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 70F95641D5
	for <archive-asf-public@cust-asf.ponee.io>; Mon, 22 Feb 2021 19:20:15 +0000 (UTC)
Received: (qmail 76797 invoked by uid 500); 22 Feb 2021 19:20:14 -0000
Mailing-List: contact user-help@arrow.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@arrow.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@arrow.apache.org>
List-Post: <mailto:user@arrow.apache.org>
List-Id: <user.arrow.apache.org>
Reply-To: user@arrow.apache.org
Delivered-To: mailing list user@arrow.apache.org
Received: (qmail 76773 invoked by uid 99); 22 Feb 2021 19:20:14 -0000
Received: from spamproc1-he-fi.apache.org (HELO spamproc1-he-fi.apache.org) (95.217.134.168)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 Feb 2021 19:20:14 +0000
Received: from localhost (localhost [127.0.0.1])
	by spamproc1-he-fi.apache.org (ASF Mail Server at spamproc1-he-fi.apache.org) with ESMTP id 8B188C0459
	for <user@arrow.apache.org>; Mon, 22 Feb 2021 19:20:13 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at spamproc1-he-fi.apache.org
X-Spam-Flag: NO
X-Spam-Score: 0.002
X-Spam-Level:
X-Spam-Status: No, score=0.002 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, HTML_MESSAGE=0.2, RCVD_IN_MSPIKE_H3=0.001,
	RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001]
	autolearn=disabled
Authentication-Results: spamproc1-he-fi.apache.org (amavisd-new);
	dkim=pass (2048-bit key) header.d=xhochy.com header.b=mUgFC9wx;
	dkim=pass (2048-bit key) header.d=messagingengine.com
	header.b=BXyqugx2
Received: from mx1-ec2-va.apache.org ([116.203.227.195])
	by localhost (spamproc1-he-fi.apache.org [95.217.134.168]) (amavisd-new, port 10024)
	with ESMTP id 8z6AmphVntQS for <user@arrow.apache.org>;
	Mon, 22 Feb 2021 19:20:12 +0000 (UTC)
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=66.111.4.28; helo=out4-smtp.messagingengine.com; envelope-from=uwelk@xhochy.com; receiver=<UNKNOWN> 
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28])
	by mx1-ec2-va.apache.org (ASF Mail Server at mx1-ec2-va.apache.org) with ESMTPS id 2698DBCE34
	for <user@arrow.apache.org>; Mon, 22 Feb 2021 19:20:12 +0000 (UTC)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41])
	by mailout.nyi.internal (Postfix) with ESMTP id F220D5C01F4
	for <user@arrow.apache.org>; Mon, 22 Feb 2021 14:20:05 -0500 (EST)
Received: from imap22 ([10.202.2.72])
  by compute1.internal (MEProxy); Mon, 22 Feb 2021 14:20:05 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=xhochy.com; h=
	mime-version:message-id:in-reply-to:references:date:from:to
	:subject:content-type; s=fm2; bh=rubWvqEDDM4WxRbpP/c8z4lJqlUofaZ
	xFSA2GpL6HHY=; b=mUgFC9wxg+Lu/iGgqgQp/Zt0o02QZX4RpOk7y4CbVIDc5nG
	/cMEtDIQnfGpTwNAgAA3yXu1lnesiXacBGa7lDgPExPPralS2ttWGn8f+BBcgD2+
	JYWXNPNgWlTJzKQtJYNVrqs0AW6tL0K7QUmhPjBqWrZZeSUjUZRofeCwLADQaiIs
	SxmXtfkjh4VZ6moev0ctkG01XXmFM+BFxz2VP9ZlDbbkMFjAx0NcM1Agtq90c5UI
	Pb/ZcPm79+1CJG0qypc1shEZGph+ImeCRythp7/qHK++z61qISGtTvADU1loOYPa
	YNPecNFnAGQcDtQYKS7iQN0t2AlUlLZb05pYKNQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=
	messagingengine.com; h=content-type:date:from:in-reply-to
	:message-id:mime-version:references:subject:to:x-me-proxy
	:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=rubWvq
	EDDM4WxRbpP/c8z4lJqlUofaZxFSA2GpL6HHY=; b=BXyqugx2YqSlvXAZY0Bsrt
	MzQSh/dX3ApE1kfKXmXyxGBZhFDrvp4M2w7Fv81iN/5oOtHMHqlXAeHoFz2IZCAx
	9zk6whP+JxPEYdjdkNKkbGKsr7h8odSEBHqRMxQCYclIy50+5eWIWri47ttSiEgz
	M6cFVGlsBpjuXXJYNhkOZDG6qHEYYNfwDEVuUUXIqmpOKf6i/45sWtkFALcBTdyh
	Y7J1kIynuGLJwBU5hR8M2dXXHkMXGoUqxoFZP+qvMTYbXXMpqb/egxsWvMIBeRc8
	rgeOyk9dPplpPGBKf7mKUJpl4DR4Wu0QGUZK+gvjd5Zl29MlyMW1iH0UEcK7i/lw
	==
X-ME-Sender: <xms:5QM0YHUp410oGLa9Kk3UuumaP-NRLNB0lnQiEcHReqnOndIBwRIPpg>
    <xme:5QM0YPngyQbSW2PWE1E0Vn71Q109jptBASwLt7f29jPg9VEwxY726gvmUZnNJGfsW
    McPUiUQDWw6b0F6Rg>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrkeefgdduvdefucetufdoteggodetrfdotf
    fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen
    uceurghilhhouhhtmecufedttdenucenucfjughrpefofgggkfgjfhffhffvufgtsegrtd
    erreerredtnecuhfhrohhmpedffgifvgcunfdrucfmohhrnhdfuceouhifvghlkhesgihh
    ohgthhihrdgtohhmqeenucggtffrrghtthgvrhhnpeeijeegkeelteeifefhheeljedvve
    egheeigfegfeekvdejtdffheelleevjeeigeenucffohhmrghinhepghhithhhuhgsrdgt
    ohhmnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepuh
    ifvghlkhesgihhohgthhihrdgtohhm
X-ME-Proxy: <xmx:5QM0YDbYAI8MGDqjLhTpHGggY2vly1prAi2ZuPW_N41WplFOvTvrqg>
    <xmx:5QM0YCX_RxAmQwMfgzHhDsy8u5MhyrUddc6W4KdgvAFjzHIeyi21Dg>
    <xmx:5QM0YBmlQiaENtTtVbTL4rIfyrtbHMbYH_q8FoIIRWEWOi6iOZERzw>
    <xmx:5QM0YNxtQWZSmFRQhqovy3fs1Zc0_Zry68KpCXqK2ry-GwyqLCEFNg>
Received: by mailuser.nyi.internal (Postfix, from userid 501)
	id B193562C005E; Mon, 22 Feb 2021 14:20:05 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.5.0-alpha0-141-gf094924a34-fm-20210210.001-gf094924a
Mime-Version: 1.0
Message-Id: <e6a383fc-3655-4ab3-8e89-9d9bd9c0b346@www.fastmail.com>
In-Reply-To: 
 <CAHNyYWX708_T9pZYMDE2vyzP429Jg59rNTYO=wXqYtDGM2WSeQ@mail.gmail.com>
References: 
 <CAHNyYWXKih0swzLv1qqe6n-_2CReVS7uWKfqU6L-=uecnc9W9A@mail.gmail.com>
 <e4647d03-5f0b-429e-b2c5-ca96cfffa27d@www.fastmail.com>
 <CAHNyYWX708_T9pZYMDE2vyzP429Jg59rNTYO=wXqYtDGM2WSeQ@mail.gmail.com>
Date: Mon, 22 Feb 2021 20:19:44 +0100
From: "Uwe L. Korn" <uwelk@xhochy.com>
To: user@arrow.apache.org
Subject: Re: [pyarrow] Pyarrow=2.0.0 without boost-cpp dependancy
Content-Type: multipart/alternative;
 boundary=9db05af5b0194885b9a58d75c436835f

--9db05af5b0194885b9a58d75c436835f
Content-Type: text/plain

Hello Alex,

no issues, happy to help and nice to see that your problem has been fixed with the change of the configuration. If ever other problems come up with the conda package of Arrow, feel free to open an issue at https://github.com/conda-forge/arrow-cpp-feedstock This is the best place to post them.

Best
Uwe

On Mon, Feb 22, 2021, at 7:37 PM, Alex Tulenko wrote:
> 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 <uwelk@xhochy.com> 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
>> 

--9db05af5b0194885b9a58d75c436835f
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html><html><head><title></title><style type=3D"text/css">p.Mso=
Normal,p.MsoNoSpacing{margin:0}</style></head><body><div>Hello Alex,<br>=
</div><div><br></div><div>no issues, happy to help and nice to see that =
your problem has been fixed with the change of the configuration. If eve=
r other problems come up with the conda package of Arrow, feel free to o=
pen an issue at&nbsp;<a href=3D"https://github.com/conda-forge/arrow-cpp=
-feedstock">https://github.com/conda-forge/arrow-cpp-feedstock</a>&nbsp;=
This is the best place to post them.<br></div><div><br></div><div>Best<b=
r></div><div>Uwe</div><div><br></div><div>On Mon, Feb 22, 2021, at 7:37 =
PM, Alex Tulenko wrote:<br></div><blockquote type=3D"cite" id=3D"qt" sty=
le=3D""><div dir=3D"ltr"><div>Hi Uwe,<br></div><div><br></div><div>I apo=
logize 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=3D2.0.0" now no=
 longer pulls in boost-cpp.<br></div><div><br></div><div><div>Thanks aga=
in,<br></div><div>Alex<br></div></div></div><div><br></div><div class=3D=
"qt-gmail_quote"><div dir=3D"ltr" class=3D"qt-gmail_attr">On Mon, Feb 22=
, 2021 at 11:53 AM Uwe L. Korn &lt;<a href=3D"mailto:uwelk@xhochy.com" t=
arget=3D"_blank">uwelk@xhochy.com</a>&gt; wrote:<br></div><blockquote cl=
ass=3D"qt-gmail_quote" style=3D"margin-top:0px;margin-right:0px;margin-b=
ottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-style:soli=
d;border-left-color:rgb(204, 204, 204);padding-left:1ex;"><div><u></u><b=
r></div><div><div>Hello Alex,<br></div><div><br></div><div>continuing th=
is here instead of StackOverflow. Can you share your source of conda pac=
kages: Do you use conda-forge? Can you share the output of `conda list` =
of your current environment?<br></div><div><br></div><div>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 de=
pendency so I suspect the boost-cpp version change comes from packages t=
hat aren't from conda-forge but from conda-forge.<br></div><div><br></di=
v><div>Best,<br></div><div>Uwe<br></div><div><br></div><div>On Mon, Feb =
22, 2021, at 1:48 AM, Alex Tulenko wrote:<br></div><blockquote type=3D"c=
ite" id=3D"qt-gmail-m_-7136820632811770279gmail-m_5110885697781940732gma=
il-m_-2419801552093007969qt"><div dir=3D"ltr"><div>Hi,<br></div><div><br=
></div><div>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 in=
to the environment. I have a number of libraries that were linked agains=
t an older version of boost-cpp and so I would like to avoid pulling in =
this new version of boost-cpp.<br></div><div><br></div><div>I am general=
ly looking for guidance on how to best handle this situation. Running ld=
d on the libarrow*.so's installed into our conda env I can't actually se=
e any references to the libboost*.so's.<br></div><div><br></div><div>Thi=
s 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 r=
equirement&nbsp;is there a recipe for building pyarrow/arrow-cpp with st=
atic linkings or any version of pyarrow that can be built without boost-=
cpp?<br></div><div><br></div><div>I am open to any suggestions on how to=
 get around the boost-cpp dependency.<br></div><div><br></div><div>Thank=
s!<br></div><div>Alex<br></div></div></blockquote><div><br></div></div><=
/blockquote></div></blockquote><div><br></div></body></html>
--9db05af5b0194885b9a58d75c436835f--