From: Michael S. Zick <minimod@morethan.org>
To: buildroot@busybox.net
Subject: [Buildroot] Job ID Query
Date: Sat, 7 Jan 2012 13:59:13 -0600 [thread overview]
Message-ID: <201201071359.15470.minimod@morethan.org> (raw)
In-Reply-To: <874nw7ia2j.fsf@macbook.be.48ers.dk>
On Sat January 7 2012, you wrote:
> >>>>> "Michael" == Michael S Zick <minimod@morethan.org> writes:
>
> Michael> Group,
> Michael> Is there a Make or BuildRoot variable that identifies
> Michael> the current make job id?
>
> Not afaik. What is the use case for knowing this?
>
Package capture in the presence of multiple make jobs outputting
to a common directory, typically, through a common part of the
build system infrastructure.
It goes back to a suggestion of mine a few months back in answer
to (one of many) posts about capturing the build output in
distinct packages.
Have been working on parts of my own suggestion and think I can
make it work, __IFF__ you run Buildroot -j1.
Which no one of sane mind, with a multicore machine will be
interested in doing. ;-)
I did also consider dropping that restrictive phrase: "outputting
to a common directory" -
But that I consider both too invasive, and against my declared
intent to make it a transparent feature addition for the user.
Will continue giving my own suggestion more thought as time
becomes available.
After all, (on a failure) make does have that: "Waiting for xyz
jobs to complete" message, it does "know" how many jobs are
running at the moment.
But I certainly don't want to propose patching make to expose
the job identification if it doesn't already provide that.
Mike
prev parent reply other threads:[~2012-01-07 19:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-06 15:25 [Buildroot] Job ID Query Michael S. Zick
2012-01-07 19:31 ` Peter Korsgaard
2012-01-07 19:59 ` Michael S. Zick [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=201201071359.15470.minimod@morethan.org \
--to=minimod@morethan.org \
--cc=buildroot@busybox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox