[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220623030708.GO7074@brightrain.aerifal.cx>
Date: Wed, 22 Jun 2022 23:07:09 -0400
From: Rich Felker <dalias@...c.org>
To: He X <xw897002528@...il.com>
Cc: musl@...ts.openwall.com
Subject: Re: 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
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
