Jon Turney via Cygwin wrote:
On 13/02/2024 13:02, Christian Franke via Cygwin wrote:
Jon Turney via Cygwin wrote:
On 12/02/2024 16:49, ASSI via Cygwin wrote:
Christian Franke via Cygwin writes:
This requires that always the same build directory is used.
Would that be solvable by using -ffile-prefix-map or is there more to
it?
That should now be used in 0.36.8, so something else leaking the
local build directory into the package, perhaps
A closer look shows that (only) the pathnames of the assembly (*.S)
files in cygwin1.dll.dbg now contain the build path instead of the
mapped path:
$ strings cygwin1.dll.dbg | grep '^/.*bcopy\.S$' | uniq
/tmp/build/cygwin-3.5.0-1.x86_64/src/newlib-cygwin/winsup/cygwin/x86_64/bcopy.S
The paths in the released package are correct:
$ strings /usr/lib/debug/usr/bin/cygwin1.dll.dbg | grep
'^/.*bcopy\.S$' | uniq
/usr/src/debug/cygwin-3.5.0-1/winsup/cygwin/x86_64/bcopy.S
The regression was introduced by cygport commit 9e82685 in
conjunction with the fact that --file-prefix-map has no effect on *.S
files:
Great. I guess that means we need to use both options.
If both --file-prefix-map and --debug-prefix-map are used in cygport,
Cygwin 3.5.0-1 build is apparently reproducible.regardless of build path.
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation: https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
