From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: schwab@linux-m68k.org, 13775@debbugs.gnu.org
Subject: bug#13775: 24.3.50; Omissions in documentation for crash reporting
Date: Fri, 22 Feb 2013 23:44:55 +0200 [thread overview]
Message-ID: <83txp4koq0.fsf@gnu.org> (raw)
In-Reply-To: <5127E27D.8070504@yandex.ru>
> Date: Sat, 23 Feb 2013 01:26:21 +0400
> From: Dmitry Gutov <dgutov@yandex.ru>
> CC: Eli Zaretskii <eliz@gnu.org>, 13775@debbugs.gnu.org
>
> On 22.02.2013 13:37, Andreas Schwab wrote:
> > Dmitry Gutov <dgutov@yandex.ru> writes:
> >
> >> 'CFLAGS="-g3" make' doesn't.
> >
> > As expected and documented.
> >
> >> 'make CFLAGS="-g3"' does work, but AFAIK that's not the usual way of
> >> binding an environment variable value.
> >
> > This is wrong. Environment variables never override makefile variables.
>
> Sorry, what's wrong, exactly? My expectations, my retelling, or the way
> it actually works?
Your expectations that putting a variable into the environment will
override Make variable that is assigned in the Makefile. (If a
variable is not assigned in the Makefile, but used by one of its
rules, Make will use the value in the environment.)
And anyway, 'CFLAGS="-g3" make' doesn't export CFLAGS into the
environment of programs run by the shell, so this method is simply
wrong, for reasons that have nothing to do with Emacs.
next prev parent reply other threads:[~2013-02-22 21:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-21 7:27 bug#13775: 24.3.50; Omissions in documentation for crash reporting Dmitry Gutov
2013-02-21 8:31 ` Andreas Schwab
2013-02-21 17:24 ` Eli Zaretskii
2013-02-22 1:31 ` Dmitry Gutov
2013-02-22 9:24 ` Eli Zaretskii
2013-02-22 21:53 ` Dmitry Gutov
2013-02-22 9:37 ` Andreas Schwab
2013-02-22 21:26 ` Dmitry Gutov
2013-02-22 21:44 ` Eli Zaretskii [this message]
2013-02-22 22:00 ` Dmitry Gutov
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83txp4koq0.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=13775@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=schwab@linux-m68k.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).