error in destroot for clang-3.8 +universal

Ryan Schmidt ryandesign at macports.org
Wed Sep 2 13:06:25 PDT 2015


On Sep 2, 2015, at 1:44 PM, Michael Dickens wrote:

> Can't search Trac so here it is; sorry about any duplication! I no
> longer have the build log to see how this library was created in the
> first place (e.g., with "-headerpad_max_install_names" or the like). -
> MLD
> 
> {{{
> :info:destroot llvm[2]: Installing compiler runtime library:
> darwin/asan_osx_dynamic
> :info:destroot /usr/bin/install -c -m 0644
> /opt/local/var/macports/build/_opt_source_MacPorts_trunk_dports_lang_llvm-3.8/clang-3.8/work/build/Release+Debug+Asserts/lib/clang/3.8.0/lib/darwin/libclang_rt.asan_osx_dynamic.dylib
> /opt/local/var/macports/build/_opt_source_MacPorts_trunk_dports_lang_llvm-3.8/clang-3.8/work/destroot/opt/local/libexec/llvm-3.8/lib/clang/3.8/lib/darwin
> :info:destroot install_name_tool
> /opt/local/var/macports/build/_opt_source_MacPorts_trunk_dports_lang_llvm-3.8/clang-3.8/work/destroot/opt/local/libexec/llvm-3.8/lib/clang/3.8/lib/darwin/libclang_rt.asan_osx_dynamic.dylib
> -id
> /opt/local/libexec/llvm-3.8/lib/clang/3.8/lib/darwin/libclang_rt.asan_osx_dynamic.dylib
> :info:destroot error: install_name_tool: changing install names or
> rpaths can't be redone for:
> /opt/local/var/macports/build/_opt_source_MacPorts_trunk_dports_lang_llvm-3.8/clang-3.8/work/destroot/opt/local/libexec/llvm-3.8/lib/clang/3.8/lib/darwin/libclang_rt.asan_osx_dynamic.dylib
> (for architecture i386) because larger updated load commands do not fit
> (the program must be relinked, and you may need to use -headerpad or
> -headerpad_max_install_names)
> :info:destroot make[2]: ***
> [/opt/local/var/macports/build/_opt_source_MacPorts_trunk_dports_lang_llvm-3.8/clang-3.8/work/destroot/opt/local/libexec/llvm-3.8/lib/clang/3.8/lib/darwin/libclang_rt.asan_osx_dynamic.dylib]
> Error 1
> }}}

The intention is that all ports link with -headerpad_max_install_names -- it is in the default configure.ldflags, since a couple years ago -- however, any port could of course ignore or override that.




More information about the macports-dev mailing list