From: Michael Zucchi <notzed@gmail.com>
To: help-guix <help-guix@gnu.org>
Subject: build issues w/ system glibc
Date: Thu, 19 Dec 2019 10:20:18 +1030 [thread overview]
Message-ID: <1c5f5fd0-361c-2ff4-d1ee-1c604006342d@gmail.com> (raw)
Morning,
Just a couple of comments re: building from git. Well that was the
intention, but it's turned into a failure to build.
1) bootstrap isn't mentioned anywhere in the README, it just mentions
configure
2) i know the README is for a web service to reformat, but it's really
miserable trying to read it from a shell
3) using "guix environment guix" the build fails.
$ make V=1
...
g++ -Wall -std=c++11 -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 -lz
-L/gnu/store/i6l1579g80387rda658jy9cfqq82643d-sqlite-3.28.0/lib
-lsqlite3 -L/usr/lib64 -lgcrypt -lbz2
/usr/bin/ld:
/gnu/store/ahqgl4h89xqj695lgqvsaf6zh2nhy4pj-glibc-2.29/lib/libpthread.so.0:
undefined reference to `__libc_vfork@GLIBC_PRIVATE'
collect2: error: ld returned 1 exit status
make[2]: *** [Makefile:3469: guix-daemon] Error 1
make[2]: Leaving directory '/home/notzed/src/guix'
make[1]: *** [Makefile:4766: all-recursive] Error 1
make[1]: Leaving directory '/home/notzed/src/guix'
make: *** [Makefile:3257: all] Error 2
notzed@shitzone:~/src/guix$
I'm using guix on Slackware-current and that (currently) uses
glibc-2.30, and when using the platform compiler it links against that
and not the guix glibc.
I tried installing gcc-toolchain but the same thing happens. I tried
-L/gnu/store/<path to glibc> but that doesn't work.
Regards,
Z
next reply other threads:[~2019-12-18 23:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-18 23:50 Michael Zucchi [this message]
2019-12-19 8:03 ` build issues w/ system glibc Julien Lepiller
2019-12-21 21:06 ` Michael Zucchi
2019-12-22 9:05 ` Julien Lepiller
2019-12-22 23:06 ` Michael Zucchi
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=1c5f5fd0-361c-2ff4-d1ee-1c604006342d@gmail.com \
--to=notzed@gmail.com \
--cc=help-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.
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).