From: Pjotr Prins <pjotr.public12@thebird.nl>
To: Pjotr Prins <pjotr.public12@thebird.nl>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: guile-git trouble (building from source)
Date: Mon, 21 Aug 2017 13:02:10 +0200 [thread overview]
Message-ID: <20170821110210.GA19775@thebird.nl> (raw)
In-Reply-To: <20170806134510.GA20166@thebird.nl>
On Sun, Aug 06, 2017 at 03:45:10PM +0200, Pjotr Prins wrote:
> > But yeah, the problem remains for someone building from source. :-/
>
> I am facing issues with guile-git.
>
> I wish we had a bullet proof way of installing from source. I had it
> with guix environment and now that won't work because guile-git is
> missing and I can't bootstrap...
Today, magically, a 'guix pull' solved it which did not work 3 weeks ago. My
latest 'bullet proof' setup for a clean build from source is:
*** Install the dependencies and build tools using Guix:
The safest route is by using guix environment after starting
a clean shell (note environment does not clutter up your profile!):
#+begin_src sh :lang bash
screen -S guix-build # I tend to build in screen
env -i /bin/bash --login --noprofile --norc
~/.guix-profile/bin/guix environment guix --ad-hoc help2man git strace \
pkg-config less vim binutils coreutils grep guile guile-git gcc --no-grafts
bash # you may want this shell
#+end_src sh :lang bash
In fact pick the most recent guix you have got, see 'ls
/gnu/store/*guix*/bin/guix' and run that command. Use the --no-grafts
switch if you have built packages that way before.
Note that you can start guix by installing the binary tar ball, or
copying it from another machine using the rather useful guix archive
or [[https://www.gnu.org/software/guix/news/creating-bundles-with-guix-pack.html][guix pack]] commands.
You may want to take a note of these running versions
#+begin_src sh :lang bash
gcc --version
guile --version
#+end_src sh :lang bash
Next in the source tree
#+begin_src sh :lang bash
rm -rf autom4te.cache/ # to be sure
make clean
./bootstrap
./configure --localstatedir=/var
make clean # to be really sure
make clean-go # to be even surer
make -j 32
#+end_src sh :lang bash
:)
Pj
--
next prev parent reply other threads:[~2017-08-21 11:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-05 19:36 guile-git repository renamed: cannot upgrade Ricardo Wurmus
2017-08-05 21:17 ` Ludovic Courtès
2017-08-06 13:45 ` guile-git trouble (building from source) Pjotr Prins
2017-08-07 0:26 ` Christopher Allan Webber
2017-08-11 14:55 ` guile-git trouble (building from source) - guix archive to the rescue Pjotr Prins
2017-08-21 11:02 ` Pjotr Prins [this message]
2017-08-06 18:31 ` guile-git repository renamed: cannot upgrade Ricardo Wurmus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170821110210.GA19775@thebird.nl \
--to=pjotr.public12@thebird.nl \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.