From: "Jano Lukac" <jano@portablehole.net>
To: <gentoo-dev@gentoo.org>
Subject: Re: [gentoo-dev] WindowMaker 0.8? (emake vs make?)
Date: Wed, 16 Jan 2002 10:37:35 -0800 (PST) [thread overview]
Message-ID: <42457.216.103.48.240.1011206255.squirrel@www.portablehole.net> (raw)
In-Reply-To: <3C45B659.1090908@shaw.ca>
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"
>
> You might also want to check the devloper's mailing list archives for
<snip>
next prev parent reply other threads:[~2002-01-16 18:23 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 ` Jano Lukac [this message]
2002-01-16 18:38 ` [gentoo-dev] WindowMaker 0.8? (emake vs make?) Jano Lukac
2002-01-16 20:21 ` Mikael Hallendal
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=42457.216.103.48.240.1011206255.squirrel@www.portablehole.net \
--to=jano@portablehole.net \
--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