On Thu, Apr 03, 2025 at 11:10:29AM +0900, Jun Omae wrote:
Hi,
On 2025/04/03 10:27, James McCoy wrote:
As noted in the [porting docs], GCC-15 uses c23 (well, gnu23) by
default. This causes -Wincompatible-pointer-types errors to occur when
building the Ruby SWIG bindings due to the rb_ensure, rb_
Hi,
On 2025/04/03 10:27, James McCoy wrote:
> As noted in the [porting docs], GCC-15 uses c23 (well, gnu23) by
> default. This causes -Wincompatible-pointer-types errors to occur when
> building the Ruby SWIG bindings due to the rb_ensure, rb_iterate, and
> rb_rescue2 callbacks.
>
> [porting docs
On 2025/04/03 20:23, Nathan Hartman wrote:
> On Wed, Apr 2, 2025 at 10:53 PM James McCoy wrote:
>
> On Thu, Apr 03, 2025 at 11:10:29AM +0900, Jun Omae wrote:
> >Hi,
> >
> >On 2025/04/03 10:27, James McCoy wrote:
> >> As noted in the [porting docs], GCC-15 uses c23 (well, gnu23)
On 2025/04/03 11:52, James McCoy wrote:
> On Thu, Apr 03, 2025 at 11:10:29AM +0900, Jun Omae wrote:
>> Hi,
>>
>> On 2025/04/03 10:27, James McCoy wrote:
>>> As noted in the [porting docs], GCC-15 uses c23 (well, gnu23) by
>>> default. This causes -Wincompatible-pointer-types errors to occur when
>>
On Wed, Apr 2, 2025 at 10:53 PM James McCoy wrote:
> On Thu, Apr 03, 2025 at 11:10:29AM +0900, Jun Omae wrote:
> >Hi,
> >
> >On 2025/04/03 10:27, James McCoy wrote:
> >> As noted in the [porting docs], GCC-15 uses c23 (well, gnu23) by
> >> default. This causes -Wincompatible-pointer-types errors
As noted in the [porting docs], GCC-15 uses c23 (well, gnu23) by
default. This causes -Wincompatible-pointer-types errors to occur when
building the Ruby SWIG bindings due to the rb_ensure, rb_iterate, and
rb_rescue2 callbacks.
[porting docs]: https://gcc.gnu.org/gcc-15/porting_to.html
This can
6 matches
Mail list logo