Hello,
I proposed years ago that we drop this package years ago since it had been superceded by antlr. At the time, someone was convinced it was a good idea
to keep it and did some work to do so.
If there is a compelling reason to keep it we could try to keep it "limping along" but I don't feel there is a compelling reason to do so.
Thanks,
Dale
On Fri, Apr 11, 2025 at 11:42 AM Andreas Tille <
tille@debian.org> wrote:
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
<div dir="ltr"><div>Hello,</div><div>I proposed years ago that we drop this package years ago since it had been superceded by antlr. At the time, someone was convinced it was a good idea to keep it and did some work to do so.</div><div><br></div><div>If
there is a compelling reason to keep it we could try to keep it "limping along" but I don't feel there is a compelling reason to do so.</div><div><br></div><div>Thanks,</div><div> Dale</div></div><br><div class="gmail_quote gmail_quote_
container"><div dir="ltr" class="gmail_attr">On Fri, Apr 11, 2025 at 11:42 AM Andreas Tille <<a href="mailto:
tille@debian.org">
tille@debian.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px
solid rgb(204,204,204);padding-left:1ex">Am Fri, Apr 11, 2025 at 10:58:29AM +0100 schrieb Colin Watson:<br>
> On Thu, Apr 10, 2025 at 09:19:08PM +0200, Andreas Tille wrote:<br>
> > when I NMUed this package I've spent quite some time into a patch[1] to<br>
> > build with gcc-15. While I made some progress the problem is not yet<br>
> > fully solved. Given that upstream is not active any more I wonder<br>
> > whether it makes sense to remove this package from unstable/testing once<br>
> > Trixi is released. This would affect the cccc package (Colin in CC)<br>
> > which Build-Depends from pccts.<br>
> <br>
> It would make me sad, but I suppose I can't stop you.<br>
I would love if someone might be able to stop me by fixing the issue.<br>
BTW, I had another idea by adding -std=gnu17 option, but this fails as<br> well. If someone might be able to sort out the mess in dlg/main.c which<br> causes:<br>
main.c:128:21: error: initialization of 'void (*)(char *)' from incompatible pointer type 'void (*)(void)' [-Wincompatible-pointer-types]<br>
128 | { "-CC", 0, (WildFunc)p_cpp, "Generate C++ output" },<br>
| ^<br>
main.c:128:21: note: (near initialization for 'options[0].process.process_one_arg')<br>
main.c:84:6: note: 'p_cpp' declared here<br>
84 | void p_cpp(void) { gen_cpp = TRUE; }<br>
| ^~~~~<br>
main.c:127:17: warning: missing braces around initializer [-Wmissing-braces]<br>
127 | Opt options[] = {<br>
| ^<br>
128 | { "-CC", 0, (WildFunc)p_cpp, "Generate C++ output" },<br>
| { }<br> main.c:129:21: error: initialization of 'void (*)(char *)' from incompatible pointer type 'void (*)(void)' [-Wincompatible-pointer-types]<br>
129 | { "-C0", 0, (WildFunc)p_comp0, "No compression (default)" },<br>
| ^<br>
main.c:129:21: note: (near initialization for 'options[1].process.process_one_arg')<br>
main.c:63:6: note: 'p_comp0' declared here<br>
63 | void p_comp0(void) {comp_level = 0;}<br>
| ^~~~~~~<br>
...<br>
we might be trough all needed patches. I admit I would love if someone<br> would find the time to make all the time I've spent into those other<br> issues not wasted.<br>
Kind regards<br>
Andreas.<br>
-- <br>
<a href="
https://fam-tille.de" rel="noreferrer" target="_blank">
https://fam-tille.de</a><br>
</blockquote></div>
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)