./configure fails when building Guix

./configure fails when building Guix

[HiPhish]

Hello everyone,

I am trying to set up Guix for proper local development, but it fails during 
the configuration step because the script cannot find the guild binary. Here is 
what I did:

- Check out the Guix repo
- Switch to a local branch
- run `guix environment guix` in order to set up all dependiencies
- run `./bootstrap`
- run `./configure`

Here is the output of `./bootstrap`:

guix$ ./bootstrap
+ find po/doc -type f -name *.po
+ sed -e s,guix-manual\.,,
+ xargs -n 1 -I{} basename {} .po
+ langs=zh_CN
de
ru
es
fr
+ [ ! -e doc/guix.zh_CN.texi ]
+ [ ! -e doc/guix.de.texi ]
+ [ ! -e doc/guix.ru.texi ]
+ [ ! -e doc/guix.es.texi ]
+ [ ! -e doc/guix.fr.texi ]
+ exec autoreconf -vfi
autoreconf: Entering directory `.'
autoreconf: running: autopoint --force
autoreconf: running: aclocal --force -I m4
autoreconf: configure.ac: tracing
autoreconf: configure.ac: not using Libtool
autoreconf: running: /gnu/store/rfaqi3a9ls7adr4y7bgwvln3iaf69qwj-
autoconf-2.69/bin/autoconf --force
autoreconf: running: /gnu/store/rfaqi3a9ls7adr4y7bgwvln3iaf69qwj-
autoconf-2.69/bin/autoheader --force
autoreconf: running: automake --add-missing --copy --force-missing
configure.ac:23: warning: The 'AM_PROG_MKDIR_P' macro is deprecated, and its 
use is discouraged.
configure.ac:23: You should use the Autoconf-provided 'AC_PROG_MKDIR_P' macro 
instead,
configure.ac:23: and use '$(MKDIR_P)' instead of '$(mkdir_p)'in your Makefile.am 
files.
Makefile.am:601: warning: AM_GNU_GETTEXT used but 'po' not in SUBDIRS
autoreconf: Leaving directory `.'

And here is the output of `./configure`:

guix$ ./configure
checking for a BSD-compatible install... /gnu/store/
020aw068yfsq84h6scmnvfrjacmznsgz-profile/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /gnu/store/
020aw068yfsq84h6scmnvfrjacmznsgz-profile/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether make supports nested variables... (cached) yes
checking whether make supports the include directive... yes (GNU style)
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking dependency style of gcc... gcc3
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /gnu/store/
020aw068yfsq84h6scmnvfrjacmznsgz-profile/bin/grep
checking for egrep... /gnu/store/020aw068yfsq84h6scmnvfrjacmznsgz-profile/bin/
grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking minix/config.h usability... no
checking minix/config.h presence... no
checking for minix/config.h... no
checking whether it is safe to define __EXTENSIONS__... yes
checking whether NLS is requested... yes
checking for msgfmt... /gnu/store/020aw068yfsq84h6scmnvfrjacmznsgz-profile/bin/
msgfmt
checking for gmsgfmt... /gnu/store/020aw068yfsq84h6scmnvfrjacmznsgz-profile/
bin/msgfmt
checking for xgettext... /gnu/store/020aw068yfsq84h6scmnvfrjacmznsgz-profile/
bin/xgettext
checking for msgmerge... /gnu/store/020aw068yfsq84h6scmnvfrjacmznsgz-profile/
bin/msgmerge
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking for ld used by GCC... /gnu/store/020aw068yfsq84h6scmnvfrjacmznsgz-
profile/bin/ld
checking if the linker (/gnu/store/020aw068yfsq84h6scmnvfrjacmznsgz-profile/
bin/ld) is GNU ld... yes
checking for shared library run path origin... done
checking for CFPreferencesCopyAppValue... no
checking for CFLocaleCopyCurrent... no
checking for GNU gettext in libc... yes
checking whether to use NLS... yes
checking where the gettext function comes from... libc
checking for sed... /gnu/store/020aw068yfsq84h6scmnvfrjacmznsgz-profile/bin/sed
checking for the Guix system type... x86_64-linux
checking for the store directory... /gnu/store
checking the length of the installed socket file name... 40
checking for unit test root directory... /home/aleksandar/Developer/guix/test-
tmp
checking the length of the socket file name used in tests... 72
checking the length of a typical hash bang line... 73
checking the length of a hash bang line used in tests... 109
checking for pkg-config... /gnu/store/020aw068yfsq84h6scmnvfrjacmznsgz-profile/
bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
configure: checking for guile 2.2
configure: found guile 2.2
checking for guile-2.2... /usr/bin/guile-2.2
checking for Guile version >= 2.2... 2.2.4
checking for guild-2.2... no
checking for guile-config-2.2... no
checking for guile-tools-2.2... no
configure: error: 'guild' binary not found; please check your guile-2.x 
installation.

