On Tue, 27 Sep 2016 22:10:31 -0700 Chris Marusich <cmmarus...@gmail.com> wrote:
> John Darrington <j...@darrington.wattle.id.au> writes: > > > On Tue, Sep 27, 2016 at 09:18:30PM -0700, Chris Marusich wrote: > > Hi, > > > > The manual says ((guix) Building from Git): > > > > --8<---------------cut here---------------start------------->8--- > > The easiest way to set up a development environment for Guix is, of > > course, by using Guix! The following command starts a new shell where > > all the dependencies and appropriate environment variables are set up > > to > > hack on Guix: > > > > guix environment guix > > --8<---------------cut here---------------end--------------->8--- > > > > After running this command successfully, I get the following error > > while > > running ./bootstrap: > > > > --8<---------------cut here---------------start------------->8--- > > + exec autoreconf -vfi > > ./bootstrap: line 5: exec: autoreconf: not found > > --8<---------------cut here---------------end--------------->8--- > > > > This makes me wonder: has something changed, and the manual is now > > incorrect? > > > > > > I don't think so. Running ./bootstrap is not part of the normal process > > for *building* > > guix - only for bootstrapping. But you are right - it is common to want to > > do that. > > For this reason I often run: > > > > guix environment guix --ad-hoc automake autoconf texinfo help2man > > > > > > But perhaps you are right - the manual might want to mention this. > > > > J' > > That makes sense. I feel like it used to provide all the dependencies, > including autoconf etc., but that was months ago, and I might be > mis-remembering. It works fine when I add the needed bootstrap > dependencies with --ad-hoc. You can also do guix environment -e "(@ (gnu packages package-management) guix)" which points to 'guix-devel' and includes everything needed to build from a git clone. `~Eric
