Changes between Initial Version and Version 1 of Ticket #36103, comment 30


Ignore:
Timestamp:
Sep 14, 2012, 5:41:33 AM (12 years ago)
Author:
jeremyhu (Jeremy Huddleston Sequoia)
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #36103, comment 30

    initial v1  
    22
    33Regarding the malloc issue, from my email just now to macports-dev:
    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...
    67
    7 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...
    8 }}}
    98