Builder curl-ares-solaris11-sparc Build #4114

Results:

Build successful

SourceStamp:

BuildSlave:

Reason:

The SingleBranchScheduler scheduler named 'schedule-curl-ares-solaris11-sparc' triggered this build

Steps and Logfiles:

1. git update ( 2 secs )
   1. stdio
2. Runtest './tests/testcurl.pl --nogitpull ...' ( 25 mins, 28 secs )
   1. stdio
   2. resultlog
3. Mail result 'cat resultlog ...' ( 0 secs )
   1. stdio

Build Properties:

Forced Build Properties:

Responsible Users:

1. Joel Depooter

   joel.depooterohnoyoudont@safe.com

Timing:

All Changes:

:

1. Change #237646

   Category	curl
   Changed by	Joel Depooter <joel.depooterohnoyoudont@safe.com>
   Changed at	Tue 24 Jun 2025 09:57:42
   Repository	https://github.com/curl/curl.git
   Project	curl
   Branch	master
   Revision	c153d9eadf41c894f71ece3dd4355c1990e08b97

   Comments

   cmake: check USE_WINDOWS_SSPI when adding secur32 to CURL_LIBS
   Instead of CURL_WINDOWS_SSPI.
   
   When running CMake on Windows with no additional parameters (ie default
   build configuration), the generated project files do not include the
   `secur32.lib` library in the linker settings. This is because
   the relevant check was looking at `CURL_WINDOWS_SSPI` instead of
   `USE_WINDOWS_SSPI`.
   
   `USE_WINDOWS_SSPI` is enabled when building with SChannel (the default
   on Windows), or if `CURL_WINDOWS_SSPI` is specified on the command line.
   
   Follow-up to 0d71b18153c8edb996738f8a362373fc72d0013b #17413
   
   Closes #17728

   Changed files

   • CMakeLists.txt