Closed GoogleCodeExporter closed 9 years ago
Hi Stefan,
The problem here is not ceres, but a faulty suitesparse install on ubuntu.
There are two ways around it.
1. Build your own suitesparse with the proper shared library flags.
2. Turn off shared library building in ceres. You can do this via
cmake -DBUILD_SHARED=OFF
and the problem should go away.
Please let me know if this works for you.
Original comment by sameerag...@google.com
on 13 Aug 2013 at 9:55
Hi Sameer,
thanks for the quick answer! I tried option 1.) and after working around some
undefined reference errors due to 'clock_gettime' in some suitesparse part
(resolved by adding -lrt to the end of target_link_libraries for ceres), it now
works fine.
regards,
Stefan
Original comment by Stefan.K...@gmail.com
on 14 Aug 2013 at 8:08
Happy to help.
Interesting about the target link libraries, I am not sure why we haven't faced
that problem in the past. Perhaps on ubuntu the high precision timer support is
not compiled into suitesparse by default?
I am closing this issue as wontfix for now. As there is nothing I can do about
it at the level of ubuntu.
Original comment by sameerag...@google.com
on 14 Aug 2013 at 2:01
This has now been fixed in master at 54b43fefeacc785f46b40f3b022813922d9ae9f3
with the caveat that a newer version of SuiteSparse than is shipped with Ubuntu
(currently 3.4.0 as of 13.10) is still required.
I tested it with a source install of SuiteSparse v4.2.1 (default options) on
Ubuntu 12.10 and everything works (irrespective of whether Ceres is compiled
statically or dynamically).
Original comment by alexs....@gmail.com
on 3 Oct 2013 at 8:21
Original issue reported on code.google.com by
Stefan.K...@gmail.com
on 13 Aug 2013 at 8:14