On 2/12/2025 12:42 PM, ASSI via Cygwin wrote:
Ken Brown via Cygwin writes:
On 2/11/2025 4:03 PM, Corinna Vinschen via Cygwin wrote:
Ken, check the source or configury of your package. It looks weird that
this function should be called architecture-independently.
Thanks for the suggestion. It's actually not called
architecture-independently, but the code was convoluted and I didn't
see at first what was going on. It turns out that I just had to add
"#if !defined(__CYGWIN__)" at the right place and the build succeeded.
It still seems wierd and brittle to hinge this decision on a platform
macro rather than a test result from configury.
I agree, and I already sent that opinion upstream. No answer so far.
Ken
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation: https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
