From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] RFC: make & emake
Date: Fri, 26 Sep 2003 00:00:55 -0400 [thread overview]
Message-ID: <200309260001.03079.vapier@gentoo.org> (raw)
[-- Attachment #1: signed data --]
[-- Type: text/plain, Size: 701 bytes --]
sometime ago i was working with someone on a package where emake failed. my
answer was just to use make. msterret pointed out though that `emake -j1` is
a better solution, the reason being that MAKEOPTS can contain other things
than just the -j command.
so i'm wondering if anyone out there has any other input on this ...
another reason i like `emake -j1` is that it quickly shows developers that the
package doesnt work with parallel builds instead of wondering 'hmm is this
supposed to be make or did they just not try emake ?'
so if no one else has anything to say about this, i'd like to start pushing
via the documentation for usage of `emake -j1` instead of `make`
-mike
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 827 bytes --]
next reply other threads:[~2003-09-26 4:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-26 4:00 Mike Frysinger [this message]
2003-09-26 20:16 ` [gentoo-dev] RFC: make & emake Aron Griffis
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=200309260001.03079.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=gentoo-dev@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