[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#13775: 24.3.50; Omissions in documentation for crash reporting

From: Dmitry Gutov
Subject: bug#13775: 24.3.50; Omissions in documentation for crash reporting
Date: Sat, 23 Feb 2013 02:00:30 +0400
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130215 Thunderbird/17.0.3

On 23.02.2013 1:44, Eli Zaretskii wrote:
Date: Sat, 23 Feb 2013 01:26:21 +0400
From: Dmitry Gutov <address@hidden>
CC: Eli Zaretskii <address@hidden>, address@hidden

On 22.02.2013 13:37, Andreas Schwab wrote:
Dmitry Gutov <address@hidden> 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.)

I expected it may get picked up in some special way. ./configure does that, after all, and it also shells out during execution.

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.

So, I was doubly wrong. Thanks for elaboration. :)

reply via email to

[Prev in Thread] Current Thread [Next in Thread]