bug#27900: broken checkout? can't run autotools (automake) anymore in guix repository

bug#27900: broken checkout? can't run autotools (automake) anymore in guix repository

[ng0]

[-- Attachment #1: Type: text/plain, Size: 2014 bytes --]

Starting With one of the commits since yesterday evening I get this
when I try to run ~/guix_dev clean OR ~/guix_dev enter and then "make".

An excerpt from my guix_dev:
    clean)
        make clean-recursive
    ;;
    enter)
       guix environment --fallback --ad-hoc guix autoconf automake@1.15.1 make guile guile-ssh pkg-config gcc-toolchain libgcrypt gnutls guile-json zlib bzip2 sqlite help2man gettext texinfo guile-git
    ;;

This happens with automake AND automake@1.15.1, yesterday it used to work as it is (without specifying automake 1.15.1).


user@abyayala ~/src/guix/guix [env]$ ~/guix_dev clean
 cd . && /bin/sh /home/user/src/guix/guix/build-aux/missing automake-1.15 --gnu Makefile
 configure.ac:11: error: version mismatch.  This is Automake 1.15.1,
 configure.ac:11: but the definition used by this AM_INIT_AUTOMAKE
 configure.ac:11: comes from Automake 1.15.  You should recreate
 configure.ac:11: aclocal.m4 with aclocal and run automake again.
 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:491: warning: AM_GNU_GETTEXT used but 'po' not in SUBDIRS
 WARNING: 'automake-1.15' is probably too old.
 You should only need it if you modified 'Makefile.am' or
 'configure.ac' or m4 files included by 'configure.ac'.
 The 'automake' program is part of the GNU Automake package:
 <http://www.gnu.org/software/automake>
 It also requires GNU Autoconf, GNU m4 and Perl in order to run:
 <http://www.gnu.org/software/autoconf>
 <http://www.gnu.org/software/m4/>
 <http://www.perl.org/>
 make: *** [Makefile:2956: Makefile.in] Error 63



So what am I supposed to do now?
-- 
ng0
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
GnuPG: https://n0is.noblogs.org/my-keys
https://www.infotropique.org https://krosos.org

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

bug#27900: broken checkout? can't run autotools (automake) anymore in guix repository

[Danny Milosavljevic]

Hi ng0,

>        guix environment --fallback --ad-hoc guix autoconf automake@1.15.1 make guile guile-ssh pkg-config gcc-toolchain libgcrypt gnutls guile-json zlib bzip2 sqlite help2man gettext texinfo guile-git

I only ever do 

$ guix environment --fallback --pure guix

(The "--pure" is important)

and it works fine, bootstrapping too (via ./bootstrap - which invokes autoreconf).

I mean I guess your ad-hoc-everything way should be possible, but why would you do that?  It makes the setup flaky should the guix package ever change its inputs (I don't know whether it did in fact do that).

I do sometimes specify extra ad-hoc packages, like so:

$ guix environment --fallback --pure guix --ad-hoc guile-ncurses-with-gpm

The order of the arguments is sometimes important.  I think of "--ad-hoc" like "--" for many other UNIX commands (startx etc).

bug#27900: broken checkout? can't run autotools (automake) anymore in guix repository

[ng0]

[-- Attachment #1: Type: text/plain, Size: 1611 bytes --]

Danny Milosavljevic transcribed 0.8K bytes:
> Hi ng0,
> 
> >        guix environment --fallback --ad-hoc guix autoconf automake@1.15.1 make guile guile-ssh pkg-config gcc-toolchain libgcrypt gnutls guile-json zlib bzip2 sqlite help2man gettext texinfo guile-git
> 
> I only ever do 
> 
> $ guix environment --fallback --pure guix
> 
> (The "--pure" is important)

Nice. This fixed my issue.
My pure environment is not so pure because I'm having issues with bashrc and bash_profile at the moment
(bash_profile isn't respecting some of my files which provide all the bash things I have),
but it worked.

> and it works fine, bootstrapping too (via ./bootstrap - which invokes autoreconf).
> 
> I mean I guess your ad-hoc-everything way should be possible, but why would you do that?

Well I only started using the guix environment subcommands recently and I am experimenting.
--ad-hoc seemed logical to me, but as we use pure with guix, it already provides everything
guix needs. So no reason to use adhoc.

It makes the setup flaky should the guix package ever change its inputs (I don't know whether it did in fact do that).
> 
> I do sometimes specify extra ad-hoc packages, like so:
> 
> $ guix environment --fallback --pure guix --ad-hoc guile-ncurses-with-gpm
> 
> The order of the arguments is sometimes important.  I think of "--ad-hoc" like "--" for many other UNIX commands (startx etc).
> 

Okay, thanks for your help!
-- 
ng0
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
GnuPG: https://n0is.noblogs.org/my-keys
https://www.infotropique.org https://krosos.org

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]