The guild binary is available, the output of `which guild` is

guix$ which guild
/gnu/store/020aw068yfsq84h6scmnvfrjacmznsgz-profile/bin/guild

I am running Guix on a foreign distro (Kubuntu 18.10) if that matters.

Re: ./configure fails when building Guix

[Julien Lepiller]

Le 14 mai 2019 11:52:40 GMT+02:00, HiPhish <hiphish@posteo.de> a écrit :
>Hello everyone,
>
>I am trying to set up Guix for proper local development, but it fails
>during 
>the configuration step because the script cannot find the guild binary.
>Here is 
>what I did:
>
>- Check out the Guix repo
>- Switch to a local branch
>- run `guix environment guix` in order to set up all dependiencies
>- run `./bootstrap`
>- run `./configure`
>
>Here is the output of `./bootstrap`:
>
>guix$ ./bootstrap
>+ find po/doc -type f -name *.po
>+ sed -e s,guix-manual\.,,
>+ xargs -n 1 -I{} basename {} .po
>+ langs=zh_CN
>de
>ru
>es
>fr
>+ [ ! -e doc/guix.zh_CN.texi ]
>+ [ ! -e doc/guix.de.texi ]
>+ [ ! -e doc/guix.ru.texi ]
>+ [ ! -e doc/guix.es.texi ]
>+ [ ! -e doc/guix.fr.texi ]
>+ exec autoreconf -vfi
>autoreconf: Entering directory `.'
>autoreconf: running: autopoint --force
>autoreconf: running: aclocal --force -I m4
>autoreconf: configure.ac: tracing
>autoreconf: configure.ac: not using Libtool
>autoreconf: running: /gnu/store/rfaqi3a9ls7adr4y7bgwvln3iaf69qwj-
>autoconf-2.69/bin/autoconf --force
>autoreconf: running: /gnu/store/rfaqi3a9ls7adr4y7bgwvln3iaf69qwj-
>autoconf-2.69/bin/autoheader --force
>autoreconf: running: automake --add-missing --copy --force-missing
>configure.ac:23: warning: The 'AM_PROG_MKDIR_P' macro is deprecated,
>and its 
>use is discouraged.
>configure.ac:23: You should use the Autoconf-provided 'AC_PROG_MKDIR_P'
>macro 
>instead,
>configure.ac:23: and use '$(MKDIR_P)' instead of '$(mkdir_p)'in your
>Makefile.am 
>files.
>Makefile.am:601: warning: AM_GNU_GETTEXT used but 'po' not in SUBDIRS
>autoreconf: Leaving directory `.'
>
>And here is the output of `./configure`:
>
>guix$ ./configure
>checking for a BSD-compatible install... /gnu/store/
>020aw068yfsq84h6scmnvfrjacmznsgz-profile/bin/install -c
>checking whether build environment is sane... yes
>checking for a thread-safe mkdir -p... /gnu/store/
>020aw068yfsq84h6scmnvfrjacmznsgz-profile/bin/mkdir -p
>checking for gawk... gawk
>checking whether make sets $(MAKE)... yes
>checking whether make supports nested variables... yes
>checking whether make supports nested variables... (cached) yes
>checking whether make supports the include directive... yes (GNU style)
>checking for gcc... gcc
>checking whether the C compiler works... yes
>checking for C compiler default output file name... a.out
>checking for suffix of executables...
>checking whether we are cross compiling... no
>checking for suffix of object files... o
>checking whether we are using the GNU C compiler... yes
>checking whether gcc accepts -g... yes
>checking for gcc option to accept ISO C89... none needed
>checking whether gcc understands -c and -o together... yes
>checking dependency style of gcc... gcc3
>checking how to run the C preprocessor... gcc -E
>checking for grep that handles long lines and -e... /gnu/store/
>020aw068yfsq84h6scmnvfrjacmznsgz-profile/bin/grep
>checking for egrep...
>/gnu/store/020aw068yfsq84h6scmnvfrjacmznsgz-profile/bin/
>grep -E
>checking for ANSI C header files... yes
>checking for sys/types.h... yes
>checking for sys/stat.h... yes
>checking for stdlib.h... yes
>checking for string.h... yes
>checking for memory.h... yes
>checking for strings.h... yes
>checking for inttypes.h... yes
>checking for stdint.h... yes
>checking for unistd.h... yes
>checking minix/config.h usability... no
>checking minix/config.h presence... no
>checking for minix/config.h... no
>checking whether it is safe to define __EXTENSIONS__... yes
>checking whether NLS is requested... yes
>checking for msgfmt...
>/gnu/store/020aw068yfsq84h6scmnvfrjacmznsgz-profile/bin/
>msgfmt
>checking for gmsgfmt...
>/gnu/store/020aw068yfsq84h6scmnvfrjacmznsgz-profile/
>bin/msgfmt
>checking for xgettext...
>/gnu/store/020aw068yfsq84h6scmnvfrjacmznsgz-profile/
>bin/xgettext
>checking for msgmerge...
>/gnu/store/020aw068yfsq84h6scmnvfrjacmznsgz-profile/
>bin/msgmerge
>checking build system type... x86_64-pc-linux-gnu
>checking host system type... x86_64-pc-linux-gnu
>checking for ld used by GCC...
>/gnu/store/020aw068yfsq84h6scmnvfrjacmznsgz-
>profile/bin/ld
>checking if the linker
>(/gnu/store/020aw068yfsq84h6scmnvfrjacmznsgz-profile/
>bin/ld) is GNU ld... yes
>checking for shared library run path origin... done
>checking for CFPreferencesCopyAppValue... no
>checking for CFLocaleCopyCurrent... no
>checking for GNU gettext in libc... yes
>checking whether to use NLS... yes
>checking where the gettext function comes from... libc
>checking for sed...
>/gnu/store/020aw068yfsq84h6scmnvfrjacmznsgz-profile/bin/sed
>checking for the Guix system type... x86_64-linux
>checking for the store directory... /gnu/store
>checking the length of the installed socket file name... 40
>checking for unit test root directory...
>/home/aleksandar/Developer/guix/test-
>tmp
>checking the length of the socket file name used in tests... 72
>checking the length of a typical hash bang line... 73
>checking the length of a hash bang line used in tests... 109
>checking for pkg-config...
>/gnu/store/020aw068yfsq84h6scmnvfrjacmznsgz-profile/
>bin/pkg-config
>checking pkg-config is at least version 0.9.0... yes
>configure: checking for guile 2.2
>configure: found guile 2.2
>checking for guile-2.2... /usr/bin/guile-2.2
>checking for Guile version >= 2.2... 2.2.4
>checking for guild-2.2... no
>checking for guile-config-2.2... no
>checking for guile-tools-2.2... no
>configure: error: 'guild' binary not found; please check your guile-2.x
>
>installation.
>
>The guild binary is available, the output of `which guild` is
>
>guix$ which guild
>/gnu/store/020aw068yfsq84h6scmnvfrjacmznsgz-profile/bin/guild
>
>I am running Guix on a foreign distro (Kubuntu 18.10) if that matters.

I get that too on foreign distros. Here configure finds your distso's guile (in /usr/bin). Try to run configure inside a pure guix environment:

guix environment guix --pure -- ./configure

Re: ./configure fails when building Guix

[HiPhish]

On Tuesday, 14 May 2019 12:51:03 CEST Julien Lepiller wrote:
> Le 14 mai 2019 11:52:40 GMT+02:00, HiPhish <hiphish@posteo.de> a écrit :
> 
> I get that too on foreign distros. Here configure finds your distso's guile
> (in /usr/bin). Try to run configure inside a pure guix environment:
> 
> guix environment guix --pure -- ./configure

Thank you, that did it.