Mamoru TASAKA
Mamoru TASAKA
gcc14 now defaults to -Werror=incompatible-pointer-types. To support compilation with gcc14, cast GTK related objects properly. Fixes the following errors (compiled with upcoming gcc14) ``` lxpolkit/lxpolkit-listener.c: In function ‘on_completed’: lxpolkit/lxpolkit-listener.c:88:22: error:...
Currently for power_assert testsuite, it depends on byebug: https://github.com/ruby/power_assert/blob/297fa68908c45c4ca6c41e0940ebcc069744d580/power_assert.gemspec#L26 https://github.com/ruby/power_assert/blob/297fa68908c45c4ca6c41e0940ebcc069744d580/test/trace_test.rb#L10 So can I rely on byebug? Why I am asking here is that * The last activity on https://github.com/deivid-rodriguez/byebug seems...
gcc14 now defaults to -Werror=incompatible-pointer-types . To support this, cast GTK related objects for assignment properly. Fixes #100 .
Upcoming gcc14 now defaults to `-Werror=incompatible-pointer-types` , and compiling libfm git head with gcc14 produces the following errors: ``` /buildroot/libfm-1.3.2/_BUILDDIR_gtk2/../src/gtk/exo/exo-icon-view.c: In function ‘exo_icon_view_key_press_event’: /buildroot/libfm-1.3.2/_BUILDDIR_gtk2/../src/gtk/exo/exo-icon-view.c:2822:25: error: assignment to ‘GdkWindow *’ {aka...
Fedora project is now planning to import python 3.13 into Fedora 40, and now trying to rebuild all packages in Fedora with python 3.13b2 . With rdflib 7.0.0, testsuite `TestUtil.test_to_bits_from_bits_round_trip`...
Fixes the following warnings: ``` connect.c:162:19: warning: suggest parentheses around comparison in operand of ‘&’ [-Wparentheses] mailstream_ssl.c:368:32: warning: self-comparison always evaluates to false [-Wtautological-compare] mailstream_ssl.c:368:32: warning: suggest parentheses around comparison...
gcc14 now defaults to gcc -Werror=incompatible-pointer-types . This commit adds required casts to different pointer types.
As PEP 594 says, cgi module is marked as deprecated in python 3.11, and will be removed in 3.13 (actually removed at least in 3.13 rc1). As suggested on PEP...
With https://github.com/ruby/rexml/pull/167 REXML::Document.write may chomp output string compared to before. This change affects VagrantPlugins::ProviderLibvirt::Action::StartDomain#call internal behavior. Modify rspec testsuite to support this REXML behavior change. Closes #1836 .
(Although I am not testing vagrant-libvirt 0.11.2) vagrand-libvirt rspec testsuite fails like below: ``` + bundle exec rspec spec Run options: exclude {acceptance: true} ............................................................................................................................FFFFF..F....................................................................................................................................................................................................................................... Failures: 1) VagrantPlugins::ProviderLibvirt::Action::StartDomain#call nvram when...