From: ludo@gnu.org (Ludovic Courtès)
To: Chris Dale <adventureonthehighseas@gmail.com>
Cc: bug-guix@gnu.org
Subject: Re: Linker error on installing gcc
Date: Mon, 22 Apr 2013 13:53:30 +0200 [thread overview]
Message-ID: <878v4avl1h.fsf@gnu.org> (raw)
In-Reply-To: <CANV_ih-+b8dUV5UAVVGLXZ2hhP_a1c8sqNevEzs9k_yBT2e=bw@mail.gmail.com> (Chris Dale's message of "Mon, 22 Apr 2013 06:43:50 -0500")
Chris Dale <adventureonthehighseas@gmail.com> skribis:
>>
>> There’s no actual error message here. Could you look for the full log
>> under /nix/var/log/nix/drvs, and check if there’s an error message
>> somewhere above? (It may have been built with ‘make -jX’, so the output
>> is intermingled.)
>>
>
> All that was above what I posted was the output of a linking command that
> worked correctly. What would I be looking for, for error message syntax?
Something starting with “error:”, I guess.
Also, are you running guix-daemon as root, with a special-purpose build
user group, as noted in the “Installation” section of the manual?
>> > x86_64 architecture
>>
>> Normally it should be using pre-compiled binaries from hydra.gnu.org by
>> default.
>>
>> What do you have in /nix/var/nix/substitute-binary/cache?
>>
>
> I have no directory /nix/var at all - just /nix/store. That may be related!
The actual directory name depends on your --localstatedir or --prefix
option passed to ‘configure’. Can you check the value of
‘localstatedir’ in the config.log file?
TIA!
Ludo’.
next prev parent reply other threads:[~2013-04-22 11:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-21 20:27 Linker error on installing gcc Chris Dale
2013-04-22 11:30 ` Ludovic Courtès
2013-04-22 11:43 ` Chris Dale
2013-04-22 11:53 ` Ludovic Courtès [this message]
2013-04-22 12:27 ` Chris Dale
2013-04-22 16:21 ` Ludovic Courtès
[not found] ` <CANV_ih9jw=ua2eh5+g9D8WR=9WEF233b6TnAcBBFuFRZymcwzA@mail.gmail.com>
2013-04-22 21:50 ` Ludovic Courtès
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=878v4avl1h.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=adventureonthehighseas@gmail.com \
--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).