Am Fri, Apr 11, 2025 at 10:58:29AM +0100 schrieb Colin Watson:
> On Thu, Apr 10, 2025 at 09:19:08PM +0200, Andreas Tille wrote:
> > when I NMUed this package I've spent quite some time into a patch[1] to
> > build with gcc-15. While I made some progress the problem is not yet
> > fully solved. Given that upstream is not active any more I wonder
> > whether it makes sense to remove this package from unstable/testing once
> > Trixi is released. This would affect the cccc package (Colin in CC)
> > which Build-Depends from pccts.
>
> It would make me sad, but I suppose I can't stop you.
I would love if someone might be able to stop me by fixing the issue.
BTW, I had another idea by adding -std=gnu17 option, but this fails as
well. If someone might be able to sort out the mess in dlg/main.c which
causes:
main.c:128:21: error: initialization of 'void (*)(char *)' from incompatible
pointer type 'void (*)(void)' [-Wincompatible-pointer-types]
128 | { "-CC", 0, (WildFunc)p_cpp, "Generate C++ output" },
| ^
main.c:128:21: note: (near initialization for
'options[0].process.process_one_arg')
main.c:84:6: note: 'p_cpp' declared here
84 | void p_cpp(void) { gen_cpp = TRUE; }
| ^~~~~
main.c:127:17: warning: missing braces around initializer [-Wmissing-braces]
127 | Opt options[] = {
| ^
128 | { "-CC", 0, (WildFunc)p_cpp, "Generate C++ output" },
| { }
main.c:129:21: error: initialization of 'void (*)(char *)' from incompatible
pointer type 'void (*)(void)' [-Wincompatible-pointer-types]
129 | { "-C0", 0, (WildFunc)p_comp0, "No compression (default)" },
| ^
main.c:129:21: note: (near initialization for
'options[1].process.process_one_arg')
main.c:63:6: note: 'p_comp0' declared here
63 | void p_comp0(void) {comp_level = 0;}
| ^~~~~~~
...
we might be trough all needed patches. I admit I would love if someone
would find the time to make all the time I've spent into those other
issues not wasted.
Kind regards
Andreas.
--
https://fam-tille.de
