Usage of __FILE__ results "captures build path"

[Ximin Luo]

Joachim Reichel:
> Hi,
> 
> the differences in libCGAL.a and libCGAL_Core.a at
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/diffoscope-results/cgal.html
> most likely result from the use of the __FILE__ macro in error messages in
> combination with absolute paths as arguments to -I. What is the recommended way
> to deal with this? Rewriting the build system such that it passes only relative
> paths to -I is not really an option.
> 
> There is the -fdebug-prefix-map gcc option for debug information. Do we need
> someting similar for __FILE__?
> 
> Joachim
> 
> P.S.: Please CC: me on replies.
> 

Hi Joachim, we plan on submitting some patches to GCC to fix this in one central place.

See

https://lists.alioth.debian.org/pipermail/reproducible-builds/Week-of-Mon-20160822/006788.html

https://lists.alioth.debian.org/pipermail/reproducible-builds/Week-of-Mon-20160905/006984.html

and

https://lists.alioth.debian.org/pipermail/reproducible-builds/Week-of-Mon-20160912/007076.html

for more details.

Help writing these patches would be welcome! I am pretty rusty with my C/C++.

X

-- 
GPG: ed25519/56034877E1F87C35
GPG: rsa4096/1318EFAC5FBBDBCE
https://github.com/infinity0/pubkeys.git