Ludovic Courtès <[email protected]> writes: > Hi, > > Christopher Baines <[email protected]> skribis: > >> It seems to build for me, but I'm having problems cross building. There >> were warnings before about protocol/ssl3 being undefined, but now this >> seems to result in an error when building extra.scm: >> >> >> GUILEC modules/gnutls.go >> gnutls.scm:608:23: warning: possibly unbound variable `protocol/ssl3' >> gnutls.scm:609:25: warning: possibly unbound variable `protocol/tls1-0' >> gnutls.scm:610:25: warning: possibly unbound variable `protocol/tls1-1' >> GUILEC modules/gnutls/extra.go > > [...] > >> ice-9/boot-9.scm:1685:16: In procedure raise-exception: >> Unbound variable: protocol/ssl3 >> make[3]: *** [Makefile:1295: modules/gnutls/extra.go] Error 1 > > Is it a regression or did we already have that problem?
A regression I think, the data service doesn't have recent data, but it does know about builds that worked: https://data.guix.gnu.org/repository/1/branch/master/package/guile-gnutls/output-history?output=out&system=x86_64-linux&target=riscv64-linux-gnu > That comes from this bit in (gnutls): > > ;; Renaming. > (define protocol/ssl-3 protocol/ssl3) > (define protocol/tls-1.0 protocol/tls1-0) > (define protocol/tls-1.1 protocol/tls1-1) > > When cross-compiling, the .so cannot be loaded (understandably; see also > GNUTLS_GUILE_CROSS_COMPILING) so ‘protocol/ssl3’ above is undefined. > The problem is that when compiling (gnutls extra), we end up loading > (gnutls) and thus evaluating the lines above, which fail. > > In Guile-Avahi I worked around it like so: > > (define protocol/unspecified > (and (defined? 'protocol/unspec) protocol/unspec)) > > I guess we could do that as well That sort of makes sense, although I don't know why this wasn't failing in the same way in the past. Build logs are available though, so maybe this makes sense to someone.
signature.asc
Description: PGP signature
