> Forgive me if I missed it, but I don't think you've submitted a ssh key.
Yes, that is correct. In further testing during the time between the sending of the ITP email and the subsequent approval, I discovered that some executables built using GCC 15.1 would encounter strange errors during runtime and cause the build to fail. I was eventually able to isolate this to an error in GCC -O2 optimizations (isseus are not observed with -O1). While Cygwin GCC package is not yet at version 15, I did want to try to understand the scope of the issue. Since then, I have been working to setup the Cygport Workflow Template on GitHub. (The process to get to the point of the GCC-induced error during the build is somewhat long.) From a maintenance perspective, this Cygport Workflow Template should also be of help, as the workflow is also setup to run on a weekly basis, so if any breaking changes are introduced by newer software versions, they hopefully should be able to be caught and flagged more quickly. I also then tested that template with a few other Cygport packages to hopefully make it a little more robust. Cygport Workflow Template Repository * https://github.com/mesheets/Cygport-Workflow-Template Examples: * https://github.com/mesheets/hello.cygport * https://github.com/mesheets/flac.cygport * https://github.com/BrickBot/h8300-hitachi-coff-toolchain.cygport * https://github.com/BrickBot/nqc.cygport At any rate, I am hoping to get back to the h8300-hitachi-coff-toolchain Cygport package process… :-) Thank you, Matthew
