On 11 June 2015 at 20:57, Laszlo Ersek <ler...@redhat.com> wrote:
> On 06/11/15 15:50, Ard Biesheuvel wrote:
>> On 10 June 2015 at 19:22, Long, Qin <qin.l...@intel.com> wrote:
>>> Thanks, Ard.
>>>
>>> This is one historical changes, and come from some early user's requests: 
>>> they would like to keep the built result / image of this module identical 
>>> as possible, whatever any path was used (e.g. aaa/edk2/.../openssl v.s. 
>>> bbb/edk2/...openssl, ...). To meet this, we have to patch those __FILE__ 
>>> macro then.  :-(
>>>
>>
>> OK, fair enough.
>>
>>> I keep this for all later updates.
>>>
>>
>> I guess not all toolchains support
>>
>> #undef __FILE__
>> #define __FILE__ NULL
>>
>> ??
>>
>> because that would be a bit simpler.
>
> It would also be undefined behavior. The C standards say that
>
>   None of these macro names, nor the identifier "defined", shall be the
>   subject of a #define or a #undef preprocessing directive.
>

OK, got it.

-- 
Ard.

------------------------------------------------------------------------------
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/edk2-devel

Reply via email to