On 19/04/2025 19:41, Jeremy Drake via Cygwin-apps wrote:
On Sat, 19 Apr 2025, Brian Inglis via Cygwin-apps wrote:
That kind of thing would have to happen in the local Cygport or Scallywag CI
Windows environment, as the calm infrastructure is Fedora.
Could we use gendef and nm/objdump to compare Cygwin definitions and uses, or
is there some loader function to display unresolved symbols, or the Cygwin ABI
required?
You might be interested in my
https://github.com/jeremyd2019/package-grokker action. MSYS2 uses it to
detect when rebuilds due to ABI breakage are required. A good amount of
it walks dependency trees from the pacman package databases, but the bits
using pefile to match up PE imports and exports would be relevant to
Cygwin also. If it were taught Cygwin's package metadata, it could
probably do the same for Cygwin. PRs welcome ;)
Ah, something like that would be lovely :)
Although I'm not sure it would help in this specific case, where an
idiot has forced an incompatible set of packages to be installed?
