CGAL users discussion list

[Philipp Moeller <>]

Ruud Vlaming 
<>
 writes:

> On 22-05-13 22:03, Marc Glisse wrote:
>> On Wed, 22 May 2013, Ruud Vlaming wrote:
>> 
>>> There seems to be unknown symbols called from CGAL, but also from
>>> other object files.  What is causing this is not clear to me yet. The
>>> question is of course, is this still a CGAL problem? If not, i should
>>> not bother you with this, i guess.
>> 
>> Are you sure the various libraries (CGAL, boost, etc) were all compiled 
>> with clang using the same -stdlib option?
>
> No, i am not, for i did not compile these libs by 
> hand (macports did). I assumed the make script would 
> take care of incompatibilities if needed. If this is not
> the case, it is going to pose a problem, for other 
> programs may require libraries files with other 
> compiler switches again.

Binary incompatibility between C++11/C++03 code is a really difficult
problem to solve in a build system, especially when you rely on some
automated packaging system to make choices for you.

>
>
> It seems i must use local copies of all dependencies, 
> and compile them separately. Hmm, this is going to 
> take much more time than anticipated ...

Not necessarily. You can instruct MacPorts to always pass -std=c++11
through the configure.cxxflags [1] option and go for a full rebuild of
the dependencies. You can also use this to ensure the correct stdlib
option is set.

>
>
>
> What is the standard way of handling this? Up to now
> i did not have any problems when using for example
> boost and c++11.

Most of Boost is not compiled, but you will already run into problems
when trying to link against Boost.FileSystem [2].


Footnotes: 
[1]  http://guide.macports.org/#reference.phases.configure
[2]  https://svn.boost.org/trac/boost/ticket/6779