|Anonymous | Login | Signup for a new account||2017-10-21 06:47 CEST|
|Main | My View | View Issues | Change Log | Roadmap|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0001460||OTB-Packaging||[Orfeo Toolbox (OTB)] General||public||2017-10-10 10:04||2017-10-18 09:10|
|Platform||OS||Linux||OS Version||Ubuntu 16.04|
|Summary||0001460: Unable to compile OTB 6.2.0 RC1 with superbuild (CURL issue)|
|Description||Unable to build OTB branch release-6.2 with the superbuild. The issue is related to CURL|
I've attached the CURL configure log.
|Additional Information||My cmake config (other options with default values):|
SET(OTB_USE_QWT ON CACHE BOOL "" FORCE )
SET(OTB_USE_SHARK ON CACHE BOOL "" FORCE )
SET(OTB_USE_MUPARSERX ON CACHE BOOL "" FORCE )
SET(OTB_WRAP_PYTHON ON CACHE BOOL "" FORCE )
option(USE_SYSTEM_SWIG ON CACHE BOOL "" FORCE)
|Tags||No tags attached.|
|Attached Files||CURL-configure-err.log [^] (940 bytes) 2017-10-10 10:04|
all these are on by default. except glut(osx) libkml(msvc) and mapnik (all)
Can you post your superbuild's cmake cache. IIUC, some thing is dragging system curl and it's not OTB. I am looking at aGDAL issue here..
I don't think so : the error is reported when building CURL, and this happens before GDAL configure.
Can you check if there is something in your install tree that drags system curl? Ideally, the SuperBuild install directory should be cleaned before calling 'make'.
|I've done my build from scratch with an empty install tree. I tried to grep system curl library path in the build tree but found nothing (apart from the initial system check which found the system curl).|
|I've reproduced the issue, investigation in progress...|
Found it : it is cmake itself that is dragging curl. If you try to build SuperBuild with a standalone CMake binary, you won't have this issue.
It comes from the fact that in SuperBuild, Cmake command is always prefixed by LD_LIBRARY_PATH=SuperBuild_install_dir/lib , so libssl.so becomes visible.
I need to check if we can't avoid this LD_LIBRARY_PATH ...
Thanks Guillaume, I think that you've reached the end point of the Superbuild as one fix for this issue would be to compile cmake in the OTB Superbuild :)
// end sacarsm
I know that slicer superbuild include curl and openssl but I don't found if they faced the same issue:
I have pushed a fix on release-6.2 :
We will check on dashboard if it has side effect. Maybe this LD_LIBRARY_PATH was here to handle cases where we mix system and superbuild libs, so I am not 100% sure there won't be any regressions. After this patch, I have compiled a SuperBuild on 3 different platforms and nothing seemed broken.
|Thanks. I confirm that it solves the issue on ly side. I think we can mark this one as solved.|
|2017-10-10 10:04||grizonnetm||New Issue|
|2017-10-10 10:04||grizonnetm||File Added: CURL-configure-err.log|
|2017-10-10 10:17||rashadkm||Note Added: 0004358|
|2017-10-10 10:43||gpasero||Assigned To||=> gpasero|
|2017-10-10 10:43||gpasero||Status||new => assigned|
|2017-10-10 10:49||gpasero||Note Added: 0004359|
|2017-10-10 11:34||grizonnetm||Note Added: 0004360|
|2017-10-10 11:54||gpasero||Note Added: 0004361|
|2017-10-10 16:44||gpasero||Note Added: 0004362|
|2017-10-11 08:19||grizonnetm||Note Added: 0004364|
|2017-10-11 09:36||grizonnetm||Priority||normal => urgent|
|2017-10-13 18:19||gpasero||Note Added: 0004375|
|2017-10-18 08:21||grizonnetm||Note Added: 0004394|
|2017-10-18 09:05||gpasero||Status||assigned => resolved|
|2017-10-18 09:05||gpasero||Resolution||open => fixed|
|2017-10-18 09:10||grizonnetm||Status||resolved => closed|
|Copyright © 2000 - 2017 MantisBT Team|