Hi Hilmar,

The easiest fix is to replace the following line in debian/rules:

  cc -Wall -g -O2 -o build/wftodm wftodm.c

with:

  cc -ansi -g -O2 -o build/wftodm wftodm.c

It works under GCC 14 as well.

The "wftodm" binary is only used during build time to build AFM and PFA
fonts; it is not shipped to the end user of the package.
So IMHO this easy fix is enough.  What do you think?  If you agree, I will
upload the change to Salsa.


Regards,

-- 
Danai


On Thu, 1 Aug 2024 at 18:36, Danai SAE-HAN <danai.sae...@gmail.com> wrote:

> Okelidokeli.  I'll install GCC 14 on Debian/testing and start improving
> the code where I can.
>
> Cheers
>
> --
> Danai
>
> On Thu, 1 Aug 2024 at 05:28, Preuße, Hilmar <hill...@web.de> wrote:
>
>> Control: tags -1 + help
>>
>> On 31.07.2024 10:48, Danai SAE-HAN (韓達耐) wrote:
>>
>> Hi Danai,
>>
>> > When compiling wftodm.c from the latex-cjk-japanese-wadalab package, I
>> > get a bunch of warnings with GCC 13 (see also below Lucas' output).
>> > To me, these seems just fairly benign warnings based on deprecated C89
>> > conventions.
>> >
>> With GCC 14 these warnings turn into errors and the build fails (as
>> described), so these messages are not benign. They are long standing,
>> though. On the other hand, they are just syntax errors; so people which
>> speak C, should be able to fix them. I tried do a patch, but my C
>> knowledge got lost over years. I tag that bug "help" for now.
>>
>> > With this bug report, I've been thinking: should we continue to put
>> time
>> > and effort in a venerable but older package like CJK?
>> > Or do we keep this package as legacy, and forcefully ignore some of the
>> > warnings of the C compiler?
>> >
>> > Let me know what you think.
>> >
>> Unfortunately I don't speak CJK, I've never used any of these packages.
>> Hence I can't really say, how useful latex-cjk-japanese-wadalab is. The
>> popcon of both package are comparable (probably b/c latex-cjk-all
>> declares a dep on it). So, we can't simply drop it. I tend to say: let's
>> wait for help.
>>
>> Hilmar
>>
>

Reply via email to