You're receiving this bug because the package in Summary has produced _FORTIFY_SOURCE related warnings indicating the presence of a sure overflow in a static buffer. Even though this is not always an indication of a security problem it might even be. So please check this out ASAP. By the way, _FORTIFY_SOURCE is disabled when you disable optimisation, so don't try finding out the cause using -O0. Thanks, Your friendly neighborhood tinderboxer
Created attachment 252069 [details] Build log
Upstream is dead since 2003. Nothing in the tree depends on it. Treecleaning?
Masked for removal in 30 days.
I haven't used mtink in quite some time, but last time I did it worked. Is there any replacement? Is there some real problem with that package except this warning?
(In reply to comment #4) > I haven't used mtink in quite some time, but last time I did it worked. Is > there any replacement? Is there some real problem with that package except this > warning? It still builds, otherwise I cannot test it (anyone still has a 9-year old Eposon printer?). Feel free to start proxy-maintaining it (with my help), and start by providing a patch for the buffer overflow bug. Printing is badly understaffed; nobody looked at this bug for a while so cleaning out was a logical consequence.
Created attachment 299003 [details, diff] mtinkd_buffer_overflow.patch > It still builds, otherwise I cannot test it (anyone still has a 9-year old > Eposon printer?). I have an DX3850 and it works (at least it managed to show the inc levels last time I tried). Not sure it it is that old. > Feel free to start proxy-maintaining it (with my help), and start by providing > a patch for the buffer overflow bug. Printing is badly understaffed; nobody > looked at this bug for a while so cleaning out was a logical consequence. Here's the patch. Feel free to CC me on bugs, but I'm not interested in anything beyond basic functionality.
Created attachment 299005 [details, diff] mtinkd_buffer_overflow.patch Last version of the patch was hand edited, here's a proper version.
And it seems that adding ${MAKEOPTS} to the make call in src_compile works.
Excellent. Thanks for the patch. Fixed.