4 | | {{{ |
5 | | Thanks for pointing out that --enable-fully-dynamic-string issue. It's not actually the case that you think (incompatibility with the host). The problem seems to be that some of MacPorts' gcc compilers have been built with --enable-fully-dynamic-string and others haven't. gcc44 and gcc45 are built with --enable-fully-dynamic-string and gcc46, gcc47, and gcc48 aren't, so gcc44 and gcc45 aren't compatible with the libstdcxx that is built from gcc47 because of this difference. |
| 4 | > Thanks for pointing out that --enable-fully-dynamic-string issue. It's not actually the case that you think (incompatibility with the host). The problem seems to be that some of MacPorts' gcc compilers have been built with --enable-fully-dynamic-string and others haven't. gcc44 and gcc45 are built with --enable-fully-dynamic-string and gcc46, gcc47, and gcc48 aren't, so gcc44 and gcc45 aren't compatible with the libstdcxx that is built from gcc47 because of this difference. |
| 5 | > |
| 6 | > I think we should try having users experiencing issues with octave-devel using gcc44 and gcc45 rebuild the compiler without --enable-fully-dynamic-string to see if that solves that particular issue... |