Usage of __FILE__ results "captures build path"

[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.