Re: toolchain/59610: obsolete file check during release build blows up on case-insensitive host file systems

["Valery Ushakov via gnats" <gnats-admin%NetBSD.org@localhost>]

The following reply was made to PR toolchain/59610; it has been noted by GNATS.

From: Valery Ushakov <uwe%stderr.spb.ru@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: 
Subject: Re: toolchain/59610: obsolete file check during release build blows
 up on case-insensitive host file systems
Date: Mon, 24 Nov 2025 13:27:46 +0300

 Might not be immediately obvious from cvs log b/c postinstall was
 renamed to postinstall.in, so just a heads up that this commit (to the
 old "postinstall") might be relevant here:
 
   revision 1.210
   date: 2017-02-11 22:35:45 +0300;  author: uwe;  state: Exp;  lines: +14 -2;  commitid: kjrpHgvxhAbwnzFz;
   Don't use slow file_exists_exact if we don't have to.
 
   file_exists_exact function was introduced in 1.26 for the benefit of
   cross-building on OS X case-insensitive file system.  It is extremely
   slow on diskless machines.  That becomes especially noticeable when
   you upgrade a system that has a lot of obsolete files, it can take
   literally hours.
 
 though I tried to be careful not to change the way the checks are
 done, only when/if the checks are done.
 
 -uwe