Re: Scallywag Mingw64 source build faile with undefined or explicit noarch ARCH

On 09/08/2026 04:08, Brian Inglis via Cygwin-apps wrote:
> Hi folks,
> 
> Trying to update mingw64 x86_64 libevent build in Scallywag, source 
> build fails whether ARCH is undefined or explicitly defined as noarch.

Thanks for reporting this.

> scallywag: parsing cygport /cygdrive/d/a/scallywag/mingw64-x86_64- 
> libevent/mingw64-x86_64-libevent.cygport
> scallywag: BUILD_REQUIRES="
>      mingw64-$XARCH-openssl mingw64-$XARCH-binutils mingw64-$XARCH-gcc-core
>      doxygen libtool
> "
> scallywag: CROSS_HOST="$XARCH-w64-mingw32"
> scallywag: ARCHES="all"
> scallywag: INHERITED=" cross "
> scallywag: build dependencies (from BUILD_REQUIRES): 
> doxygen,libtool,mingw64-$XARCH-binutils,mingw64-$XARCH-gcc-core,mingw64- 
> $XARCH-openssl
> scallywag: cross_host: $XARCH-w64-mingw32, pkg_prefix is unknown

Hmm.. it seems like this was meant to be a fatal error (so ARCHES is 
undefined later on), even though we didn't report it as such, and 
perhaps it shouldn't be.

I've pushed a change to handle this more liberally.

Things still don't build because we try to install packages named 
literally 'mingw64-$XARCH-gcc-core', etc. and then fail because the 
needed cross-compiler isn't installed.

(This is really a cygport bug, since 'cygport vars' is failing because 
cygport insists on checking for the presence of the cross-compiler (even 
though it's not needed for that command and causes a chicken-and-egg 
situation in determining the BUILD_REQUIRES), so scallywag falls back to 
trying to parse BUILD_REQUIRES out the cygport instead, which doesn't 
give the right answer here)