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

  • Home
  • SEARCH
  • 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 6919827
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 27, 20262026-05-27T10:02:58+00:00 2026-05-27T10:02:58+00:00

I usually have an environment setting for MAKE_MODE (Windows XP, using GNU make, both

  • 0

I usually have an environment setting for MAKE_MODE (Windows XP, using GNU make, both under Cygwin and native)

set MAKE_MODE=UNIX

I now found differences between my build server (which has no MAKE_MODE defined) and a local build. This may be something completely different, but it got me wondering what other values I could specify for MAKE_MODE.

I think I know that MAKE_MODE=UNIX is suppose to tell GNU make to use /bin/sh – if it finds it – , but I quickly checked the GNU make manual and couldn’t find a description. A google search only told me what I already know, but doesn’t give a valid alternative.

Is the only alternative to not define the variable? Does it have influence at all when using CMD.exe and a native version of GNU make?

EDIT: So far I have found references for the values ‘unix’, ‘win32’, ‘null’ and undefined, but no explanations, and no specifications. But a look at the source code for GNU make 3.82 shows not a single occurrence of the string “MAKE_MODE”, so GNUmake itself apparently doesn’t change its behavior when this environment variable is set or not.

EDIT2: I checked the source code for GNU make for MinGW, and again found nothing. Maybe it’s CygWin specific?

EDIT3: I found a reference that it might be property of an old version of GNU make, so I checked version 3.75. No luck, the string MAKE_MODE does not appear in the source code at all. The next step really must be the Cygwin version of GNU make. I know from 10 years ago that the Cygwin port in those days was not integrated in the regular source tree.

  • 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. Editorial Team
    Editorial Team
    2026-05-27T10:02:59+00:00Added an answer on May 27, 2026 at 10:02 am

    I found an ancient mailing list entry on the Cygwin site, explaining the basic operational effect of MAKE_MODE. This definitely indicates that the variable has to do with the Cygwin implementation of GNU make.

    I’ll dig around in the source code, and add to this answer when I find more details.

    UPDATE: In a more recent post by maintainer Christopher Faylor I found the following update for GNU make version 3.81:

    Note that the –win32 command line option and “MAKE_MODE” environment
    variable are no longer supported in Cygwin’s make. If you need to use a
    Makefile which contains MS-DOS path names, then please use a MinGW
    version of make.

    I’ve not really found the values allowed for MAKE_MODE, but it’s not any more necessary or supported in most recent versions of GNU make for Cygwin, and it was used for supporting DOS filenames in Cygwin’s make.

    And if you really want to know the set of allowed values, look in the source for Cygwin’s make version before 3.81-1. I guess the only useful value was unix, all others will have meant the same.

    Case closed? There’s still not many views here…

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

Sidebar

Related Questions

It's a known fact that Windows applications usually have 2Gb of private address space
I usually do all my java development on linux, using fedora package manager setting
I usually have my structure laid out something like this: <div id=all> <div id=page>
When I run an MSI (without parameters) I usually have to click my way
When performing many inserts into a database I would usually have code like this:
I work with Mac OS X Leopard. I usually have 5 or 10 text
In a Python system for which I develop, we usually have this module structure.
When I'm testing my simple geometric library, I usually have one or two methods
When I want to get to a web, I usually have to do code
When I look at Java frameworks like Hibernate, JPA, or Spring, I usually have

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.