Hi,
Dave Horsfall wrote:
We can't guess what the problem is. Please file a bug report and
attach the compressed main.log.
I like to make sure that I'm not duplicating a bug report -- how do
*you* go bug-hunting? -- but OK, one hidously-long filename
"main.log.gz" attached...
In the meantime, you seem to have missed the other part of my message,
viz: how do I *not* recompile GCC? That will bring this old MacBook to
its knees, and I have better things to do with it than have character
echo times measured in seconds...
to my untrained eyes it looks like it is trying to rebuild gcc49, that
it is using clang which spits out lots of warnings and the stage-1
generated compiler itself then files to execute properly
The fatal error is:
:info:build In file included from
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc49/gcc49/work/gcc-4.9.4/gcc/c/c-objc-common.c:33:
:info:build In file included from
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/new:89:
:info:build
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/exception:173:5:
error: no member named 'fancy_abort' in namespace 'std::__1'; did you
mean simply 'fancy_abort'?
:info:build _VSTD::abort();
:info:build ^~~~~~~
:info:build
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/__config:392:15:
note: expanded from macro '_VSTD'
:info:build #define _VSTD std::_LIBCPP_NAMESPACE
coulkd this be due to the latest C++ fixes of macports?
Riccardo
