GNU bug report logs -
#13775
24.3.50; Omissions in documentation for crash reporting
Previous Next
Reported by: Dmitry Gutov <dgutov <at> yandex.ru>
Date: Thu, 21 Feb 2013 07:29:01 UTC
Severity: minor
Found in version 24.3.50
Done: Dmitry Gutov <dgutov <at> yandex.ru>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
On 23.02.2013 1:44, Eli Zaretskii wrote:
>> Date: Sat, 23 Feb 2013 01:26:21 +0400
>> From: Dmitry Gutov <dgutov <at> yandex.ru>
>> CC: Eli Zaretskii <eliz <at> gnu.org>, 13775 <at> debbugs.gnu.org
>>
>> On 22.02.2013 13:37, Andreas Schwab wrote:
>>> Dmitry Gutov <dgutov <at> 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.)
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. :)
This bug report was last modified 12 years and 154 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.