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

Bug#960500: marked as done (openvdb: FTBFS with boost 1.71)

Your message dated Thu, 11 Jun 2020 09:10:58 +0100
with message-id <e650677d-d25f-439b-f5cb-771ff3a905d1@p10link.net>
and subject line re: openvdb: FTBFS with boost 1.71
has caused the Debian Bug report #960500,
regarding openvdb: FTBFS with boost 1.71
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
960500: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960500
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: openvdb
Version: 7.0.0-3
Severity: important
User: team+boost@tracker.debian.org
Usertags: boost1.71

openvdb fails to build with boost 1.71 as default:
| -- Found Python: /usr/bin/python3.8) (found suitable version "3.8.3", minimum required is "3.7")
| -- Found NumPy: /usr/lib/python3/dist-packages/numpy/core/include (found suitable version "1.18.4", minimum required is "1.12.1")
| -- Found boost_python38
| CMake Error at openvdb/python/CMakeLists.txt:209 (message):
|   Unable to find boost_numpy38, boost_numpy3 or boost_numpy.

Cheers
-- 
Sebastian Ramacher

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message --- 

openvdb fails to build with boost 1.71 as default:
| -- Found Python: /usr/bin/python3.8) (found suitable version "3.8.3", minimum required is "3.7")
| -- Found NumPy: /usr/lib/python3/dist-packages/numpy/core/include (found suitable version "1.18.4", minimum required is "1.12.1")
| -- Found boost_python38
| CMake Error at openvdb/python/CMakeLists.txt:209 (message):
|   Unable to find boost_numpy38, boost_numpy3 or boost_numpy.

It seems that the actual rebuilds of the package in debian were successful, so presumably either this was some artifact of the test-rebuild environment or some issue in another package that has been fixed since.


--- End Message ---
Reply to: