Alexander Kanavin
Alexander Kanavin
llvm configuration should be obtained from llvm's cmake files only, not from llvm-config executable
As seen here, meson gets llvm configuration by running llvm-config: https://github.com/mesonbuild/meson/blob/master/mesonbuild/dependencies/dev.py#L195 Executing 'llvm-config' to obtain configuration is problematic in cross-compile situations: it is a target binary, and cannot be easily...
When cross compiling glib, this snippet in gio/tests/meson.build proved problematic: ``` plugin_resources_c = custom_target('plugin-resources.c', input : 'test4.gresource.xml', output : 'plugin-resources.c', command : [glib_compile_resources, compiler_type, '--target=@OUTPUT@', '--sourcedir=' + meson.current_source_dir(), '--internal', '--generate-source',...
According to https://pythonhosted.org/smartypants/ https://github.com/leohemsted/smartypants.py seems dead as well. I'm not sure what can be done about it, perhaps you could take over the maintainership?
This has been deprecated for a long time, and finally removed in python 3.12
These started to matter in perl 5.38 where they are used to print line numbers.
When building 2.3.0 with clang, the following error occurs: ``` /mnt/b/yoe/master/build/tmp/work/core2-64-yoe-linux-musl/python3-kivy/2.3.0/git/kivy/graphics/cgl_backend/cgl_gl.c:4549:52: error: incompatible function pointer types assigning to 'void (*)(GLuint, GLsizei, const GLchar **, const GLint *)' (aka 'void (*)(unsigned...
This allows testing Y2038 with system time set to after that (i.e.2040), so that actual Y2038 issues can be exposed, and not masked by key expiry time errors.
Now that the original homepage is going away, it would be good to start providing release tarballs here: https://github.com/sysstat/sysstat/releases (perhaps historical tarballs aren't needed, just the two latest development/stable releases,...
The old homepage does say that 12.7.x is a development serie, and stable 12.6.x is stable one, but the new home page does not. So has the policy changed? Which...
Latest autoconf-archive should provide an updated compatible version.