Hi,
I just tries to build stunnel 5.20 on Solaris 10 Sparc and noticed a strange behaviour
during „make check“ which yields in a try to build Windows executables:
>dam at unstable10s [unstable10s]:/home/dam/mgar/pkg/stunnel/trunk/work/solaris10-sparc/build-isa-sparcv8plus/stunnel-5.20 > gmake check
> Making check in src
> gmake[1]: Entering directory '/home/dam/mgar/pkg/stunnel/trunk/work/solaris10-sparc/build-isa-sparcv8plus/stunnel-5.20/src'
> gmake stunnel.exe tstunnel.exe
> gmake[2]: Entering directory '/home/dam/mgar/pkg/stunnel/trunk/work/solaris10-sparc/build-isa-sparcv8plus/stunnel-5.20/src'
> i686-w64-mingw32-gcc -c -I/usr/src/openssl-1.0.2d-i686/include -mthreads -fstack-protector -O2 -Wall -Wextra -Wpedantic -Wformat=2 -Wconversion -Wno-long-long -D_FORTIFY_SOURCE=2 -DUNICODE -D_UNICODE -o tls.obj tls.c
> /bin/bash: i686-w64-mingw32-gcc: command not found
> Makefile:1206: recipe for target 'tls.obj' failed
> gmake[2]: *** [tls.obj] Error 127
> gmake[2]: Leaving directory '/home/dam/mgar/pkg/stunnel/trunk/work/solaris10-sparc/build-isa-sparcv8plus/stunnel-5.20/src'
> Makefile:1054: recipe for target 'check-am' failed
I think this comes from these lines in src/Makefile.am:
> # Just check if the programs can be built, don't perform any actual tests
> check_PROGRAMS = stunnel.exe tstunnel.exe
Essentially the „check“ phase could just not be called during build, but it
would be cleaner to not bail out on Unix.
Best regards
— Dago
--
"You don't become great by trying to be great, you become great by wanting to do something,
and then doing it so hard that you become great in the process." - xkcd #896
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2418 bytes
Desc: not available
URL: <http://www.stunnel.org/pipermail/stunnel-users/attachments/20150712/d11c4fee/attachment.bin>