bug#37371: CMake’s “ctest” doesn’t know about X.509 certificates

2019-09-10 Thread Ludovic Courtès
Hello, Tobias Geerinckx-Rice skribis: > Ricardo Wurmus 写道: >> This is the correct way, in my opinion. The user of libcurl is >> supposed >> to handle environment variable lookup. > > I'm aware of this, but it seems like some users don't do this. I’ve pushed this as

bug#37371: CMake’s “ctest” doesn’t know about X.509 certificates

2019-09-10 Thread Tobias Geerinckx-Rice via Bug reports for GNU Guix
Ricardo, Ricardo Wurmus 写道: This is the correct way, in my opinion. The user of libcurl is supposed to handle environment variable lookup. I'm aware of this, but it seems like some users don't do this. On #guix, Tobias also rightfully suggested adding a ‘getenv’ call directly in libcurl,

bug#37371: CMake’s “ctest” doesn’t know about X.509 certificates

2019-09-10 Thread Ricardo Wurmus
Ludovic Courtès writes: > The ‘ctest’ command uses libcurl to submit reports to CDash servers. > However, it does not “getenv” anything related to CA certs, and it does > not either look at /etc/ssl/certs. […] > > For now I propose to provide a patched ‘cmake’ package that does the > right

bug#37371: CMake’s “ctest” doesn’t know about X.509 certificates

2019-09-10 Thread Ludovic Courtès
Hello, The ‘ctest’ command uses libcurl to submit reports to CDash servers. However, it does not “getenv” anything related to CA certs, and it does not either look at /etc/ssl/certs. The culprit is this function: --8<---cut here---start->8--- std::string