public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mikael Hallendal <hallski@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] WindowMaker 0.8? (emake vs make?)
Date: 16 Jan 2002 21:21:27 +0100	[thread overview]
Message-ID: <1011212487.8195.11.camel@fluffy> (raw)
In-Reply-To: <42457.216.103.48.240.1011206255.squirrel@www.portablehole.net>

[-- Attachment #1: Type: text/plain, Size: 743 bytes --]

ons 2002-01-16 klockan 19.37 skrev Jano Lukac:
> Zach Forrest said:
> <snip>
> >  Two, "try" is no longer used. Instead, use something like
> > "./configure || die" or "emake || die". This will all make a little
> > more  sense once you've read the Gentoo Linux Developers HOWTO.
> 
> SHouldn't it be "emake || make || die" ??  That way, for those non-smp
> makefiles, you'll get at least *some* benefit for have more than 1.  Unless,
> of course, emake has been rewritten to try "make $MAKEOPTS || make"

Yes, emake first tries to run make $MAKEOPTS and if that fails it tries
to run make.

Regards,
  Mikael Hallendal

-- 
Mikael Hallendal
Gentoo Linux Developer, Desktop Team Leader
CodeFactory AB, Stockholm, Sweden


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 232 bytes --]

  parent reply	other threads:[~2002-01-16 20:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-16 14:39 [gentoo-dev] WindowMaker 0.8? Clay Mitchell
2002-01-16 15:38 ` Gila
2002-01-16 16:10   ` Clay Mitchell
2002-01-16 16:58     ` Tod M. Neidt
2002-01-16 17:20     ` [gentoo-dev] WindowMaker 0.8? (ebuild info) Zach Forrest
2002-01-16 18:37       ` [gentoo-dev] WindowMaker 0.8? (emake vs make?) Jano Lukac
2002-01-16 18:38         ` Jano Lukac
2002-01-16 20:21         ` Mikael Hallendal [this message]
2002-01-16 19:21     ` [gentoo-dev] WindowMaker 0.8? Gila
2002-01-16 17:02 ` Grant Goodyear

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=1011212487.8195.11.camel@fluffy \
    --to=hallski@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