unhandled C++ exceptions not propagating

I was just debugging a c++ app (b2 build system from boost), and noticed that it would appear to exit unexpectedly without an error. This turned out to be when an unhandled C++ exception was thrown. On a fresh install of cygwin with gcc-g++, this program will throw an exception from the std::st

Re: unhandled C++ exceptions not propagating

Takashi Yano writes: > On Sat, 15 Aug 2020 20:38:01 -0300 > David McFarland via Cygwin wrote: >> >> I was just debugging a c++ app (b2 build system from boost), and noticed >> that it would appear to exit unexpectedly without an error. This turned >> out to be w

[PATCH 0/1] libbrotli has broken pkg-config

I'm a little lost on the exact process for sending patches for packages, so excuse me if I'm in the wrong place. I found this problem when trying to build something that depends on libbrotli. This patch pulls the fix from this PR: https://github.com/google/brotli/pull/838 David McFarland (1): c

[PATCH 1/1] cherry-pick fix for pkg-config

This PR removes a recently added -R/usr/lib from the linker flags, which is incompatible with gcc: $ cc $(pkg-config --libs libbrotlidec) cc: error: unrecognized command-line option ‘-R’ --- brotli.cygport | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/brotli.cygpor

setup: --prune-install appears to be broken

If I do a base install to a new root: setup-x86_64.exe --root "$(cygpath -wa .cygtest)" --no-admin \ --no-shortcuts --no-replaceonreboot --no-version-check \ --prune-install --verbose And then run the same install again, I get: libsolv: orphaned packages: libsolv:

Re: setup: --prune-install appears to be broken

> You are misunderstanding what prune-install does: it ensures that only > the exact list of groups/packages that you give it for installation > (plus their dependencies) is installed when it finishes and you > literally said you want to end up with no packages at all. That's not what it's doing