#47754: Vigra @1.10.0_6 build fails -------------------------+------------------------------- Reporter: macports@… | Owner: benjamin.seppke@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: Port: vigra | -------------------------+------------------------------- Changes (by ryandesign@…): * owner: macports-tickets@… => benjamin.seppke@… -- Ticket URL: <https://trac.macports.org/ticket/47754#comment:1> MacPorts <https://www.macports.org/> Ports system for OS X

#47754: Vigra @1.10.0_6 build fails -------------------------+------------------------------- Reporter: macports@… | Owner: benjamin.seppke@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: Port: vigra | -------------------------+------------------------------- Comment (by mmoll@…): I can reproduce the problem, but at the same time I can see that the symbol *is* defined in libc++: {{{

nm /usr/lib/libc++.dylib |c++filt|grep ::widen\(char\) 000000000000a7e4 unsigned short std::__1::basic_ios<char, std::__1::char_traits<char> >::widen(char) const 000000000000af16 unsigned short std::__1::basic_ios<wchar_t, std::__1::char_traits<wchar_t> >::widen(char) const }}}

-- Ticket URL: <https://trac.macports.org/ticket/47754#comment:3> MacPorts <https://www.macports.org/> Ports system for OS X

#47754: Vigra @1.10.0_6 build fails -------------------------+------------------------------- Reporter: macports@… | Owner: benjamin.seppke@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: Port: vigra | -------------------------+------------------------------- Comment (by benjamin.seppke@…): ... after one day of intense testing and monitoring, I eventually found some reason for the error! The error of this subject is more or less a clang error. The symbol is just not defined in the libc++ of clang++. Thus, we get the compiler/linker error during the compilation of the module. The (forced) setting to -stdlib=libstc++ temporary solves *this* issue, but hinders other things like the boost::python bindings to compile. When using the gcc/g++ compiler the error does not arise, since all symbols are defined here. And this is also the reason, why I was able to compile the vigra in my previous posting here. Another possibility is to compile the vigra library using Clang but without HDF5 (-DWITH_HDF5=NO), which also works fine but really reduces the usability of the library... So, what du you think? The easiest way would be *not* to use CLang here... -- Ticket URL: <https://trac.macports.org/ticket/47754#comment:6> MacPorts <https://www.macports.org/> Ports system for OS X

#47754: Vigra @1.10.0_6 build fails -------------------------+------------------------------- Reporter: macports@… | Owner: benjamin.seppke@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: Port: vigra | -------------------------+------------------------------- Comment (by benjamin.seppke@…): Hello, you are right - and I was still confused regarding my last post. I edited it to avois any confusion here. The error arises for the error (?!) inside the cmake defaults w.r.t. the clang++ build chain. In the default setting, this results in a CMakeCache.txt build config for Release like: {{{ CMAKE_CXX_FLAGS_RELEASE -pipe -Os -DNDEBUG }}} In the -Os optimization level some symbols of the std c++ lib are somehow lost. But if you replace the -Os with e.g. -O3 optimization, it compiles just as expected. I have appended a Portfile-patch to this ticket, which solves this issue for me. Feel free to try it out and - if successful - please patch the macports Portfile for me. Unfortunately, I don't have write priviledges there. -- Ticket URL: <https://trac.macports.org/ticket/47754#comment:8> MacPorts <https://www.macports.org/> Ports system for OS X

#47754: vigra @1.10.0_6 build fails with -Os -------------------------+------------------------------- Reporter: macports@… | Owner: benjamin.seppke@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: fixed | Keywords: Port: vigra | -------------------------+------------------------------- Changes (by ryandesign@…): * cc: ryandesign@… (added) Comment: Replying to [comment:8 benjamin.seppke@…]:

In the -Os optimization level some symbols of the std c++ lib are somehow lost. But if you replace the -Os with e.g. -O3 optimization, it compiles just as expected.

I haven't heard of anything like that before, but if that's true, then that's bizarre. Have you reported that problem to anyone else—the llvm project, for example, or Apple? `-Os` is the optimization level Apple uses to compile the software you get as part of OS X, so it's the optimization level that should be best-tested by Apple, who are also developers of llvm and clang and libc++, which is why MacPorts switched its default optimization level to `-Os` to match. If there is a problem with llvm/clang/libc++ and `-Os` I would very much like to know it, as probably would Apple. -- Ticket URL: <https://trac.macports.org/ticket/47754#comment:10> MacPorts <https://www.macports.org/> Ports system for OS X