All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: alsa makefiles don't work with -jN where N > 1
Date: Tue, 24 Aug 2004 15:44:40 -0400	[thread overview]
Message-ID: <1093376680.817.48.camel@krustophenia.net> (raw)

Subject says it all.  Here is the relevant section from the GNU make documentation:

`warning: jobserver unavailable: using -j1. Add `+' to parent make rule.'
        In order for make processes to communicate, the parent will pass
        information to the child. Since this could result in problems if
        the child process isn't actually a make, the parent will only do
        this if it thinks the child is a make. The parent uses the
        normal algorithms to determine this (see section 5.6.1 How the
        MAKEVariable Works). If the makefile is constructed such that
        the parent doesn't know the child is a make process, then the
        child will receive only part of the information necessary. In
        this case, the child will generate this warning message and
        proceed with its build in a sequential manner.

I believe this is because some of the rules in the makefile aren't make
commands, but rm -f's.  This always seemed dangerous and sloppy to me -
why does make need to rm -f anything?  Isn't this the whole point of
makefiles, so you don't have to rm -f your tree and rebuild every time
you change something? 

Lee



-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285

             reply	other threads:[~2004-08-24 19:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-24 19:44 Lee Revell [this message]
2004-08-25 13:57 ` alsa makefiles don't work with -jN where N > 1 Takashi Iwai

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=1093376680.817.48.camel@krustophenia.net \
    --to=rlrevell@joe-job.com \
    --cc=alsa-devel@lists.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.