Changes between Initial Version and Version 1 of Ticket #70641, comment 23


Ignore:
Timestamp:
Sep 18, 2024, 3:53:57 PM (39 hours ago)
Author:
BarneyStratford
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #70641, comment 23

    initial v1  
    1 I've experienced the same problem on port gcc14 as on libgcc14. "configure.pipe no" fixes the problem for me on both ports using macOS 15.0.
     1I've experienced the same problem on port gcc14 as on libgcc14. You can work around it for now on all ports affected by this bug by appending the following to /opt/local/etc/macports/macports.conf:
     2
     3configurepipe no