In data martedì 14 novembre 2017 11:14:00 CET, Ximin Luo ha scritto: > You're using __FILE__ inappropriately, none of the documentation > guarantees or implies that you can access __FILE__ as a real > filesystem path. "Surely for relative paths" is your justification > for your own broken behaviour.
Again, this is your own echo chamber: "__FILE__ is broken, everybody using it is broken no matter what". > You can either accept my one line patch suggestion, or fix it some > other way. I am not interested in working around broken changes introduced blindly for very doubtful reasons. > I'm not going to change the GCC patch, it does nothing wrong. Let me add also another POV to this approach: do you really expect Debian to carry this important diversion for GCC upstream? I really doubt GCC will accept this. -- Pino Toscano
signature.asc
Description: This is a digitally signed message part.