Changes between Initial Version and Version 1 of Ticket #54215, comment 46


Ignore:
Timestamp:
Oct 10, 2017, 11:57:34 AM (7 years ago)
Author:
ccorn
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #54215, comment 46

    initial v1  
    1 One more remark to the experimental `defaultabi4` and `staticlibgcc` variants: On my G5 (Darwin 9/PPC), `+defaultabi` does //not// prevent the previously described crashes (or rather endless unwind loops) of e.g. `octave-gui` and the `botan`-linked `monotone`. I still have to use `+staticlibgcc` to get those ports running fine.
     1One more remark to the experimental `defaultabi4` and `staticlibgcc` variants: On my G5 (Darwin 9/PPC), `+defaultabi4` does //not// prevent the previously described crashes (or rather endless unwind loops) of e.g. `octave-gui` and the `botan`-linked `monotone`. I still have to use `+staticlibgcc` to get those ports running fine.
    22
    33I have run tests for `gcc6` and `gcc7` with both variants enabled together. The test results do not differ from those with `+staticlibgcc` alone. As described earlier, this means 24 more `g++` testsuite failures than without `+staticlibgcc`. (I had entertained the dim hope that `+defaultabi4` would make those test failures go away, but alas.) On the other hand I can use `monotone` and `octave-gui` again, which is what counts for me.