public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Uladzimir Bely <ubely@ilbers.de>
To: "Schultschik, Sven" <sven.schultschik@siemens.com>,
	"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: Re: limit PARALLEL_MAKE
Date: Thu, 29 Feb 2024 11:14:16 +0300	[thread overview]
Message-ID: <046e9d21b3dea3055e27581db11e932172cdc904.camel@ilbers.de> (raw)
In-Reply-To: <0ffc2ce05f64d20599170b31799ef54eafe8862c.camel@siemens.com>

On Wed, 2024-02-28 at 18:05 +0000, Schultschik, Sven wrote:
> On Wed, 2024-02-28 at 15:57 +0300, Uladzimir Bely wrote:
> > On Wed, 2024-02-28 at 12:52 +0000, 'Schultschik, Sven' via isar-
> > users
> > wrote:
> > > Hi,
> > > 
> > > I found a bug in the fTPM build that it has a bug if more than 16
> > > cores
> > > are available. On a machine with 20 cors the my build faild
> > > constantly.
> > > Limit hardcoded the ftpm build to -j 16 fixed the issue.
> > > 
> > > Is there a correct ISAR way to limit $(PARALLEL_MAKE) to max 16?
> > > 
> > > Or do I have to write me an own if (nproc > 16) -j 16 variable?
> > > 
> > > Thanks
> > > 
> > > Sven
> > > 
> > 
> > Hello.
> > 
> > Just export it before the build:
> > ```
> > export PARALLEL_MAKE="-j 10"
> > ```
> > 
> > It should work both with build using kas-container and ordinary
> > build.
> 
> Hi
> 
> sure that would work, but I wanted to just limit for that one recipe
> and not for the complete build.
> 
> So it can be included directly into the recipe and be used by others.

Hello

```
PARALLEL_MAKE = "-j 10"
```

Adding this to the recipe also works.


      reply	other threads:[~2024-02-29  8:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-28 12:52 Schultschik, Sven
2024-02-28 12:57 ` Uladzimir Bely
2024-02-28 18:05   ` Schultschik, Sven
2024-02-29  8:14     ` Uladzimir Bely [this message]

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=046e9d21b3dea3055e27581db11e932172cdc904.camel@ilbers.de \
    --to=ubely@ilbers.de \
    --cc=isar-users@googlegroups.com \
    --cc=sven.schultschik@siemens.com \
    /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