#7 compiling on linux with guile 3

Suljettu
4 vuotta sitten avasi tch70 · 3 kommenttia
tch70 kommentoitu 4 vuotta sitten

The module doesn't compile on linux with guile 3 without modifications, right? I'm attaching my kludge for the problem:

The module doesn't compile on linux with guile 3 without modifications, right? I'm attaching my kludge for the problem:
tch70 kommentoitu 4 vuotta sitten
Tekijä

What can I upload, then? Here's the patch inline, then (accessible from editing/source view):

--- configure.ac.prev ^2020-05-23 13:23:29.000000000 +0300 +++ configure.ac ^2020-09-24 22:51:46.250648180 +0300 @@ -27,6 +27,14 @@ LIBGCRYPT_LIBDIR="no" LIBGCRYPT_PREFIX="no" . +if test "x$GUILD" = "x"; then

  • GUILD="pkg-config guile-3.0 --variable=guild"
  • if test "x$GUILD" = "x"; then
  • AC_MSG_ERROR(['guild' binary not found; please check your Guile installation.])
  • fi
  • AC_SUBST([GUILD]) +fi + AC_ARG_WITH([libgcrypt-prefix], [AS_HELP_STRING([--with-libgcrypt-prefix=DIR], [search for GNU libgcrypt in DIR])], [case "$withval" in
What can I upload, then? Here's the patch inline, then (accessible from editing/source view): --- configure.ac.prev ^2020-05-23 13:23:29.000000000 +0300 +++ configure.ac ^2020-09-24 22:51:46.250648180 +0300 @@ -27,6 +27,14 @@ LIBGCRYPT_LIBDIR="no" LIBGCRYPT_PREFIX="no" . +if test "x$GUILD" = "x"; then + GUILD="`pkg-config guile-3.0 --variable=guild`" + if test "x$GUILD" = "x"; then + AC_MSG_ERROR(['guild' binary not found; please check your Guile installation.]) + fi + AC_SUBST([GUILD]) +fi + AC_ARG_WITH([libgcrypt-prefix], [AS_HELP_STRING([--with-libgcrypt-prefix=DIR], [search for GNU libgcrypt in DIR])], [case "$withval" in
civodul kommentoitu 2 vuotta sitten
Yhteistyökumppani

Hi @tch70 and apologies for the delay.

Guile-Gcrypt 0.3.x definitely builds with Guile 3.0 so I'm not sure what problem you encountered. Could you check if it still applies and describe the issue itself?

Hi @tch70 and apologies for the delay. Guile-Gcrypt 0.3.x definitely builds with Guile 3.0 so I'm not sure what problem you encountered. Could you check if it still applies and describe the issue itself?
tch70 kommentoitu 2 vuotta sitten
Tekijä

I don't remember why that AC fragment happened to be needed 2 years ago and more, how this fragment helped. The 2-years old build dir remains and config.log shows there was .nix-profile sitting first in the path. Maybe that was the cause. I don't have that .nix-profile anymore, so can't check.

On my today's system (updated, no nix stuff) both 0.3.0 and 0.4.0 build okay. Let's consider the issue resolved.

I don't remember why that AC fragment happened to be needed 2 years ago and more, how this fragment helped. The 2-years old build dir remains and config.log shows there was .nix-profile sitting first in the path. Maybe that was the cause. I don't have that .nix-profile anymore, so can't check. On my today's system (updated, no nix stuff) both 0.3.0 and 0.4.0 build okay. Let's consider the issue resolved.
Kirjaudu sisään osallistuaksesi tähän keskusteluun.
Ei tunnistetta
Ei merkkipaalua
Ei osoitettua
2 osallistujaa
Ladataan...
Peruuta
Tallenna
Sisältöä ei vielä ole.