Changes between Initial Version and Version 1 of Ticket #38938, comment 5


Ignore:
Timestamp:
Apr 26, 2013, 6:39:46 PM (11 years ago)
Author:
kasper.peeters@…
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #38938, comment 5

    initial v1  
    11Yes, I meant llvm-gcc.
    22
    3 I don't necessarily need apple-gcc-4.2, it can be any later version, but it has to be the apple one otherwise the resulting binary gets linked to two different libstdc++ libraries and that leads to all sorts of malloc errors. Or at least I did not figure out a way to use a non-apple-gcc compiler without running into this problem.
     3I don't necessarily need apple-gcc-4.2, it can be any later version, but it has to be the apple one otherwise the resulting binary gets linked to two different libstdc++ libraries and that leads to all sorts of malloc errors. Or at least I did not figure out a way to use a non-apple-gcc compiler without running into this problem.
     4
     5I have gcc-4.2 here as well, but if I remember correctly that also produced the double-libstdc++ problem.
    46
    57So my question is really: how do I restrict to apple-gcc without restricting to a specific version?
    68
    7 (It took me quite some time to pin this down. It may thus be a good idea to discuss this problem somewhere more prominently on the Macports pages that discuss compiler choices, as I am apparently not the only one puzzled by these weird malloc errors).
     9(It took me quite some time to pin this down. It may thus be a good idea to discuss this problem somewhere more prominently on the Macports pages that discuss compiler choices, as I am apparently not the only one puzzled by these weird malloc errors. In general, as soon as you start excluding the default C++ compiler, all hell breaks loose...).