From: Szabolcs Nagy <nsz@port70.net>
To: Rob Landley <rlandley@se-instruments.com>,
musl <musl@lists.openwall.com>
Subject: Re: musl-cross-make build script.
Date: Fri, 17 Feb 2017 12:56:46 +0100 [thread overview]
Message-ID: <20170217115646.GI12395@port70.net> (raw)
In-Reply-To: <20170217115321.GH12395@port70.net>
* Szabolcs Nagy <nsz@port70.net> [2017-02-17 12:53:22 +0100]:
> * Rob Landley <rlandley@se-instruments.com> [2017-02-16 16:57:54 -0600]:
> > install -j$(nproc)
>
> i didnt know about -j$(nproc), what does it do?
never mind,
just got confused between make and shell syntax
and thought make had some magic nproc variable..
next prev parent reply other threads:[~2017-02-17 11:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-16 22:57 Rob Landley
2017-02-17 11:53 ` Szabolcs Nagy
2017-02-17 11:56 ` Szabolcs Nagy [this message]
2017-02-18 8:45 ` Rob Landley
2017-02-18 12:53 ` Szabolcs Nagy
2017-02-18 13:39 ` Szabolcs Nagy
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=20170217115646.GI12395@port70.net \
--to=nsz@port70.net \
--cc=musl@lists.openwall.com \
--cc=rlandley@se-instruments.com \
/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.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).