Re: bin/59713: bin/sh/Makefile clobbers COPTS.<fn>

["Sotiris Lamprinidis via gnats" <gnats-admin%NetBSD.org@localhost>]

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

From: Sotiris Lamprinidis<sotiris%lamprinidis.com@localhost>
To: netbsd-bugs%netbsd.org@localhost, gnats-bugs%netbsd.org@localhost,
 gnats-admin%netbsd.org@localhost
Cc: kre%munnari.OZ.AU@localhost
Subject: Re: bin/59713: bin/sh/Makefile clobbers COPTS.<fn>
Date: Sat, 17 Jan 2026 13:21:33 +0100

 > From gnats%netbsd.org@localhost Tue Oct 21 21:45:13 2025
 > From: "Robert Elz via gnats" <gnats-admin%NetBSD.org@localhost>
 > To: gnats-admin%netbsd.org@localhost,netbsd-bugs%netbsd.org@localhost,sotiris%lamprinidis.com@localhost
 > Subject: Re: bin/59713: bin/sh/Makefile clobbers COPTS.<fn>
 > Cc: 
 > Date: Tue, 21 Oct 2025 19:45:01 +0000 (UTC)
 >
 > The following reply was made to PR bin/59713; it has been noted by GNATS.
 >
 > From: Robert Elz <kre%munnari.OZ.AU@localhost>
 > To: gnats-bugs%netbsd.org@localhost
 > Cc: 
 > Subject: Re: bin/59713: bin/sh/Makefile clobbers COPTS.<fn>
 > Date: Wed, 22 Oct 2025 02:43:19 +0700
 >
 >      Date:        Sun, 19 Oct 2025 16:15:01 +0000 (UTC)
 >      From:        sotiris%lamprinidis.com@localhost
 >      Message-ID:  <20251019161501.25FA11A923C%mollari.NetBSD.org@localhost>
 >  
 >  
 >    | >Description:
 >    | bin/sh clobbers file-specific COPTS.<fn>; see patch
 >    |
 >    | I was trying to build netbsd-11 from netbsd-11/GCC 12.5 and there are a
 >    | few Werrors I addressed using COPTS.<fn> flags,
 >  
 >  I'd prefer to fix the code to avoid the warnings rather than work around
 >  them with "turn off" compilation flags, unless they are the kind of thing
 >  which really would be difficult or impossible to handle.
 >  
 >  What errors (warnings) are you fixing, and which architecture is that for?
 >  
 >  Feel free to send me off-list mail (to kre%munnari.oz.au@localhost or kre%netbsd.org@localhost)
 >  rather than adding lots more to this PR.
 >  
 >  kre
 >  
 >
 I am using -O3 and this was causing the errors. This would be a hacky way to
 do that without changing the source, "sniping" the files and disabling
 problematic optimizations for them.
 
 On second thought, this is not a good idea. It could possibly pollute the
 namespace. So, let's close this.
 
 Thanks for your time.
 S.