Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 151635
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 11, 20262026-05-11T09:28:51+00:00 2026-05-11T09:28:51+00:00

Using GNU make, is it possible to create a set of targets that will

  • 0

Using GNU make, is it possible to create a set of targets that will never be scheduled at the same time when using the ‘–jobs’ option?

Background:

To make this a little more concrete, consider a makefile of the form

p1: ...deps... # no parallelization conflicts (can run at the same time as p*, e*)         ...rules...  p2: ...deps... # no parallelization conflicts (can run at the same time as p*, e*)         ...rules...  p3: ...deps... # no parallelization conflicts (can run at the same time as p*, e*)         ...rules...  e1: ...deps... # cannot run at same time as any other e*         ...rules...  e2: ...deps... # cannot run at same time as any other e*         ...rules...  e3: ...deps... # cannot run at same time as any other e*         ...rules... 

The main thing I need to do is make sure that e1, e2, and e3 never are being processed at the same time because they do some work on an embedded device with limited resources. They crash if multiple ones of them are executing at the same time. p1, p2, and p3 can be executed in parallel with anything, including any e* job.

Note that the actual makefile has a few thousand targets with a dependency tree that’s about 10 levels deep, so I’m hoping there’s a way to do this that (a) doesn’t require running make serially and (b) preserves the benefits of encoding the dependency tree in a makefile.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. 2026-05-11T09:28:51+00:00Added an answer on May 11, 2026 at 9:28 am

    One option for you is to use ‘flock’ to run the ‘e’ rules under an exclusive lock. See man flock(1) for details. For example, instead of

    e2: deps     my_cmd foo bar 

    You can have

    e2: deps     flock .embedded-device-lock -c my_cmd foo bar 

    What happens then is that all the ‘e’ targets get started by make in parallel (possibly), but the actual commands will be executed serially.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Ask A Question

Stats

  • Questions 90k
  • Answers 90k
  • Best Answers 0
  • User 1
  • Popular
  • Answers
  • Editorial Team

    How to approach applying for a job at a company ...

    • 7 Answers
  • Editorial Team

    How to handle personal stress caused by utterly incompetent and ...

    • 5 Answers
  • Editorial Team

    What is a programmer’s life like?

    • 5 Answers
  • Editorial Team
    Editorial Team added an answer Keyboard.Modifiers is the right class/property to use. I would suggest… May 11, 2026 at 6:00 pm
  • Editorial Team
    Editorial Team added an answer Remember that a pointer variable is a variable itself, so… May 11, 2026 at 6:00 pm
  • Editorial Team
    Editorial Team added an answer In plain old C++, you can do this with compile-time… May 11, 2026 at 6:00 pm

Related Questions

My application has a command line interface, and I'm thinking about using the GNU
I have an existing codebase targeting a Windows environment and with an eye to
What would be the best choice of build system for a more than one
I need to get unmanaged Windows C++ clients to talk to a WCF service.

Trending Tags

analytics british company computer developers django employee employer english facebook french google interview javascript language life php programmer programs salary

Top Members

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.