From: Konrad Hinsen <konrad.hinsen@fastmail.net>
To: bug-guix@gnu.org
Subject: Re: Installing guix from Git
Date: Sun, 9 Jun 2013 12:03:16 +0200 [thread overview]
Message-ID: <20916.21220.189793.288404@Ordinateur-de-Catherine-Konrad.local> (raw)
In-Reply-To: <87wqq48qd4.fsf@karetnikov.org>
Nikita Karetnikov writes:
> > make: *** No rule to make target `nix/libstore/schema.sql', needed by `nix/libstore/schema.sql.hh'. Stop.
>
> Could you try to run './bootstrap' before './configure && make && make
> check'?
Thanks, that helped me make a lot of progress!
Now the build procedure crashes during "make", see below for the error message.
As always I am very open to suggestions ;-)
Konrad.
g++ -g -O2 -o guix-daemon nix/nix-daemon/guix_daemon-nix-daemon.o nix/nix-daemon/guix_daemon-guix-daemon.o libstore.a libutil.a libformat.a -lbz2 -L/nix/store/8dk06b6wm9gc1kwqr9fn7a1x6bvl8pf2-sqlite-3.7.15.2/lib -lsqlite3 -L/home/hinsen/.guix-profile//lib -lgcrypt
libutil.a(libutil_a-hash.o): In function `finish':
/home/hinsen/Development/guix/nix/libutil/hash.cc:271: undefined reference to `SHA256_Final'
/home/hinsen/Development/guix/nix/libutil/hash.cc:269: undefined reference to `MD5_Final'
/home/hinsen/Development/guix/nix/libutil/hash.cc:270: undefined reference to `SHA1_Final'
libutil.a(libutil_a-hash.o): In function `update':
/home/hinsen/Development/guix/nix/libutil/hash.cc:263: undefined reference to `SHA256_Update'
/home/hinsen/Development/guix/nix/libutil/hash.cc:261: undefined reference to `MD5_Update'
/home/hinsen/Development/guix/nix/libutil/hash.cc:262: undefined reference to `SHA1_Update'
libutil.a(libutil_a-hash.o): In function `start':
/home/hinsen/Development/guix/nix/libutil/hash.cc:254: undefined reference to `SHA256_Init'
/home/hinsen/Development/guix/nix/libutil/hash.cc:252: undefined reference to `MD5_Init'
/home/hinsen/Development/guix/nix/libutil/hash.cc:253: undefined reference to `SHA1_Init'
collect2: error: ld returned 1 exit status
make[2]: *** [guix-daemon] Error 1
make[2]: Leaving directory `/media/sf_mac-hinsen/Development/guix'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/media/sf_mac-hinsen/Development/guix'
make: *** [all] Error 2
next prev parent reply other threads:[~2013-06-09 10:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-07 15:42 Installing guix from Git Konrad Hinsen
2013-06-07 16:22 ` Ludovic Courtès
2013-06-08 17:16 ` Konrad Hinsen
2013-06-08 17:27 ` Nikita Karetnikov
2013-06-09 10:03 ` Konrad Hinsen [this message]
2013-06-09 10:23 ` Ludovic Courtès
2013-06-10 6:33 ` Konrad Hinsen
2013-06-10 8:26 ` Ludovic Courtès
2013-06-10 8:27 ` Ludovic Courtès
2013-06-10 9:55 ` Konrad Hinsen
2013-06-10 22:02 ` Ludovic Courtès
2013-06-11 8:20 ` Konrad Hinsen
2013-06-11 12:17 ` Ludovic Courtès
2013-06-11 13:23 ` Konrad Hinsen
2013-06-11 13:58 ` Ludovic Courtès
2013-06-11 15:30 ` Konrad Hinsen
2013-06-11 22:35 ` Ludovic Courtès
2013-06-12 7:11 ` Konrad Hinsen
2013-06-12 7:43 ` Ludovic Courtès
2013-06-11 19:47 ` Konrad Hinsen
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20916.21220.189793.288404@Ordinateur-de-Catherine-Konrad.local \
--to=konrad.hinsen@fastmail.net \
--cc=bug-guix@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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).