public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Don Baker <dbaker@mcc.com>
To: cygwin@sourceware.cygnus.com
Cc: dbaker@mcc.com
Subject: Bug in B20.1 make with mixed case environment variables
Date: Wed, 30 Jun 1999 22:10:00 -0000	[thread overview]
Message-ID: <37726760.73181765@mcc.com> (raw)
Message-ID: <19990630221000.jZMH_O5wTKqFB6alwsgNelOlaiEkmC_O4XbUcWT15I4@z> (raw)

B20.1 uses GNU make 3.75 which seems to have a bug or mis-feature
where (DOS) environment variable names are converted to upper case
when made into makefile variables.  (I believe that GNU make 3.77
fixes this problem, so upgrading may be all that's necessary. 
Unfortunately, I don't know the exact lineage of the make 3.77
that I have.)

From a DOS shell, set an environment variable with lower case
letters:

set foo=hello

Then run make on the following makefile:

all:
	echo $(foo)

The echo is empty, unless the makefile variable is changed
to all upper case, where "hello" is printed.  This problem
does not seem to occur if the environment variable is set
in bash.  (Bash, however has all of the DOS environement
variables converted to upper case.)

Thanks for looking into this problem.

------------------------------------------------------------
Don Baker, Member of the Technical Staff
MCC, 3500 West Balcones Center Dr., Austin, Texas 78759-6509
dbaker@mcc.com * Phone: (512) 338-3362 * Fax: (512) 338-3890

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

             reply	other threads:[~1999-06-30 22:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-06-24 10:14 Don Baker [this message]
1999-06-30 22:10 ` Don Baker
1999-06-24 10:39 Earnie Boyd
1999-06-30 22:10 ` Earnie Boyd
1999-06-24 13:29 Dennis McCunney
1999-06-30 22:10 ` Dennis McCunney

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=37726760.73181765@mcc.com \
    --to=dbaker@mcc.com \
    --cc=cygwin@sourceware.cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).