On Thu, 2025-03-13 at 14:53 +, Jonathan Wakely wrote:
> On Tue, 11 Feb 2025 at 22:44, Sérgio Basto wrote:
> >
> > On Tue, 2025-02-11 at 21:45 +, Jonathan Wakely wrote:
> > > On Tue, 28 Jan 2025 at 09:07, Jakub Jelinek
> > > wrote:
> > > >
> > > > On Mon, Jan 27, 2025 at 07:31:35PM +
On Tue, 11 Feb 2025 at 22:44, Sérgio Basto wrote:
>
> On Tue, 2025-02-11 at 21:45 +, Jonathan Wakely wrote:
> > On Tue, 28 Jan 2025 at 09:07, Jakub Jelinek wrote:
> > >
> > > On Mon, Jan 27, 2025 at 07:31:35PM +, Sérgio Basto via devel
> > > wrote:
> > > > I just want check, if I'm thinki
On Tue, 2025-02-11 at 21:45 +, Jonathan Wakely wrote:
> On Tue, 28 Jan 2025 at 09:07, Jakub Jelinek wrote:
> >
> > On Mon, Jan 27, 2025 at 07:31:35PM +, Sérgio Basto via devel
> > wrote:
> > > I just want check, if I'm thinking correctly before submitting a
> > > fix in
> > > gtest packag
On Tue, 28 Jan 2025 at 09:07, Jakub Jelinek wrote:
>
> On Mon, Jan 27, 2025 at 07:31:35PM +, Sérgio Basto via devel wrote:
> > I just want check, if I'm thinking correctly before submitting a fix in
> > gtest package
> >
> > The problem is on Rawhide I have this warning that make other package
On Mon, Jan 27, 2025 at 07:31:35PM +, Sérgio Basto via devel wrote:
> I just want check, if I'm thinking correctly before submitting a fix in
> gtest package
>
> The problem is on Rawhide I have this warning that make other packages
> fail to build [1]
>
> gtest source [2] source get __cplu
On 2025/01/27 21:15, Sérgio Basto via devel wrote:
On Mon, 2025-01-27 at 20:52 +0100, Cristian Le via devel wrote:
According to the CPP standard, and the deprecation was
added in CPP20 [1] so would be best not to patch that part
unconditionally in the gtest source. Maybe you could patch in a
p
On Mon, 2025-01-27 at 20:52 +0100, Cristian Le via devel wrote:
> According to the CPP standard, and the deprecation was
> added in CPP20 [1] so would be best not to patch that part
> unconditionally in the gtest source. Maybe you could patch in a
> pragma to disable the warning instead?
>
> Anot
According to the CPP standard, and the deprecation was added in CPP20
[1] so would be best not to patch that part unconditionally in the gtest
source. Maybe you could patch in a pragma to disable the warning instead?
Another option could be to drop the CPP standard check altogether and rely on
Hi,
I just want check, if I'm thinking correctly before submitting a fix in
gtest package
The problem is on Rawhide I have this warning that make other packages
fail to build [1]
gtest source [2] source get __cplusplus value and include or
#include depending on __cplusplus value .
On rawhi
