zsh-users
 help / color / mirror / code / Atom feed
From: Perry Smith <pedz@easesoftware.com>
To: zsh-users@zsh.org
Subject: Re: Parallel processing
Date: Mon, 28 Mar 2022 08:26:15 -0500	[thread overview]
Message-ID: <8C2E6EAC-F17C-4462-BA38-A678ABEAB1FD@easesoftware.com> (raw)
In-Reply-To: <YkC5zgf9TJPmZ/6n@gmx.de>



> On Mar 27, 2022, at 14:23, Dominik Vogt <dominik.vogt@gmx.de> wrote:
> 
> On Thu, Mar 24, 2022 at 11:34:07PM -0500, Perry Smith wrote:
>> I need to do about 20 commands.  Each will take several hours to perhaps days.  I???d like to start some fixed number like 4 jobs that are running.  The others are waiting for one of the others to get finished.
>> 
> 
>> I tried creating a Makefile and use the -j option in make but my
>> targets have spaces in them and make doesn???t like that.  (This
>> is on a BSD system.)
> 
> Are you talking about GNU Make?  What is the problem?
> 
> $ cat Makefile
> TARGETS = a\ b foo\ bar
> all: $(TARGETS)
> foo\ bar:
>        touch "$@"
> a\ b:
>        touch "$@"
> $ ls .
> Makefile
> $ make -j 2
> $ ls .
> a b  foo bar  Makefile
> 

I’m inside a BSD “jail”.  They have their own make (I believe).  Let me try the syntax and see if I can get it to work.  The next challenge will be to get this syntax to work from within a list so I can say:

${LIST_OF_TARGETS} :

Where an item in the list can have spaces.





  reply	other threads:[~2022-03-28 13:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-25  4:34 Perry Smith
2022-03-25 18:27 ` Bart Schaefer
2022-03-26 18:10   ` Philippe Troin
2022-03-26 22:19     ` Bart Schaefer
2022-03-27 17:32       ` Philippe Troin
2022-03-27 17:42         ` Bart Schaefer
2022-03-27 19:23 ` Dominik Vogt
2022-03-28 13:26   ` Perry Smith [this message]
2022-03-28 13:31 ` Perry Smith
2022-03-26  4:34 jdh
2022-03-27 18:37 jdh
2022-03-27 19:06 ` Bart Schaefer
2022-03-27 19:24   ` Ray Andrews
2022-03-28 13:47 ` Perry Smith

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=8C2E6EAC-F17C-4462-BA38-A678ABEAB1FD@easesoftware.com \
    --to=pedz@easesoftware.com \
    --cc=zsh-users@zsh.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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).