[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [HTCondor-users] HTCondor 8.8.4 and boost169-python2

Sorry about the surprise. To get the python 3 bindings into the stable
release, we needed to use a newer version of boost. The quickest way to
do that leverages boost169 from EPEL. It was not possible to involve 2
different boost versions in a single build. So to use python2-condor or
python3-condor, you have the run-time dependency on boost169-python2 or
boost169-python3. I tried linking the boost libraries statically to
avoid this dependency. However, one cannot link the static boost
libraries into the dynamic python htcondor and classad libraries.

On RHEL7 and derivatives, boost169-python2 or boost169-python3 are
required to use the HTCondor python bindings.

On 7/15/19 1:30 PM, Steve Huston wrote:
> I'm running a RHEL7 derivative, and until last week using the HTCondor
> stable repository.  However with the release of 8.8.4 it started
> giving errors about not being able to update due to missing
> dependencies.  I see in the changelog this minor blurb:
> "The Python bindings are now available for Python 3 on Debian, Ubuntu,
> and Enterprise Linux 7. To use these bindings on Enterprise Linux 7
> systems, the EPEL repositories are required to provide Python 3.6 and
> Boost 1.69. (Ticket #6327)"
> However what I find is that the RPMs require that boost169-python2 be
> installed, which also is part of EPEL and not configured by default on
> my machines.  Since the package in question is
> python2-condor-8.8.4-1.el7.x86_64 should it be built against either a
> different (included) version of boost, or not at all?  Or is boost169
> now a requirement for Python 2 as well, which is undocumented and
> unexpected?
Tim Theisen
Release Manager
HTCondor & Open Science Grid
Center for High Throughput Computing
Department of Computer Sciences
University of Wisconsin - Madison
4261 Computer Sciences and Statistics
1210 W Dayton St
Madison, WI 53706-1685
+1 608 265 5736