From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] emerge ignoring -v switch
Date: Wed, 7 Dec 2011 09:14:28 +0000 [thread overview]
Message-ID: <20111207091428.0f610c7e@hactar.digimed.co.uk> (raw)
In-Reply-To: <201112060858.43067.michaelkintzios@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 820 bytes --]
On Tue, 6 Dec 2011 08:58:23 +0000, Mick wrote:
> On Sunday 04 Dec 2011 20:49:55 Neil Bothwick wrote:
> > On Sun, 4 Dec 2011 15:18:40 +0000, Mick wrote:
> > > But then if there were say 5 ebuilds running in parallel and all
> > > their output printed in the same terminal, it would be almightily
> > > difficult to untangle the spaghetti that may show up in an error?
> >
> > Which is why setting -j >1 sets wh
>
> Did you mean to finish this message later on, or does "wh" mean
> something? o_O
Not only did I mean to finish it, I thought I had. Using --jobs >1 sets
the quiet-build flag, so you only get the emerge output, not all the
stuff from autotools and gcc. If an ebuild fails, you get that output at
the end.
--
Neil Bothwick
WinErr 012: Window closed - Do not look inside
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-12-07 9:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-03 14:23 [gentoo-user] emerge ignoring -v switch Indi
2011-12-03 14:29 ` Hinnerk van Bruinehsen
2011-12-03 16:45 ` Frank Steinmetzger
2011-12-04 8:27 ` Mick
2011-12-04 14:05 ` Frank Steinmetzger
2011-12-04 15:18 ` Mick
2011-12-04 20:49 ` Neil Bothwick
2011-12-06 8:58 ` Mick
2011-12-07 9:14 ` Neil Bothwick [this message]
2011-12-07 10:26 ` [gentoo-user] " Nikos Chantziaras
2011-12-07 10:55 ` Neil Bothwick
2011-12-07 11:13 ` Pandu Poluan
2011-12-07 13:39 ` Dale
2011-12-07 16:13 ` Frank Steinmetzger
2011-12-07 16:23 ` Neil Bothwick
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=20111207091428.0f610c7e@hactar.digimed.co.uk \
--to=neil@digimed.co.uk \
--cc=gentoo-user@lists.gentoo.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