From: ludo@gnu.org (Ludovic Courtès)
To: Saul Hazledine <saul@alienscience.org.uk>
Cc: guix-devel@gnu.org
Subject: Re: Advice needed on gcc error
Date: Fri, 21 Nov 2014 10:21:12 +0100 [thread overview]
Message-ID: <87r3ww9aev.fsf@gnu.org> (raw)
In-Reply-To: <546E5DF6.6080007@alienscience.org.uk> (Saul Hazledine's message of "Thu, 20 Nov 2014 22:32:38 +0100")
Saul Hazledine <saul@alienscience.org.uk> skribis:
> I have a running installation of guix/gnu os and wanted to install vim:
> guix package -i vim
>
> I am not using hydra and so the package manager went ahead and tried
> to download and compile the internet (which is what I wanted because I
> am experimenting with the OS). I hit what could be a compilation error
> in gcc 4.8.3:
> Makefile:3584: recipe for target 's-attrtab' failed
Could you post, say, the last 200 lines of its build log? One way to
find it is to run:
ls -lrt /var/log/guix/drvs/*/*gcc-4.8.3*
and then open the most recent one.
> This led me to the reason I am contacting the list. A newly installed
> guix machine is pretty basic and does not seem to have any way I
> report a bug from the build other than typing it myself - am I missing
> a more convenient method.
There’s no convenient method to report build issues, but I agree it
would be very useful. Something like a --report option to ‘guix build’
that would automatically email bug-guix@gnu.org with the relevant info
upon failure.
Thanks,
Ludo’.
next prev parent reply other threads:[~2014-11-21 9:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-20 21:32 Advice needed on gcc error Saul Hazledine
2014-11-21 9:21 ` Ludovic Courtès [this message]
2014-11-22 17:52 ` Saul Hazledine
2014-11-22 21:00 ` Ludovic Courtès
2014-11-22 21:10 ` Adam Pribyl
2014-11-22 22:09 ` Ludovic Courtès
2014-11-23 10:17 ` Adam Pribyl
2014-11-23 20:22 ` Ludovic Courtès
2014-11-23 20:55 ` Adam Pribyl
2014-11-24 20:17 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r3ww9aev.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=saul@alienscience.org.uk \
/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.