From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-3.3 required=5.0 tests=MAILING_LIST_MULTI, RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 15646 invoked from network); 23 Jun 2022 03:07:25 -0000 Received: from mother.openwall.net (195.42.179.200) by inbox.vuxu.org with ESMTPUTF8; 23 Jun 2022 03:07:25 -0000 Received: (qmail 7173 invoked by uid 550); 23 Jun 2022 03:07:23 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Reply-To: musl@lists.openwall.com Received: (qmail 6112 invoked from network); 23 Jun 2022 03:07:22 -0000 Date: Wed, 22 Jun 2022 23:07:09 -0400 From: Rich Felker To: He X Cc: musl@lists.openwall.com Message-ID: <20220623030708.GO7074@brightrain.aerifal.cx> References: <20220622131859.GM7074@brightrain.aerifal.cx> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Subject: Re: [musl] g++ fpermissive compilation error for strdupa On Thu, Jun 23, 2022 at 10:59:07AM +0800, He X wrote: > > so it's been kinda nice that this is catching bugs in C++ programs. > > I agreed. I will see what bazel guys say about the usage of strdupa. Maybe > they are willing to remove strdupa. > > > Maybe there's some way we can fix the C++ const issue but make it > produce warnings when strdupa is used in both C and C++...? > > I have no idea why '-fno-permissive' does not work for me. But whatever, it > is OK that the patch can not be merged upstream. You have it backwards I think. At least as I read the message, you need -fpermissive to allow this code to compile with the argument type mismatch. Rich